Doorgaan naar de website
OCLC Support

Automatic Holdings Feed

  1. Laatst bijgewerkt
  2. Opslaan als pdf
Find information about the Activity History for Automatic Holdings Feeds in Knowledge base collections.

Find details about Automatic Holdings Feeds

To find details about Automatic Holdings Feeds:

  1. Navigate to Collection Manager Search.
  2. Choose Activity History as the Data Type.
  3. Select My Institution's History as the Scope.
  4. Leave the search box blank. 
  5. Click Search.
  6. At the top of the screen, select the Loads & Feeds filter. From the drop-down menu that appears, choose Automatic Holdings Feed.
  7. Click Filter.
  8. In the search results, click the load or feed of interest to see details about the specific load or feed.
    • Automatic Holdings Feeds are preceded by a Provider Data Load.
  9. Click on Title Changes.
    • To download a report, click on the Download Detailed Report button.

Activity History search results

Automatic Holdings Feeds are data loads for providers that work with OCLC to offer automatic collection loading and maintenance for their knowledge base collections. Automatic Holdings Feeds contain data specific to each library. The feeds have your library's specific subset of titles. The data is dynamic or changes over time as your library purchases titles, modifies subscriptions, or as titles are triggered for purchase.

In the Activity History, when you see an Automatic Holdings Feed, there will be a previous Provider Data Load activity with the same Update Source. It is typical that the feeds appear within one to three days of each other. For a complete vision of what changed for your library, view both activities.

The process OCLC uses to load Automatic Holdings Feeds

The high-level process OCLC uses to load Automatic Holdings Feeds is as follows. This information will help you understand what you see in the Activity History:

  1. The provider sends OCLC refreshed data at a regular, agreed-upon time. The data includes:
    1. Provider data to update the global collections and titles, and
    2. Library-specific data or "holdings" information, such as the unique titles each library owns and for some providers, the unique coverage ranges.
  2. OCLC verifies, normalizes, and loads the provider data to update the global knowledge base.
  3. Typically one to three days later, as soon as the global data has been updated, OCLC loads the library-specific holdings information.

Title Changes page(s)

Depending on the provider, the Automatic Holdings Feed Title Changes page will have different information.

For some providers with automatic feeds, the Title Changes page always will only include your unique title selections and deselections. When providers send title data specific to your library, it is often the unique title list that your library owns, and new titles are included and automatically selected as you purchase new titles. Coverage values are global values because they do not vary per library. If those values are updated, they will show in the Provider Data Load activity that shows global changes. For example, Automatic Holdings Feeds from The U.S. Government Publishing Office (GPO) include unique title selections for your library.

For some providers, coverage data can vary per library. Thus, the Title Changes page could include title updates that are counted as Local Edits. This simply means that the provider offers the title with different coverage ranges and that the coverage your library purchased is unique from the global value.

Download a detailed report

Automatic Holdings Feeds have a downloadable report option. Find the Download Detailed Report button at the top of the Title Changes page.

This report will contain titles from a Automatic Holdings Feed. Each title will have a value populated in the RESULT column describing the way the title was processed if it was selected, updated, and so forth. Only one result will be listed for each title. Thus, if a title was selected and it had unique coverage, the result would be selected, even if the action is covoverlay.