Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    360 KB: Early English Books databases from Chadwyck-Healey : Database Name Change -- August 29, 2019

    What is happening to the names of Early English Books databases?

    Early English Books databases from the provider Chadwyck-Healey will be supported under ProQuest. Existing Early English Books databases from the provider Chadwyck-Healey will have "Legacy" added to the database names to indicate their archive status. 

    Therefore, we will be changing the database names in the Knowledgebase. The content of the database, and the database IDs, will remain the same.

    This change will take effect on August 29, 2019:

    • Before August 29, 2019:
    Database Code Database Name
    ITP Early English Books I (Pollard and Redgrave, STC I), 1475-1640
    ITR Early English Books II (Wing, STC II), 1641-1700
    BHS Early English Books Online
    BBWEO Early English Books Online -Licence Nationale
    ISW Early English Books Thomason Tracts
    IRU Early English Books Tract Supplement
    • After August 29, 2019:
    Database Code Database Name
    ITP Early English Books I (Pollard and Redgrave, STC I), 1475-1640 (Legacy)
    ITR Early English Books II (Wing, STC II), 1641-1700 (Legacy)
    BHS Early English Books Online (Legacy)
    BBWEO Early English Books Online -Licence Nationale (Legacy)
    ISW Early English Books Thomason Tracts (Legacy)
    IRU Early English Books Tract Supplement (Legacy)

     

     

    Actions you may need to take:

    • If you are a 360 MARC Updates client and have requested the custom specification that adds the database 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 August 29, 2019.
    • If your library uses a third-party service (such as EBSCO A-Z, etc.), custom scripts to manage data, or other non-ProQuest tools that require the database name to function, you should note the change in ProQuest's database name in order to retain the proper relationship/mapping between those tools.

     


    • Article last edited: 29-Aug-2019
    //Feedback