Cataloging E-Resources: Remote Access Record Customizations

Introduction

In July 2020, Yale University Library implemented the use of EZproxy to provide remote access to most of our library licensed e-resources. With the addition of this new remote access option, ERSM has created the following guidelines for catalogers so that they can create or update records in a way that is consistent with new practices required for remote access.

If you are cataloging a new licensed e-resource and you did not acquire it through ERSM workflows, please notify ecollections@mailman.yale.edu so that staff can properly configure proxied access if needed.

For all licensed e-resources:

If a licensed e-resource will be proxied, add the following:

  1.  Append Yale’s EZproxy prefix to the front of the e-resource URL in the 856 $u
    a. Proxy prefix: https://yale.idm.oclc.org/login?URL=
    b. Example of prefixed URL: https://yale.idm.oclc.org/login?URL=https://www.jstor.org/
    c. Use the prefix URL exactly as noted above, including the “=” symbol; do not put any spaces between the prefix and the e-resource URL.
  2.  Insert a 953 $a (indicators = blank) with the original, unproxied e-resource URL
For e-resources in the Databases A-Z list only:
  1.   Identify the type of remote access required for the e-resource (for help, contact ecollections@mailman.yale.edu):
      a. EZproxy (VPN secondary)
      b. Institutional username and password
      c. Personal account
      d. On-site use only; no remote access allowed
      e. Yale single sign-on (Shibboleth)
      f. Yale Central Authentication Service (CAS)
      g. VPN only
      h. No remote access authentication required (open access, freely available, locally hosted materials on Yale servers)
  2.   If remote access method matches any of the situations above, select relevant 590 Local Note from MARC Record Stock Phrases for E-Resources. Resources that do not require remote access authorization do not require this 590 local note.
  3. The new remote access 590 local note field should be placed as the first 590 local note field in the record, above all others.