Skip to main content
ExLibris

  • Subscribe by RSS
    • 360 KB
    Ex Libris Knowledge Center

    360 KB: PION: Provider Change and PION Historic Archive database and PION Journals database: Database Migration -- May 2016

    1. Last updated
    2. Save as PDF
    • Product: 360 KB

    What happened to the PION Historic Archive and PION Journals databases from provider PION?

    Provider PION is no longer offering certain databases; instead, they are being provided by Sage Publications. PION’s entire publishing portfolio became part of SAGE’s Journal Program.

    Therefore, provider PION has moved titles in PION Historic Archive database (database code QON) and PION Journals database (database code RON) to SAGE Complete A-Z List (database code SFC).

    This change took effect on May 12th, 2016:

    Before May 12th, 2016: PION Historic Archive database (database code QON) & PION Journals database (database code RON)

    After May 12th, 2016: SAGE Complete A-Z List (database code SFC)


    In order to maintain accurate and authoritative provider metadata (based on the Knowledgebase collection policy), all titles have been removed from the databases PION Historic Archive database and PION Journals database in the Knowledgebase on May 12th, 2016. The database became a zero-titles database. (NOTE: The titles are now available in SAGE Complete A-Z List).


    Action you need to take:

    • Once the above change takes effect, update the holdings in your Intota or Client Center profile by subscribing to the new database instead of the old database.  For information on how to update your profile, and considerations prior to removing the old database from your profile:

      • Intota users click here.

      • Client Center users click here.

    • If you are a 360 MARC Updates client and have requested the custom specification that adds the provider name as it appears in the Client Center/Intota to MARC records, you can expect to see some change records when you get your MARC records after May 12th, 2016.

    • If your library uses a third-party service (such as SFX, EBSCO A-Z, etc.), custom scripts to manage data, or other non-ProQuest tools that require the provider name to function, you should note the change in ProQuest's provider name in order to retain the proper relationship/mapping between those tools.

     

    • Date Created: 29-Apr-2016
    • Last Edited Date: 18-May-2016
    • Old Article Number: 13820