WorldCat knowledge base Release Notes for Contents

(1)

WorldCat knowledge base

Release Notes for 2013-05-12

New Features

Data Version and Last Updated Display

Users are understandably concerned about data currency. To help with this determination, the WorldCat knowledge base has added two fields on the Collection Properties page just below the

Collection ID. The first, Data Version, tells users which knowledge base data release is the source for

that collection.

Just below the Data Version field, users will see a second new field, Last Updated, which tells users when the collection, or an item in the collection, was last updated either via a knowledge base update or by the user.

PubMed LinkOut Export

To help libraries with discoverability, we have added a new export type, PubMed LinkOut, to the

Download Library Holdings File feature on the Library Holdings page. The NCBI explains that “LinkOut

is a service that allows you to link directly from PubMed and other NCBI databases to a wide range of information and services beyond the NCBI systems”

http://www.ncbi.nlm.nih.gov/projects/linkout/doc/linkout.html. In order to use this functionality, users will need to create an Identity File. For instructions on how to do so, see:

http://www.ncbi.nlm.nih.gov/books/NBK3807/#files.Identity_File. Users can then export the holdings file from the knowledge base. After exporting the file, open it, find <Base>[[&resolver.url]]</Base> and point to the identity file you created. For more information see:

http://www.ncbi.nlm.nih.gov/books/NBK3808/

Like the library holdings export, the PubMed LinkOut file is refreshed every two weeks. The export includes only PubMed items with coverage dates and without embargoes or moving wall coverage and is not de-duped.

(3)

3

Article Filtering in WorldCat Setting

We have added a new setting in the Library Holdings tab called Use Knowledge Base Coverage to

Determine Article Holdings in WorldCat Local Discovery Interface.

This setting changes the functionality of WorldCat Local to use the KB holdings data instead of WorldCat holdings data to filter article results held by your library. Setting this selection to "Yes" uses the

coverage information maintained in the knowledge base to display to users in WorldCat Local only items for which your library holds the fulltext or print as determined by your knowledge base holdings

coverage information. The setting is now available in the WorldCat knowledge base, but is not currently used by WorldCat Local. The WorldCat Local team is working on updating their application to enable the feature. We will announce via the User Support Center when users can enable this setting.

Enhancements

Collection ID Auto-Increment

When creating new collections, users are required to enter a unique Collection ID. In the past, the system has pre-populated the Collection ID field with a value: customer.regid.1. Thus, the user needed to remember, or guess, a unique value for the Collection ID in order to save successfully. The system now pre-populates the Collection ID field with the next available consecutive Collection ID based on the pattern customer.regid.number. It also excludes any Collection ID that has already been used,

allocated, or deleted, and it reads from the highest number previously used to create a new Collection

ID. For example, if a user, guessing a unique Collection ID, entered customer.regid.123456, then, for

the next collection created, the system will pre-populate Collection ID with customer.regid.123457. So, large numbers are possible and should not cause alarm. Users are still able to change the value in this field should they desire, but this should speed collection creation and eliminate save errors cause by non-unique Collection IDs.

Provider-Specific Settings for Infobase & IRIS Education

Some providers require special settings for proper linking. We have added Library ID fields for Infobase and IRIS Education. These are located in Settings in the Provider-Specific accordion.

Linking Keys Editable and Visible in Interface

Some collections require extra bits of information, or keys, for links to work properly or to link more deeply. Users have been able to see and edit the Journal Linking Key for the Journal format for some

(4)

4 time. We have now added a Linking Key field that is visible and editable for other formats (e-book, audio, image, video, and other) as well. We have also added, at the collection level, a visible and editable Database Linking Key field. These fields will allow users to make edits when necessary as well as allow them to do more with custom collections.

Normalized and Diacritics Enabled Titles in API and Link Resolver

End users enter search terms in multiple and various ways. Sometimes they copy and paste exact titles with diacritics, type on non-English keyboards, or otherwise use diacritics, for example: Française. Other times they will enter a title in normalized text, for example: Francaise. We have changed our system to handle either use case for title requests through the API or link resolver.

Author Exposed in API

We had previously exposed author fields in the OpenURL response from the API. Now we have changed the REST API (used to create the A to Z list view) to expose author fields as well.

Bug Fixes

Moving Wall Coverage R Value

In the February release we changed the system to use the standard KBART R value for moving wall coverage start dates. While the KBART file upload successfully handled the R value, the Service Configuration interface still displayed a P value for moving wall coverage even when values were correctly entered as R in the KBART upload. This has been corrected. The KBART upload and download and the Service Configuration interface both display moving wall coverage as R values and embargoes as P values. The WorldShare interface also handles R values via file upload and download, but displays the moving wall and embargo coverage in natural language rather than encoding.

Incorrect Data Feeds Values Exposed

Libraries using the Upload Library Holdings File on the Library Holdings page saw “Service,” “UI,” and “Config” as Selected data feeds only options in their Data Feeds settings. The cause of this has been corrected and in the weeks following the release we will clean up any of these invalid feeds that may remain in the system after the release and correction.

Google Scholar Broken for WorldShare Interface

For the WorldShare interface only, users were unable to select “yes” for Google Scholar on the Library

Holdings page and save the setting. This has been corrected and users can now successfully select “yes”

(5)

5

Loss of Provider-Specific Settings with Collection Name or Link Change

For Library or Location ID related Provider-Specific Settings (EBL, ebrary, Factiva, or Gale), changes in

Collection Name or Collection Link Formula resulted in loss of these Provider-Specific Settings values.

Consequently, links broke resulting in inaccessibility for end users. We have corrected this issue.

Known Issues

LMAN KB Flyout Missing for WorldShare interface

During the May 2012 release we implemented license manager integration in the collection and title information flyouts. The information icon would check the collection for known licenses. If there was a license attached to it, then a link to the license appeared. If there was no license attached to it, then it linked to the Create License screen in license manager and pre-populated it with the collection

information. The feature was temporarily disabled due to a technical issue. It remains disabled, but will be re-enabled in a future release.

Overlay Anything Feature not Available in WorldShare Interface

As noted in the February 2013 release notes, the ability to edit records from fully selected collections in the WorldShare interface is not yet implemented. This will be corrected in an upcoming release. This feature is implemented for the Service Configuration interface.