Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
perpetual_access_procedures [2019/01/15 13:32]
cknapp [Perpetual Access Procedures & Codes]
perpetual_access_procedures [2022/01/14 13:00]
jmulvaney [Perpetual access process]
Line 1: Line 1:
 ====== Perpetual Access Procedures & Codes ====== ====== Perpetual Access Procedures & Codes ======
  
-UMass policy for tracking and maintaining perpetual access is as follows (as of 10/24/18): +UMass policy for tracking and maintaining perpetual access is as follows (as of 01/14/2022): 
-  * Cancellations of individual ​subscriptions:​ Do not set up PA. A cancelled publication is not deemed critical to support academic work at UMass. +  * Cancellations of individual subscriptions:​ Mostly we are not retaining PA access but if publisher is known to retain PA, exceptions can be made. Many publishers are not reliably retaining PA access long-term. 
-  * Transferred titles from package ejournals: Do not set up PA access EXCEPT for Springer, Wiley and Elsevier. Elsevier and Springer autoload maintains these titles in SFX, although Springer is still being tested and backup targets are being maintained (1/2019). A Wiley autoload request has been sent to ExLibris.  +      * Publishers who have retained PA relatively reliably are: Cambridge, Taylor & Francis, De Gruyter, Wiley, Elsevier, Springer. 
-  * Individual ​subscriptions:​ Mostly we are not retaining PA access but if publisher is known to retain PA, exceptions can be made. Many publishers are not reliably retaining PA access long-term ​(e.g. Sage, OVIDCambridge), and the volume ​of titles ​migrating between publishers is increasing.  +      * Publishers who have NOT retained PA reliably are: Sage, OvidOxford. 
-  * Aleph PA recordsA cleanup project was completed by a student in 1/2019. If PA access was not available in SFX, order records were changes ​from PA to CLS. PA order records are no longer being added to Aleph. ​ +  * Cancellations ​of Packages/​Databases:​ If the licenses allows for PCA, keep content activated. 
 +      * Transferred ​titles ​from package ejournals: Do not set up PA access EXCEPT for Springer, Wiley, and Elsevier. The Elsevier and Springer entitlements KBARTS include PA, these will be loaded to HLM
 +  * Aleph PA recordsA cleanup project was completed by a student in 1/2019. If PA access was not available in SFX, order records were changed ​from PA to CLS. These titles were migrated to HLM. PA order records are no longer being added to Aleph and will not be migrated to FOLIO.
 ==== Perpetual access process ==== ==== Perpetual access process ====
- 
-  * SFX maintenance of PA for Springer, Wiley and Elsevier titles. 
-     * Elsevier uses autoload which includes all perpetual access content. 
-     * Springer uses autoload which includes all perpetual access content, although other targets are being maintained until testing is completed (1/2019). 
-     * Wiley uses 2010 FULL COLLECTION, DATABASE MODEL (previous years), or WILEY ONLINE LIBRARY JOURNALS targets for PA. Change the SFX date threshold and add an Internal Description note in the format "PA to (dates of access)."​ Internal notes are now exportable. 
   * EDS maintenance of PA for Springer, Wiley and Elsevier titles.   * EDS maintenance of PA for Springer, Wiley and Elsevier titles.
-     * Springer ​and Wiley are paid to EBSCO so PA should ​be maintained by EBSCO+     ​* ​Entitlements KBARTS for Elsevier & Springer ​will include PA for HLM upload. 
-     ​* ​Elsevier ​is maintained ​in HLM by uploading the SFX Elsevier autoload regularly, which should ​maintain PA. +         * Springer is paid to EBSCO which should ​allow SmartLinks+ to work to some extent for PA titles still recorded in EBSCONet from previous sub. years
 +     ​* ​Individual title transfers are not being tracked as closely anymore and may become out of sync for some providers. 
 +         * In cases where a new package ​is created every year this should be less obvious ​in HLM than it was in SFX. In cases where a package is re-used it should ​be caught by the review.
  
-//[[cknapp@library.umass.edu|Primary contact: ​Catherine Knapp]]//+//[[jmulvaney@library.umass.edu|Primary contact: ​Jack Mulvaney]]//
  
  
perpetual_access_procedures.txt · Last modified: 2022/01/14 13:00 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