What is happening to the databases from provider Canadian Electronic Library?
Some databases are incorrectly attributed to the provider Canadian Electronic Library.
Therefore, we will be changing the provider associated with several databases in 360 Knowledgebase.
This change will take effect on May 31, 2018:
- Before May 31, 2018: Canadian Electronic Library
- After May 31, 2018: Ebrary
This will affect the following databases:
|DB Code||Database Name||Provider Before May 31, 2018||Provider After May 31, 2018|
|3AN||CEL Perpetual||Canadian Electronic Library||Ebrary|
|JIV||Canadian Health Research Collection||Canadian Electronic Library||Ebrary|
|JIW||Canadian Publishers Collection||Canadian Electronic Library||Ebrary|
|JIY||Canadian Public Policy Collection||Canadian Electronic Library||Ebrary|
|B1C||Canadian Publishers Collection - CRKN||Canadian Electronic Library||Ebrary|
|ACJRN||OCUL Canadian Publishers Collection||Canadian Electronic Library||Ebrary|
|N7Y||Canadian Publishers Collection - non-CRKN||Canadian Electronic Library||Ebrary|
|3AW||Bibliothèque Numérique Canadienne Française||Canadian Electronic Library||Ebrary|
|C8S||Ulysses Travel Guide Library||Canadian Electronic Library||Ebrary|
|C8N||Orca Digital Collection||Canadian Electronic Library||Ebrary|
Action you need to take:
- If you are a 360 Resource Manager or 360 Counter client and you have information attached to the old provider that also pertains to the new provider (such as license information), you can attach the information to the new provider in the same way they were attached to the old provider. See information about Attaching Resources and Licenses:
- 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 to MARC records, you can expect to see some change records when you get your MARC records after May 31st, 2018.
- 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 provider name to function, you should note the change in provider name in order to retain the proper relationship/mapping between those tools.
- Article last edited: 11-May-2018