Skip to content

eclectic librarian

random musings from a serialist

  • Home
  • Blog
  • About
  • CV
  • Contact Me
eclectic librarian

Tag: National Aeronautics and Space Administration

Serials Solutions DC Users Group Meeting 2012

Meeting Table by Mo Elnadi
“Meeting Table” by Mo Elnadi

Updates from Serials Solutions – mostly Resource Manager (Ashley Bass):

  • Keep up to date with ongoing enhancements for management tools (quarterly releases) by following answer #422 in the Support Center, and via training/overview webinars.
  • Populating and maintaining the ERM can be challenging, so they focused a lot of work this year on that process: license template library, license upload tool, data population service, SUSHI, offline date and status editor enhancements (new data elements for sort & filter, new logic, new selection elements, notes), and expanded and additional fields.
  • Workflow, communication, and decision support enhancements: in context help linking, contact tool filters, navigation, new Counter reports, more information about vendors, Counter summary page, etc. Her most favorite new feature is “deep linking” functionality (aka persistent links to records in SerSol). [I didn’t realize that wasn’t there before — been doing this for my own purposes for a while.]
  • Next up (in two weeks, 4th quarter release): new alerts, resource renewals feature (reports! and checklist!, will inherit from Admin data), Client Center navigation improvements (i.e. keyword searching for databases, system performance optimization), new license fields (images, public performance rights, training materials rights) & a few more, Counter updates, SUSHI updates (making customizations to deal with vendors who aren’t strictly following the standard), gathering stats for Springer (YTD won’t be available after Nov 30 — up to Sept avail now), and online DRS form enhancements.
  • In the future: license API (could allow libraries to create a different user interface), contact tools improvements, interoperability documentation, new BI tools and reporting functionality, and improving the Client Center.
  • Also, building a new KB (2014 release) and a web-scale management solution (Intota, also coming 2014). They are looking to have more internal efficiencies by rebuilding the KB, and it will include information from Ulrich’s, new content types metadata (e.g. A/V), metadata standardization, industry data, etc.

Summon Updates (Andrew Nagy):

  • I know very little about Summon functionality, so just listened to this one and didn’t take notes. Take-away: if you haven’t looked at Summon in a while, it would be worth giving it another go.

360 Link Customization via JavaScript and CSS (Liz Jacobson & Terry Brady, Georgetown University):

Goal #1: Allow users to easily link to full-text resources. Solution: Go beyond the out-of-the box 360 Link display.
Goal #2: Allow users to report problems or contact library staff at the point of failure. Solution: eresources problem report form

They created the eresources problem report form using Drupal. The fields include contact information, description of the resource, description of the problem, and the ability to attach a screenshot.

When they evaluated the slightly customized out of the box 360 Link page, they determined that it was confusing to users, with too many options and confusing links. So, they took some inspiration from other libraries (Matthew Reidsma’s GVUS jQuery code available on Github) and developed a prototype that uses custom JavaScript and CSS to walk the user through the process.

Some enhancements included: making the links for full-text (article & journal) butttons, hiding additional help information and giving some hover-over information, parsing the citation into the problem report page, and moving the citation below the links to full-text. For journal citations with no full-text, they made the links to the catalog search large buttons with more text detail in them.

Some of the challenges of implementing these changes is the lack of a test environment because of the limited preview capablities in 360 Link. Any changes actually made required an overnight refresh and they would be live, opening the risk of 24 hour windows of broken resource links. So, they created their own test environment by modifying test scenarios into static HTML files and wrapping them in their own custom PHP to mimic the live pages without having to work with the live pages.

[At this point, it got really techy and lost me. Contact the presenters for details if you’re interested. They’re looking to go live with this as soon as they figure out a low-use time that will have minimal impact on their users.]


Customizing 360 Link menu with jQuery (Laura Wrubel, George Washington University)

They wanted to give better visual clues for users, emphasize the full-text, have more local control over linkns, and visual integration with other library tools so it’s more seamless for users.

They started with Reidsma’s code, then then forked off from it. They added a problem link to a Google form, fixed ebook chapter links and citation formatting, created conditional links to the catalog, and linked to their other library’s link resolver.

They hope to continue to tweak the language on the page, particularly for ILL suggestion. The coverage date is currently hidden behind the details link, which is fine most of the time, but sometimes that needs to be displayed. They also plan to load the print holdings coverage dates to eliminate confusion about what the library actually has.

In the future, they would rather use the API and blend the link resolver functionality with catalog tools.


Custom document delivery services using 360 Link API (Kathy Kilduff, WRLC)

They facilitate inter-consortial loans (Consortium Loan Service), and originally requests were only done through the catalog. When they started using SFX, they added a link there, too. Now that they have 360 Link, they still have a link there, but now the request form is prepopulated with all of the citation information. In the background, they are using the API to gather the citation information, as well as checking to see if there are terms of use, and then checking to see if there are ILL permissions listed. They provide a link to the full-text in the staff client developed for the CLS if the terms of use allow for ILL of the electronic copy. If there isn’t a copy available in WRLC, they forward the citation information to the user’s library’s ILL form.


License information for course reserves for faculty (Shanyun Zhang, Catholic University)

Included course reserve in the license information, but then it became an issue to convey that information to the faculty who were used to negotiating it with publishers directly. Most faculty prefer to use Blackboard for course readings, and handle it themselves. But, they need to figure out how to incorporate the library in the workflow. Looking for suggestions from the group.


Advanced Usage Tracking in Summon with Google Anaytics (Kun Lin, Catholic University)

In order to tweak user experience, you need to know who, what, when, how, and most important, what were they thinking. Google Anayltics can help figure those things out in Summon. Parameters are easy ways to track facets, and you can use the data from Google Analytics to figure out the story based on that. Tracking things the “hard way,” you can use the conversion/goal function of Google Analytics. But, you’ll need to know a little about coding to make it work, because you have to add some javascripts to your Summon pages.


Use of ERM/KB for collection analysis (Mitzi Cole, NASA Goddard Library)

Used the overlap analysis to compare print holdings with electronic and downloaded the report. The partial overlap can actually be a full overlap if the coverage dates aren’t formatted the same, but otherwise it’s a decent report. She incorporated license data from Resource Manager and print collection usage pulled from her ILS. This allowed her to create a decision tool (spreadsheet), and denoted the print usage in 5 year increments, eliminating previous 5 years use with each increment (this showed a drop in use over time for titles of concern).


Discussion of KnowledgeWorks Management/Metadata (Ben Johnson, Lead Metadata Librarian, SerialsSolutions)

After they get the data from the provider or it is made available to them, they have a system to automatically process the data so it fits their specifications, and then it is integrated into the KB.

They deal with a lot of bad data. 90% of databases change every month. Publishers have their own editorial policies that display the data in certain ways (e.g., title lists) and deliver inconsistent, and often erroneous, metadata. The KB team tries to catch everything, but some things still slip through. Throught the data ingestion process, they apply rules based on past experience with the data source. After that, the data is normalized so that various title/ISSN/ISBN combinations can be associated with the authority record. Finally, the data is incorporated into the KB.

Authority rules are used to correct errors and inconsistencies. Rule automatically and consistently correct holdings, and they are often used to correct vendor reporting problems. Rules are condified for provider and database, with 76,000+ applied to thousands of databases, and 200+ new rules are added each month.

Why does it take two months for KB data to be corrected when I report it? Usually it’s because they are working with the data providers, and some respond more quickly than others. They are hoping that being involved with various initiatives like KBART will help fix data from the provider so they don’t have to worry about correcting it for us, but also making it easier to make those corrections by using standards.

Client Center ISSN/ISBN doesn’t always work in 360 Links, which may have something to do with the authority record, but it’s unclear. It’s possible that there are some data in the Client Center that haven’t been normalized, and could cause this disconnect. And sometimes the provider doesn’t send both print and electronic ISSN/ISBN.

What is the source for authority records for ISSN/ISBN? LC, Bowker, ISSN.org, but he’s not clear. Clarification: Which field in the MARC record is the source for the ISBN? It could be the source of the normalization problem, according to the questioner. Johnson isn’t clear on where it comes from.

Author AnnaPosted on November 15, 2012Categories libraryTags Andrew Nagy, API, Ashley Bass, Ben Johnson, catalog search large buttons, catalog tools, Catholic University, Client Center, Consortium Loan Service, data, Data management, DC, decision tool, document delivery services, editor, ERMS, George Washington University, Georgetown University, Github, google, HTML, Illinois, information, JavaScript, Kathy Kilduff, knowledge base, Knowledge representation, Lead Metadata Librarian, library science, license upload tool, Liz Jacobson, Matthew Reidsma, metadata, Microsoft Windows, Mo Elnadi, NASA Goddard Library, National Aeronautics and Space Administration, php, Resource Manager, serials solutions, Support Center, Technical communication, web-scale management solution, workflowLeave a comment on Serials Solutions DC Users Group Meeting 2012

CIL 2011: Repositories — Strategies & Practices

Speakers: Mitzi M. Cole & Jeremy Gottwig

They wanted to create an author and publication repository. They maintain information about the authors with name variants and the codes for their divisions, in addition to identifying the relationships between the author and publication and among the authors themselves. The display of this information needed to be displayed with links to the full-text using their link resolver or by attaching full text files when allowed by copyright. Those needs helped identify requirements for the system they chose.

They were able to use the Homeland Security database of NASA employees to harvest information about the authors to begin populating that database. They then harvested data from a number of commercial sources to find their publications.

They developed crosswalks to move metadata from the various sources, and developed a utility to de-dupe the records and match author name variants. They also used the OpenURL standard to create full-text links.

They used Fedora Repository to store all of this. In order to use Fedora, you need to think in objects. Using relational queries, you can repurpose almost all of your data.

The author metadata was created using MADS in a separate tool and then exported to the format needed for Fedora. They used the local identification numbers for employees for the PID. On the public display of the author record, they show the author’s publications and the related authors (i.e. co-authors).

In the publications database, they used PUB_MD identifiers for publications to create unique PIDs. Unfortunately, there were problems with variations because they were pulling data from several sources.

The public end uses Drupal with Zen-based themes. For future consideration, they are looking at self-submission methods, Hydra, Islandora, BibApp, and whatever else may be developed which will plug into Fedora.

Talk to the end users early and often. We think like librarians and they don’t. Publisher metadata can be problematic — even they have trouble with author disambiguation. Automation can only go so far, and you still need human quality control. There’s always something new on the horizon.

Speaker: Amy Buckland

Many repositories are founded because someone at an institution wants one or sets it as a goal. But you need to know what that means.

Clifford Lynch calls it “a set of services that a university offers to the members of its community for the management and dissemination of digital materials created by the institution and its community members.”

If it’s a service, it impacts all areas of the library. It needs to be sustainable, and flexible as formats change. At McGill, they mediate the deposits in order to make sure copyrights are honored.

How do users find out about your IR? What kind of support will it have? You need to know this at the beginning so that you can market it to the stakeholders.

Who are the members of the community? Will students be included? At McGill, they are, and it’s a requirement for graduation that theses are deposited.

There is no way that what you are using for your IR will make it manageable and accessible. Be very wary of tools that promise this.

What goes in? What kinds of digital materials? Is it dark or open? Flat media (articles, papers, theses, etc) are easy, but it gets tricky with other objects and dynamic resources like blogs and websites.

The standards don’t stay standard for very long. Pick one and stick to it, because retro-fitting is challenging.

Who is a part of your institution? Do alumni get included? For public institutions, is the public included?

Institutional repository is a librarian term. Call it something else depending on who you talk to so that it has meaning to them.

“our goal is to take advantage of the web to make the knowledge created at our institution available to the world”

Speaker: Jim DelRosso

Digital projects are chronically understaffed. We need to be advocates to change that.

If you are going into digital repositories, copyright is going to be a pain in your butt.

Digitization isn’t magical. It takes people to figure out if it can be included and then do all the work to get it there. If it was possible to do this easily, libraries wouldn’t be doing it, Google would.

Step one: digitize
Step two: ???
Step three: Profit! (or for libraries, survive)

People are one of the toughest things to get support for. Tech is shiny and gets the attention, but it can be done without staff. Tell decision makers that technologies go obsolete, shiny gets dull, but people will last.

Our capacity to do works that will stagger our users and our peers is sometimes missed. There is right now more potential for the dissemination and preservation of knowledge than we have ever seen in human history. Go forth and do that!

Author AnnaPosted on March 23, 2011Categories libraryTags Academic publishing, Archival science, author, cil11, Clifford Lynch, communication, Fedora, flat media, google, institutional repository, Jim DelRosso, Knowledge, librarian, library, library science, metadata, Mitzi M. Cole, National Aeronautics and Space Administration, open access, repositories, Repository, science, speaker, Tool, ZenLeave a comment on CIL 2011: Repositories — Strategies & Practices
  • October 2026 statsNovember 10, 2026
  • September 2026 statsOctober 2, 2026
  • August 2026 StatsSeptember 1, 2026
  • keeping track of work thingsApril 15, 2025
  • running is kind of…fun?February 12, 2025
  1. barrywynn on running is kind of…fun?February 12, 2025

    Yay for getting it done!

  2. barrywynn on board games played in Jan 2025February 6, 2025

    Thanks for the reviews. Been wanting to try more board games.

  3. Kathryn Greenhill on NASIG Annual 2023June 2, 2023

    Thanks for this Anna. With the decline of the birdsite (and my decision not to play there) I am feeling…

Recent Photo
Recently Played Board Games
  • Home
  • Blog
  • About
  • CV
  • Contact Me
eclectic librarian Proudly powered by WordPress