- Product: 360 KB
What is happening to the ebrary subject collections?
The ebrary subject collections that clients have traditionally subscribed to in the Knowledgebase have been retired. These "old" ebrary subject collections have been replaced by "new" subject collections from ebrary.
In order to maintain accurate and authoritative provider metadata (based on the Knowledgebase collection policy), the old ebrary subject collection databases will be hidden in the Knowledgebase on April 15th, so that only current subscribers can view them in the Client Center. The old ebrary subject collections will be considered defunct collections and will not be updated or maintained in the Knowledgebase after April 15th.
To get access to active and regularly-updated ebrary subject collection content, we recommend that clients subscribe to the new ebrary subject collection databases. You can find a spreadsheet that lists the old ebrary subject collection database names and database codes, along with the new ebrary subject collection databases clients should subscribe to instead here. Please note that the old ebrary subject collections will also have their database names changed on April 15th to include the phrase "Legacy Collection."
If you do not see a new ebrary subject database included on the spreadsheet that you would like represented in the Knowledgebase, please contact ebrary customer support at email@example.com
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:
- If you are a 360 MARC Updates client and have requested the custom specification that adds direct URLs or database specific information to MARC records, you can expect to see some change records when you get your MARC records after April 15th.
- 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.
- Date Created: 26-Mar-2015
- Last Edited Date: 26-Mar-2015
- Old Article Number: 12543