Skip to main content

CDL Conventions for Cataloging Electronic Resources

Originally created by the SOPAG Electronic Resources Cataloging Task Force in 1999

Revised March 2003 by Becky Culbertson

Revised November 2008 by SCDPP WG

Revised September 2009 by Renee Chin

Revised March 2019 by SCP and approved with minor revision July 2019 by SCP-AC

Revised February 2024 by SCP and approved with minor revision by SCP-AC

The Shared Cataloging Program (SCP) is responsible for creating the “official” CDL records that are shared with the campuses via UC Library Search (Primo VE). The SCP adheres to national standards for cataloging CDL resources, with additional fields and suggested wording to aid in consistent presentation and clustering in the Alma Network Zone and UC Library Search. Name and series access points should conform to the forms found in the LCNAF or, if not available, SCP may establish according to RDA and LC-PCC Policy Statements. Content designation should conform to the MARC 21 Format for Bibliographic Data, as implemented by OCLC. LC classification, LCSH, and MeSH are required where appropriate. For batch cataloging, it is not required to upgrade the descriptive information to conform to RDA and records may not comply with full level cataloging standards. This does not apply to one-by-one cataloging or original records. Authorized access points and accurate tagging are used when accepting description and choice of access points found on existing records. Accurate content designation and cataloging consistency are especially important to facilitate migration to a successor system.

Campuses should, however, make local changes as needed to accommodate their local system specifications in their local catalog (the Alma Institution Zone).

Bibliographic records provided by the Alma Community Zone are not governed by the CDL Conventions outlined here unless replaced by CDL OCLC bibliographic records.

Contents

  1. Electronic serials
  2. Electronic monographs
  3. Electronic Integrating Resources

1. Electronic serials

As of April 1, 2019, SCP catalogers should use the separate record approach for cataloging electronic serials. Whenever possible, serial records should be cataloged according to RDA, the CONSER Cataloging Manual, (including Module 31 (Remote Access Computer Files)), the CONSER Standard Record cataloging guidelines, and the PCC Provider-Neutral cataloging guidelines. Latest entry MARC records [i.e. 008/34 “1”] are not used.

The table below outlines the elements that should be present in the SCP record. For information about which elements to include in the OCLC master record, refer to the CONSER Documentation linked above.

For batch or minimal level cataloging, each package is different; catalogers may not look at or include all fields listed, especially when cataloging groups of vendor records. As a result, the 1XX/7XX entries may not always have the correct forms, 050 and/or 6XXs may not always present. However, these may be upgraded later due to OCLC WorldCat updates and/or error report via CDL Helpline.

Electronic Serials

MARC tag Separate record Notes
Fixed fields Code the fixed fields per national standards.  
001 and 035 (Unique and permanent numeric or alpha-numeric record ID numbers for record output)

OCLC numbers are automatically generated in the 001 and 035 fields upon export.

 

Example:

001  46763253

035   $a (OCoLC)46763253

 

006 (Additional material characteristics)

Add if lacking.  Required only to code the first byte (e.g., 006  m). Most serials that are textual have this 006:  

006  m     o  d     

It is possible to have multiple 006 fields.  For example, a digital atlas serial is coded in the 008 field as cartographic material with a 006 field for computer file and a 006 field for serial.
007 $a $b (Physical description)

Add if lacking. Note that only $a and $b are required. 

Example:

007   $a c $b r

 
022 (ISSN) Accept as is but if it is a print ISSN, move it to $y. If an ISSN needs to be added as a result of SFX idiosyncrasies, record the ISSN in 022 $y. Never add a qualifier to an ISSN. Often it is necessary to verify format information in the ISSN Portal.  A frequent combination is an e-ISSN in subfield $a and a print ISSN in subfield $y.
040 (Cataloging source)

Add $e rda following $b eng if upgrade to RDA. 

Add $e pn if lacking.

 
041 (Language code) Accept as is, or add if applicable. Pair with a 546 field if applicable.
050 (LC call number) If lacking, add a LC classification number (050 14 $a for CONSER records and 050 _4 $a for non-CONSER records). No need to supply the book (cutter) number.

For newspapers, use classification number “AN”. LC classification not required for CalDocs.

Classification numbers are optional for Minimal level cataloging

086 (CalDocs call number)

Add if available (CalDocs only) suffixed by “Online”.

Example:

086   $a L960.T42 $2 cadocs Online

or

086   $a L960.T42 Online

 
130 (Uniform title main entry) Accept as is. Remove “(Online)” if present.  
210 (Abbreviated title) Supply only if abbreviated title for online format is available. Delete if it applies to the print version. If there is no online ISSN, you may add the print abbreviated key titles with the indicators, “10” 
222 (Key title) Supply only if key title for online format is available. Delete if it applies to the print version.  
245 $a (Title proper) The title proper should be the one that appears on the preferred source. If using Description based on print version record (588 “Description based on” note), it should be the same as the 245 on the print record.  
245 $b (Remainder of title) Accept as is.  
245 $n & $p (Number & name of part/section) Accept as is.  
245 $h (General material designation) Remove $h [electronic resource] if present.  
246 (variant title, title added entries) Use 246 for variants of the electronic title.

246 1_ $i Available from some providers with title: $a …

246 1_ $a all other variant titles

260/264 (Place of publication, publisher, and date) Accept as is.

If 264 $a and $b are impossible to determine, use $a [Place of publication not identified] : $b [publisher not identified]

Supply a probable place of publication if possible rather than give “[Place of publication not identified].”

300 $a (extent of publication) Use “1 online resource” in $a. If a serial is ceased, record the number of volumes if known. 

Example for ongoing serials 

300   $a 1 online resource (volumes)

Example for ceased: 

300   $a 1 online resource (5 volumes)

  Do not use $c.
310/321 (Frequency) Accept as is.  
336 (Content type) Add if lacking.  
337 (Media type) Add if lacking.  
338 (Carrier type) Add if lacking.  
362 (Numbering) Accept as is.  
440/490/830/890 (Series)

Follow PCC guidelines for series and verify all series. Delete if an aggregator name has been treated as a series title.

Delete (Online) qualifier as appropriate.

Example:

830 _0 $a Developer’s notebook series (Online).

 
500/550 (Provider notes) Delete online package/provider names.  
506 (Access restriction note)

Delete. Unless used for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects.

Follow PCC guidelines for open access titles.

 
515 (Numbering peculiarities) Record as needed.  
516 (Type of computer file or data) Delete.  Retain only if unusual format (e.g., need special Chinese software to read).  Delete any “Text (electronic journal)” notes.  
530 (Additional physical form) Prefer 776 $i. However, do not delete if present.

Examples of 530 notes:

Also issued online.

Also issued in print.

Also issued on microfilm and online.

533 (Reproduction note) Delete. Unless used for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects.  
538 (System details note) Delete Unless used for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects.  
546 (Language note) Accept as is, or add if applicable.  If recorded, also add 041 $a.  
583 (Action note) Delete. Unless used for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects.  
588 0_ (DBO/Title source note)

If there is a 588, accept as is with “Description based on” spelled out. 

If you are redescribing, however, use 588 0_ and remove the “Description based on” phrase. 

Example:

588 0_ $a Print version record.

Optionally change 500 field for DBO to 588 0_

Add if lacking

The wording of notes is left to the cataloger’s judgment.

Catalogers are strongly encouraged to accept the wording found in copy cataloging if it is clear and succinct. Do not strive for consistency.

588 1_ (Latest issue consulted note)

If there is a 588, accept as is with “Latest issue consulted”  spelled out.  If you are redescribing, however, use 588 1_ and remove the “Latest issue consulted” phrase

Example:

588 1_ $a Vol. 12 (2023). 

If there is only a 588,  accept it as is, unless redescribing. If you are redescribing, then record the latest issue consulted if lacking.
Example:

588 1_ $a Vol. 5, no. 1 (January 1995) (OCLC FirstSearch, viewed January 10, 1998).

Ignore the phrase “Description based on” and “Last issue consulted” if they are in the record, unless redescribing. If not there, then use 588 0_ for “Description based on” and 588 1_ for “Latest issue consulted”
650 (LCSH) With the exception of some newspapers and general subject journals, assign at least one LCSH.  
650 (MeSH) If easily ascertainable, assign at least one MeSH heading for biomedical electronic titles.  
655 (Genre/form heading)

Accept as is.

 
7XX (Added entries) Add 7XX if applicable. Delete 7XX fields for providers. Add $e relationship designator if available
773 (Host Item Entry) Do not use. Remove if found on copy.  
776 (Additional Physical Form Linking Entry)

Add 776 $i for the print version and/or other format using “Insert from cited record” macro command; if it lacks OCLC number, provide $t [title]. $z ISSN if available.

Add if applicable, even if only to provide $t. Add $a (main entry heading) if appropriate. Use $i in lieu of 530 note to describe the physical format being linked per the CONSER standard record cataloging guidelines.

Examples:

776 08 $i Print version: $t European heart journal $x 0195-668X $w (DLC)sn 79009215 $w (OCoLC) 5585193

776 08 $i

Microform version: $t American journal of international law $x 0002-9300 $w (DLC)sf 84019125 $w (OCoLC)6661469

76X-78X (Linking fields) Record as needed (fields other than 776).  
856 $3 (Coverage info)

The coverage/holdings information in the 856 $3 should reflect the numerical designations of the title being cataloged (i.e., coverage in the 856 $3 should generally parallel the 588 DBO. Record the coverage information using the NISO level 3 (modified level 4 detailed) holdings standard. In modified level 4 detailed holdings, the whole volume and year is recorded when coverage begins with issue 1 of that volume [e.g., v.1:no.1(2005:Jan.) is recorded as v.1(2005)] or ends with the last issue of the ending coverage [e.g., v.12:no.12(2005:Dec.) is a complete volume, therefore, record as v.12(2005)]. “Detailed holdings” [i.e., volume:issue number(year:month)] are recorded when the beginning volume does not begin with issue 1 or when the ending volume is incomplete.

Example:

856 40 $3 v.29(2013)- $u http://www.ncbi.nlm.nih.gov/pmc/journals/2910

Do not record gaps in coverage.

If needed to use 856 to create a portfolio in Alma, will change $3 to $z to bring coverage information into portfolio as a public note.

856 $u (Electronic access

& location)

Use URLs found in the OCLC WorldCat record if it is generic. Add if lacking. If campus-specific authenticated URLs are required for access, contact CDL to create an interim screen. Add a persistent URL in $u. Some types of persistent URLs utilized by SCP: 

DOIs

GPO PURLs

Digital Archive Links (DALs) Archival Resource Keys (ARKs)

See: SCP cataloging and linking guidelines

Do not add links for related websites (856 42).

As URL syntaxes are subject to change without notice, always consult the CDL eresources tracking page to verify the type of URL to be used and how to construct URLs for each package.

When URL domain changes, request to update it on the CDL eresources tracking page.

930  (Local added entry)

Add at least one 930 field for every 946 field in a record (NOTE: An 946 for a title in DOAJ may have more than one corresponding 930 field). 

Examples: 

930 0_ $a Project Muse online journals 

930 0_ $a Open access resource; selected by the UC Libraries. DOAJ

For a list of authorized title entries (930 $a), consult the CDL eresources tracking page.

For detailed instructions on how to set up 930 $a, refer to Guidelines for Setting up 930/973 $a and Local Collections for electronic resources.

946 (Electronic access & location)

After updating OCLC WorldCat record and before exporting, copy 856 40 to a new field with a tag of 946 40

If with PIDs, change to native URLs

 

back to top

2. Electronic Monographs

SCP catalogers should use the separate record approach for cataloging electronic monographs. Monographic records should be cataloged according to RDA, BIBCO Standard Record cataloging guidelines and PCC Provider-Neutral cataloging policy. Create an original record for the electronic version if one does not exist, or choose the separate record that fits your version, and edit it according to the table below. If you are adding a second access point, add it to the local record and add it to the OCLC WorldCat record.

As of August 1, 2009, SCP catalogers have also been upgrading the descriptive information in the OCLC WorldCat records for e-monographs to make them provider-neutral compliant.

The table below outlines the elements that should be present in the SCP record. For information about which elements to include in the OCLC WorldCat record, refer to the BIBCO documentation linked above.

For batch cataloging, each package is different; catalogers may not look at or include all fields listed, especially when cataloging groups of vendor records. As a result, the 1XX/7XX entries may not always have the correct forms, 050 and/or 6XXs may not always present. However, these may be upgraded later due to OCLC daily updates and/or error report via CDL Helpline.

Electronic Monographs

MARC tag Separate record Notes
Fixed fields Code the fixed fields per national standards.  
001 and 035 (Unique and permanent numeric or alpha-numeric record ID numbers for record output) OCLC numbers are automatically generated in the 001 and 035 fields upon export.

Example:

001  46763253

035   $a (OCoLC)46763253

006 (Additional material characteristics)

Add if lacking. Required only to code the first byte (e.g., 006  m). Most are:  

006  m     o  d

 
007 $a $b (Physical description)

Add if lacking. Note that only $a and $b are required.

Example:

007   $a c $b r

 
020 (ISBN) Accept as is. Input e-ISBNs in $a and print-ISBNs in $z.  
040 (Cataloging Source)

Add $e rda following $b eng if upgrade to RDA. 

Add $e pn if lacking.

 
041 (Language code) Accept as is, or add if applicable. Pair with a 546 field if applicable.
050 (LC call number) Accept as is, or add if applicable.  
086 (CalDocs call number) Accept as is. Add if available (CalDocs only)  
100/110/111/130 (main entries) Accept as is Add $e relationship designator if available
245 $a (Title proper) The title proper should be the one that appears on the preferred source.  If using Description based on print version record (588 “Description based on” note), it should be the same as the 245 on the print record.

Prefer source of title proper in this order:

DBO print

PDF title page

HTML title page

245 $b (Remainder of title) Accept as is.  
245 $n & $p (Number & name of part/section) Accept as is.  
245 $h (General material designation) Remove $h [electronic resource] if present.  
246 (variant title, title added entries)

Leave existing 246s but change them as common sense dictates.

Example: Added title entry for spine title on print version transferred to DBO print record. (print record) 246 18 $a Handbook of chemistry

change to: (PN record) 246 1_ $a Handbook of chemistry

246 1_ $i Available from some providers with title: $a …

246 1_ $a all other variant titles

246 31 $a parallel titles 

260/264 (Place of publication, publisher, and date) In most cases, the place, publisher, and date of publication given will be that of the print.

If 264 $a and $b are impossible to determine, use $a [Place of publication not

Identified] : $b [publisher not identified].

Supply a probable place of publication if possible rather than give “[Place of publication not identified].”

300 $a (extent of publication)

Use “1 online resource” in $a (add subunits and duration, if applicable, in parentheses).

Single volume example:

300   $a 1 online resource (xi, 584 pages)

Multiple volumes example:

300   $a 1 online resource (5 volumes)

$b example:

300   $a 1 online resource (28 page) : $ b illustrations,  maps

Do not use $c.
336 (Content type) Add if lacking.  
337 (Media type) Add if lacking.  
338 (Carrier type) Add if lacking.  
440/490/830/890 (Series)

Follow PCC guidelines for series and verify all series. Delete if an aggregator name has been treated as a series title.

Delete (Online) qualifier as appropriate.

Example:

830 _0 $a Developer’s notebook series (Online).

 
500/550 (Provider notes)

Delete aggregator-specific notes if present.

Example: remove

500   $a Issued as part of Safari Books Online.

 
504 (Bibliography, Etc. Note) Accept as is, or add if applicable.  
506 (Access restriction note)

Delete. Unless used for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects.

Follow PCC guidelines for open access titles.

 
516 (Type of computer file or data) Delete if present.  
530 (Additional physical form) Prefer 776 $i. However, do not delete if present. 

Examples of 530 notes: 

Also issued in print. 

Also issued on microfilm and print.

533 (Reproduction note) Delete. Unless used for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects.  
538 (System details note) Delete. Unless used for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects.  
546 (Language note) Accept as is, or add if applicable.  If recorded, also add 041 $a.  
583 (Action note) Delete. Unless used for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects.  
588 0_ (DBO/Title source note)

Accept as is, unless redescribing. If information is derived from the print version record, use:

588 0_ $a Print version record.

If editing is necessary, record an explicit indication of the provider in the title source: 

588 0_ $a Online resource; title from copyright page (Safari, viewed April 14, 2008).

Add if lacking.

The wording of notes is left to the cataloger’s judgment. Catalogers are strongly encouraged to accept the wording found in copy cataloging if it is clear and succinct.
650 (LCSH) Assign at least one LCSH.  
650 (MeSH) If easily ascertainable, assign at least one MeSH heading for biomedical electronic titles.  
655 (genre/form heading) Accept as is.  
7XX (Added entries) Add 7XX for an issuing body if applicable. Delete 7XX fields for providers. Add $e relationship designator if available
710 (Added entry— corporate name)

Do not add 710 for digitizers or providers. Delete if present.

Example: Not to add or remove

710 2_ $a Safari Books Online (Firm)

For CalDocs only: Add corporate name entries for private companies that share responsibility with the government agency for the publication.

Examples:

710 2_ $a California Energy Commission. $b Assessments Division, $e issuing body. 

710 2_ $a Code Consultants, Inc., $e author.

Add $e relationship designator if available

 

For CalDocs only: Add corporate name entries for private companies such as consultants, that either write or share responsibility for the publication with the government agency.

(Doesn’t really have to be a government agency in consultation with a private company–it could be any corporate body that does something in conjunction with a private consultant).

773 (Host Item Entry) Do not use. Remove if found on copy.  
776 (Additional Physical Form Linking Entry) Add 776 $i for the print version and/or other format using “Insert from cited record” macro command; if it lacks OCLC number, provide $t [title]. $z ISBN if available.  
76X-78X (Linking fields) Record if applicable (fields other than 776).  
856 $3 (Materials specified)

For multivolume monographic sets, use for designating specific volumes. 

Example: 

856 40 $3 v.1. $u … 

856 40 $3 v.2. $u …

856 40 $3 v.1. EPUB version. $u …

 
856 $u (Electronic access & location)

Use URLs found in the OCLC WorldCat record if it is generic. Add if lacking. If campus-specific authenticated URLs are required for access, contact CDL to create an interim screen. Add a persistent URL in $u. Some types of persistent URLs utilized by SCP: 

DOIs 

GPO PURLs 

Archival Resource Keys (ARKs) 

See: SCP cataloging and linking guidelines 

Do not add links for related websites (856 42).

As URL syntaxes are subject to change without notice, always consult the CDL eresources tracking page to verify the type of URL to be used and how to construct URLs for each package. 

When URL domain changes, request to update it on the CDL eresources tracking page.

930 (Local added entry)

Add at least one 930 field for every 946 field in a record. 

Examples: 

930 0_ $a IEEE Xplore online conference proceedings

930 0_ $a Open access resource; selected by the UC Libraries. CalDocs online monographs

For a list of authorized title entries (930 $a), consult the CDL eresources tracking page.

For detailed instructions on how to set up 930 $a, refer to Guidelines for Setting up 930/973 $a and Local Collections for electronic resources.

946 (Electronic access & location)

After updating OCLC WorldCat record and before exporting, copy 856 40 to a new field with a tag of 946 40

If with PIDs, change to native URLs.

 

back to top

 

3. Electronic Integrating Resources

For CDL licensed databases, SCP catalogers should catalog them as integrating resources using the online record. Integrating resources should be cataloged according to RDA, the CONSER Cataloging Manual Module 35 and PCC Provider-Neutral cataloging guidelines. Description of integrating resources should reflect the current iteration of the resource.

The table below outlines the elements that should be present in the SCP record. For information about which elements to include in the OCLC WorldCat record, refer to the PCC Provider-Neutral cataloging guidelines.

Pay close attention to the URLs for databases as they tend to be subscription specific and sometimes campus-specific. If campus-specific authenticated URLs are required for access, contact Kristen Chua at the CDL to create an interim screen.

Electronic Integrating Resources

MARC tag Integrating resources record Notes
Fixed fields

Use Continuing Resources workform and code BLvL: i and Entry Convention S/L: 2

Code the fixed fields per national standards.

 
001 and 035 (Unique and permanent numeric or alpha-numeric record ID numbers for record output) OCLC numbers are automatically generated in the 001 and 035 fields upon export.

Example:

001  46763253

035   $a (OCoLC)46763253

006 (Additional material characteristics)

Add if lacking.  Required only to code the first byte. 

Example:

006  m     o  d

 
007 $a $b (Physical description)

Add if lacking.  Note that only $a and $b are required. 

Example:

007   $a c $b r

 
040 (Cataloging Source) Add $e rda following $b eng.  Add $e pn following $e rda if also provider-neutral. All IRs should be based on the latest iteration so descriptions may require upgrading to RDA.
041 (Language code) Accept as is, or add if applicable. Pair with a 546 field if applicable.
050 (LC call number) If lacking, add a LC classification number. (050 14 $a for CONSER records and 050 _4 $a for non-CONSER records). LC classification not required for CalDocs.
086 (call number)

Add if available (CalDocs only) suffixed by “Online”.

Example:

086    $a L960.T42 $2 cadocs Online

or

086   $a L960.T42 Online

 
130/240 (Uniform titles) Accept as is.  
245 $a (Title proper) The title proper should be the one that currently appears on the website being described.  
245 $b (Remainder of title) Accept as is.  
245 $n & $p (Number & name of part/section) Accept as is.  
245 $h (General material designation) Remove $h [electronic resource] if present.  
246 (variant title, title added entries) Leave existing 246s.  If appropriate, add 246 for variant titles.  
247 (Former title) Former titles are recorded in the 247 field.  Input the current title in 245.  
264 (Place of publication, publisher, and date) The earliest date of the integrating resource, regardless of the changes in title, will be retained in the most current 264 $c.  
300 $a (extent of publication)

Use “1 online resource” in $a

 

 
310/321 (Frequency)

Record frequency if known.  

Examples:

310      $a Frequently updated

310      $a Updated six times a year

 
336 (Content type) Add if lacking.  
337 (Media type) Add if lacking.  
338 (Carrier type) Add if lacking.  
362 (Numbering)

Record if applicable. 

Example:

362 1_ $a Began in 1999.

 

440/490/830/890

(Series)

Follow PCC guidelines.  
500/550 (Provider notes)

Record if applicable.

Example:

550  $a Made available through: ABC-Clio. 

Do not note providers as the digitizer.

 
506 (Access restriction note)

Accept as is. Do not use, unless restrictions apply to all versions of the IR. An example is a “classified” government document for which access is always restricted. If specific access restrictions are considered useful, give in 856 $z.

Follow PCC guidelines for open access titles. 

 
516 (Type of computer file or data) Do not use.  Retain only if unusual format (e.g., need special Chinese software to read).  
520 (Contents/summary note) Record if applicable  
530 (Additional physical form) Prefer 776 $i.  
546 (Language note) Accept as is, or add if applicable.  If recorded, also add 041 $a.  
588 0_ (DBO/Title source note)

Accept as is, unless redescribing, use 588 0_. 

Example:

588 0_ $a Title from quick search screen (viewed September 21, 2018).

Add if lacking.

The wording of notes is left to the cataloger’s judgment. Catalogers are strongly encouraged to accept the wording found in copy cataloging if it is clear and succinct. Do not strive for consistency.
650 (LCSH) Assign at least one LCSH.  
650 (MeSH) Assign at least one MeSH heading for biomedical databases.  
655 (Genre/form heading) Accept as is.  
7XX (Added entries) Add 7XX for an issuing body if applicable. Delete 7XX fields for providers. Add $e relationship designator if available
730 (Analytical entry)

Record if applicable. 

Example: use for tracing titles of databases within databases:

730 02 $a CRC Press. $p ENGnetBASE.

 
740 (Added entry— uncontrolled related title)

Record if applicable.

Example: 

740 02 $a ENGnetBASE.

 
773 (Host Item Entry) Do not use. Remove if found on copy.  
776 (Additional Physical Form Linking Entry)

Record if applicable for related manifestations in different formats and for format changes.

 

Example:

776 08 $i Print version: $t Current protocols in bioinformatics $z 0471250937 $w (DLC)  2008215311 $w (OCoLC)213330914

76X-78X (Linking fields) Record if applicable (fields other than 776).  
856 $u (Electronic access & location)  Use URLs found in the OCLC WorldCat record if it is generic. Add if lacking. If campus-specific authenticated URLs are required for access, contact CDL to create an interim screen. Do not add links for related websites (856 42).

930 (Local added entry)

 

 

Add a 930 field for every 856 field in a record.

Examples: 

930 0_ $a CDL licensed databases

930 0_ $a CDL open access databases

930 0_ $a CDL licensed databases. J-DAC, Japan Digital Archives Center

For a list of authorized title entries (930 $a), consult the CDL eresources tracking page.

For detailed instructions on how to set up 930 $a, refer to Guidelines for Setting up 930/973 $a and Local Collections for electronic resources.

920 $u (Electronic access & location)

After updating OCLC WorldCat record and before exporting, copy 856 40 to a new field with a tag of 946 40

If with PIDs, change to native URLs.

 

back to top