WorldCat knowledge base Release Notes for Contents

Transcription

1 WorldCat knowledge base Release Notes for Contents New Features... 2 Detailed title level reporting for file uploads... 2 Refresh data from the WorldCat Registry... 3 Opac links from the WorldCat Registry... 3 Proxy and provider specific settings per collection... 5 Controls for the Google Scholar feed per collection... 5 LinkScheme per record... 6 Enhancements... 6 Automated data loads visible in Activity History... 6 View/Edit collection level link formula... 6 Retrieve all content types in the KBART download... 8 API Enhancements and enhancements to integrated products... 8 Collection results sortable by update time... 8 Access to the available scope... 9 Download titles in this collection... 9 ISBN and collection_user_note in response to an entries query... 9 Bug Fixes Delete coverage and/or enum when not present in the upload file Title IDs with spaces Downloading selected holdings for large collections Known Issues None... 10

2 New Features Detailed title level reporting for file uploads Reports are now generated at the title level that describe all of the actions taken as a result of a file upload. The report of the details of a file upload is available from the Activity History screen. It will return a report containing the same information as was in the upload with an additional column for the RESULT. The file will contain all of the records from the uploaded file as well as any records that were already present in your collection when the upload was done. This enables an administrator to know exactly what the state of the collection was after the load and also to see what may have gone wrong with some of the records. Some of the more common RESULT values are listed below. RESULT value selected updated unmatched duplicate invalid_missing_oclc_entry_id previously_selected_in_upload previously_selected_not_in_upload invalid Explanation The record was selected as a result of the file upload. The record was changed by the file upload (when 'overlay' or 'covoverlay' is used). The record was not matched to any record in the collection. No action was taken. The row is a duplicate of another row in the file. A value in the oclc entry id column is required to select/deselect records, but it was not present in the file. The record was in the uploaded file, and was previously selected. Nothing has been changed. The record was not in the uploaded file, but was previously selected. Nothing has been changed. Something unexpected happened while processing this record There are other values that may be present for unusual errors. Documentation is available in the User Support Center to describe them all.

3 Refresh data from the WorldCat Registry Several fields used by the WorldCat knowledge base are being retrieved from the WorldCat Registry. These fields are copied into the WorldCat knowledge base and stored forever, so changes will not occur unless specifically requested. In order to update the data, we have added a button to Refresh from Registry which is at the top of the Settings page. Once clicked, a popup window will display showing the exact fields that will be updated and any changes from the previous settings to allow the administrator to confirm or deny the changes. Opac links from the WorldCat Registry Collections that are locally created by a library which contain print records currently allow any URL to be placed on the record. This allows maximum flexibility for the library to define the appropriate linking target for their Opac links. A new feature is available to make creating common types of links, which relies on the Opac linking section of the WorldCat Registry. When creating a new collection the library has the option to specify the type of OPAC Linking on the collection s Properties screen.

4 Setting this value to Manual will allow the library to input any URL value they wish. Setting it to From WorldCat Registry will cause the links to be automatically created using metadata from each record and the settings in the WorldCat Registry. After clicking this button a popup window will display so that the administrator can view their current WorldCat Registry settings. When creating links, the appropriate identifier (if available on the record) will be appended to the Direct to <identifier type> address. If no identifiers are available for the record, the system will fall back to using the URL value on the record.

5 Proxy and provider specific settings per collection Certain libraries with consortial or other complex subscription types have a need to provide different mechanisms for authenticating certain collections or to use different library identifiers when creating links. The library level configuration on the Settings page for proxy information and provider specific settings can now be overridden from each collection s Properties screen. This allows libraries with more complex subscriptions to ensure their patrons have the correct access even in these cases. The setting is collapsed into an Overrides section of the Properties page. When opened, it will display override options for EZProxy, III WAM Proxy, and any appropriate provider specific settings. Here is an example screen from a Galegroup collection: These settings are optional and should only be configured if the library level configuration is not correct for this particular collection. Controls for the Google Scholar feed per collection It is now possible to control whether certain holdings are sent to Google in the Google Scholar feed on a per collection basis. This control is available on every collection s Properties page.

6 By altering this setting the library may choose whether certain collections are appropriate to surface in Google Scholar. Certain libraries may, for instance, choose not to send their print holdings to Google Scholar and instead surface only their electronic subscriptions. LinkScheme per record The LinkScheme value instructs the WorldCat knowledge base how to create article links for a particular record or set of records. For libraries that wish to create one collection with content from multiple, different platforms or where an individual title may require special handling, this setting can now be overridden on a per record basis. The Title Edit screen for any record will display a field that allows the library to set an Override LinkScheme. This value will be used when creating article links for this record instead of the collection level LinkScheme value. The field is optional and should only be used when it is truly necessary. OCLC support staff can assist in picking the correct value to use. A list of all available options can be downloaded from the User Support Center. Enhancements Automated data loads visible in Activity History OCLC does a significant amount of automatic data loading on behalf of the users of the WorldCat knowledge base. Until now, the results of these automated feeds were only visible to the library by checking the live data in the WorldCat knowledge base. In order to keep libraries more informed about the data loads that are taking place and ensure the library has the tools and data necessary to perform a quality check on that activity, all data loads will now show up in the library s Activity History page. The detailed report of the results, mentioned earlier, is available for these types of loads as well. A new field labeled Source will display information about where this feed came from. View/Edit collection level link formula As a result of the need to handle linking with proxy information or provider specific settings, the title level links created by the WorldCat knowledge base are often based on formulae. These formulae instruct the system about the correct way to combine these settings with bibliographic data from a

7 record or from a static formula so that a correct title level URL can be created. This functionality has existed in the WorldCat knowledge base from the beginning, but these fields were only editable by OCLC staff. The values of these fields are now available to all administrators so that they can be created or edited according to the library s needs. The Collection Link Formula displays a collection level field (meaning that it applies to all titles in the collection) that shows the formula the system will use for creating links. This value is editable from the collection s Properties page. An example link is given in the Calculated Title Link Sample field so that the user can test the results of their edits. Additional information is shown on the Title Edit page for any record to assist in the creation of correct title level links. As the above screenshot shows, not all titles have an actual value stored in the URL field. However, they may still have title level links created through this formula based mechanism. The most common formula is **localstem++**url++ which instructs the system to proxy the link if appropriate **localstem++ and to simply use the value of the URL field on the record to create the link **url++. Any part of the formula enclosed in double brackets [[ ]] will be replaced with the corresponding value from the record or from the library s configuration. Commonly used fields include: [[ISSN]] The ISSN from the record [[ISBN]] The ISBN from the record [[localstem]] A proxy prefix (if appropriate) [[url]] The URL value from the record [[galesiteid]] An example of using a configured settings value.

8 Retrieve all content types in the KBART download All possible content types are now returned in the KBART format downloads for every collection as well as the entire library holdings file. The content type value is displayed in the coverage_depth column of the spreadsheet. This allows a library to have full control over their holdings through the upload and download functionality. Note that the oclc_entry_id value is used to condense multiple rows of an uploaded file into a single record. Loading the above dates (all for the same title) with the same oclc_entry_id will result in a single record with all of the dates. Using this mechanism a library can use the download and upload functionality to describe any coverage gaps in their subscription. Previously this was only possible through the user interface. API Enhancements and enhancements to integrated products Collection results sortable by update time Collection level API results have an additional field called updated. Example: <updated> t13:25:09.000z</updated> This field contains the timestamp of when the collection or any of its titles was most recently updated. The results from a collection search can also be sorted by this value by specifying the parameter &orderby=updated. This will sort the dates in descending order (most recent first). In combination with the fact that the API results are in Atom format, this allows clients to keep track of updates to their collections in a similar fashion to the way that an RSS feed works. This sorting mechanism should also be used by any clients wishing to keep a complete set of data in sync instead of periodically refreshing the entire data set. The client needs only to maintain the date of last update to their local data and they can retrieve the changes from that date using the updated time.

9 Two additional parameters updatedmin and updatedmax allow a client to specify a range of dates to retrieve based on the update time. Access to the available scope A new query parameter called scope can be used to control whether results are returned from the library s holdings or from the global knowledge base. A scope value of my will return only results from the library specified in the institution_id field or the one that is associated with the wskey in the request. A scope value of available will instead return results from the global knowledge base (or from collections shared with this library, but not selected). This is the first step to enabling write access to the data in the WorldCat knowledge base. With access to the available scope a client could reproduce the full range of searching options that are available in the administrative user interface. Download titles in this collection A download link for the titles in a collection in KBART format is available through a new link type, indicated by these attributes: rel="enclosure" title="kbart file" This link will download the selected titles that are configured for this library when viewing the record in the my scope. The link will download the available titles from the global knowledge base when viewed from the available scope. This mirrors the functionality of the user interface. Similar to the previous two items, this increases the functionality of the API to allow clients to either replicate functionality available in the user interface or to perform a complete synchronization of a local system with the data in the WorldCat knowledge base. ISBN and collection_user_note in response to an entries query Two fields ISBN and collection_user_note have been added to the response format for queries against the entries in the WorldCat knowledge base. ISBN contains the ISBN on the record and was overlooked in previous releases. Collection_user_note contains the collection level user facing note field so that this value can be displayed alongside title level results in the A to Z list.

10 Bug Fixes Delete coverage and/or enum when not present in the upload file When uploading changed values for dates or enumeration using a KBART formatted spreadsheet, the system was not removing coverage when the fields of the spreadsheet were blanked out. When users attempted to change the dates to blank, or no date, the system would simply ignore this information and not change anything. This was originally done to protect users from inadvertent changes to their holdings. Based on user feedback, this was classified as a bug since this behavior was unexpected. Title IDs with spaces The release notes for our May update included a known issue relating to errors caused by spaces or other unusual characters in the Title ID field (or oclc_entry_id in the KBART file). This field is now validated and controlled much more tightly so that these characters cannot be accidentally included in the field which will prevent several bugs that were caused as a result of the unexpected values. Downloading selected holdings for large collections Certain users reported that they would receive errors when attempting to download their selected records from very large collections. We have revamped the download operation so that these errors no longer occur. As a result of this change, downloading selected titles from any collection is now significantly faster. Known Issues None