360 KB: Oxford Journals Databases from Oxford University Press: Database Name Change -- July 2017
What is happening to the name of Oxford Journal databases?
New Databases | Database Name Changes
Oxford University Press has changed their sales model of their Oxford Journal collections. In addition to the subject front file, subject back file, and A-Z lists, Oxford have changed to an annual representation. We will be representing Oxford Journal collection as they do in the KBART title lists represented here:
https://academic.oup.com/journals/pa...brarians/kbart
This means that we will be or have already creating new databases and will be changing the names of existing databases in order to reflect Oxford's new model.
New Databases
Starting with 2016, Oxford University Press is representing their journal collections as annual. We have created new collections to reflect 2016. The collections for 2017 will be described in the Database Name Changes section below. In January 2018, we will create new Oxford Journals for those clients wishing to subscribe and advance to the new annual collections.
Linked below is a list to help you identify the new 2016 collections and some of the new 2017 collections we did not have previously:
NewOxfordJournal_Databases.xlsx
Actions you need to take (360 Core, Resource Manager, Counter, Link, or Intota clients):
- You may need to update the holdings in your Intota or Client Center profile by subscribing to the new databases, as applicable to your Oxford subscription. If you have any questions regarding your subscription packages for Oxford Journals, please contact your Oxford representative.
Below is a list of database name changes:
OxfordJournal_DatabaseNameChange.xlsx
Date of change: July 12, 2017
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 July 12, 2017.
- 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 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: 12-JUN-2017