What is happening to the title URL linking syntax of ProQuest databases?
Update November 2017: Literature Online (LION) databases are using a stable OpenURL Gateway linking syntax in the KB, which requires the regular HTTP protocol. Therefore, we are converting LION databases back to the regular HTTP protocol in the 360 KB.
Update October 2017: The database and title URL changes to HTTPS have been completed for databases under provider ProQuest.
The provider ProQuest is in the process of updating their linking to HTTP secure (HTTPS) for many ProQuest databases. For more information on this from ProQuest, please see ProQuest Support for HTTPS at the ProQuest Support Center. Please note that, as per ProQuest, “If you cannot make the changes until after the official cutover, the system should automatically redirect to HTTPS.” Therefore, redirects will continue for 360 KB database and title URLs.
We will be gradually changing the database and title-level linking for databases under provider ProQuest (provider code: PRVPQU) from HTTP to HTTPS in the Knowledgebase starting on June 20, 2017. Aside from regular updates based on ProQuest title lists, the content of the ProQuest databases will remain the same. Regarding databases related to ProQuest but under separate providers in KB, such as Ebook Central and Alexander Street Press, we are working with these providers on their timelines to switch to HTTPS, and this article will be updated with more information as we have it.
The 360 KB URL changes for databases under provider ProQuest (provider code: PRVPQU) are estimated to be completed by the end of Summer 2017, but please keep in mind that, for consortia-specific databases, we rely on consortia to send updated title lists on various schedules, so these updates may take longer (360 KB: ProQuest Consortia-Specific Databases: Collection Policy).
These database and title URL changes will begin taking effect in June 2017, with an estimated completion date of July/August 2017:
Actions you may need to take:
- If you are a 360 MARC Updates client and have requested the custom specification that adds direct URLs to MARC records, you can expect to see some change records when you get your next MARC records.
- Make sure that https is included in your proxy configuration as soon as possible.
- Article last edited: 13-June-2017