Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
sfx_renewals [2019/06/26 10:48]
jmulvaney [eJournal Package Renewals]
sfx_renewals [2020/03/06 11:35] (current)
jmulvaney
Line 5: Line 5:
   * UMass Amherst Library [[https://​sfxhosted.exlibrisgroup.com/​umass | SFX URL]].   * UMass Amherst Library [[https://​sfxhosted.exlibrisgroup.com/​umass | SFX URL]].
   * [[https://​docs.google.com/​spreadsheets/​d/​1aC8MqoWM4bzc278Z02SLqbqV-1fs46yoxjHIVowoWL0/​edit?​usp=sharing|CORAL Glossaries]] What the termins in CORAL mean, and how UMass is using it.   * [[https://​docs.google.com/​spreadsheets/​d/​1aC8MqoWM4bzc278Z02SLqbqV-1fs46yoxjHIVowoWL0/​edit?​usp=sharing|CORAL Glossaries]] What the termins in CORAL mean, and how UMass is using it.
-  * Ask Judy for access the the Publisher-Platform Changes ​Tracking Sheet, and the E-Journal, Package Changes: Acquisitions to Access sheet.+  * Ask Jack for access the the eResource ​Platform ​and URL Changes ​for, and ask Judy for access to the E-Journal, Package Changes: Acquisitions to Access sheet.
  
 **Also See:** **Also See:**
Line 203: Line 203:
 ==== Platform Changes ==== ==== Platform Changes ====
 It is not always clear when and where a platform change occurs, often it isn't announced and either Judy or Nancy or someone in DRMS will notice it by chance. It can often come up in the SFX change reports, or in the KB updates. Platform changes vary from a switch from HTTP to HTTPS, a journal moving from High Wire to a publisher platform, or a database migrating their interface resulting in URL changes that cascade to all of our systems. It is not always clear when and where a platform change occurs, often it isn't announced and either Judy or Nancy or someone in DRMS will notice it by chance. It can often come up in the SFX change reports, or in the KB updates. Platform changes vary from a switch from HTTP to HTTPS, a journal moving from High Wire to a publisher platform, or a database migrating their interface resulting in URL changes that cascade to all of our systems.
-  * When you find that a platform change is about to occur, or has already occurred, ​put it in the Publisher-Platform Changes ​Tracking in Google Sheets. +  * When you find that a platform change is about to occur, or has already occurred, ​fill out the eResource ​Platform ​and URL Changes ​form.
-      * Start with the name of the resource. +
-      * Put what the current platform is, and where it is moving too. +
-          * When is the new platform available? When does the old platform shut down. +
-      * If you know what changes are being made in terms of URLs, make the change in CORAL and leave a note in the sheet. +
-          * Same with the Holdings Record in Aleph +
-      * If the proxy needs to be changed coordinate with Scott. +
-      * Leave any notes about the process and how it will affect SFX +
-          * Usually this means leaving notes that nothing has changed, linking is broken, a Support Case (SC) or KB change request is in process, etc. +
-      * If the resource requires the attention of a Batch-loader,​ let Mary Ann and Jennifer know! +
-      * Leave any additional notes in the sheet, the Target Service, or in CORAL is needed +
  
  
 //​[[jmulvaney@library.umass.edu|Primary contact: Jack Mulvaney]]//​ //​[[jmulvaney@library.umass.edu|Primary contact: Jack Mulvaney]]//​
sfx_renewals.1561560524.txt.gz · Last modified: 2019/06/26 10:48 by jmulvaney
[unknown link type]Back to top
www.chimeric.de Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0