Type of Record: Code a for language material. If warranted, code m for computer file. (e.g. computer software, computer-oriented multimedia, online systems, or services).  If no one type of content predominates, or if predominant content cannot be determined, or in case of doubt, code “m.”


Bibliographic Level: Code i for integrating resource


Computer file fixed field: When Type of Record is coded a, code the 006 for computer file aspects, Type of file and Government Publication.


Physical description fixed field: When leader is coded type a or m, code 007 for electronic resource. Code the Specific Material Designation remote and the Dimensions not applicable.


Form of Item: When Type of Record is coded a, code the 008 s for electronic.


LC classification number: Leave if available.


Main entries: Use as required.


Uniform titles: Don’t assign a uniform title simply to resolve a database conflict when the main entry for the resource being cataloged is the same as the main entry for another work.  However, when a heading for an integrating resource is needed as a subject or related work added entry and the main entry is the same as the main entry for another work, create a uniform title and resolve the conflict by adding a qualifier at the end of the title proper.  A uniform title is also assigned when a serial changes to an integrating resource and vice versa.


Title proper: Record the title proper from the chief source (i.e., title screen, home page). Do not transcribe words that serve as an introduction and are not intended to be part of the title. AACR2 1.1B1. Use the GMD [electronic resource].  Base the title proper on the most current iteration of the resource (the one you are viewing).


Variant titles: Use the appropriate indicators to generate a note for the source of the title.  Also record acronyms of the title proper in 246.  If there is no appropriate indicator, set the 2nd indicator to "blank" and add the text of a note in |i. Possible |i notes; |i Also known as: |i HTML title: 

247 10

Former Title Proper: If any change in the title proper occurs on a subsequent iteration: change the title and statement of responsibility area to reflect the current iteration and give the earlier title in a 247 with ‡f showing the "last viewed" date of the earlier title. Important reminder: If changes are made to the main entry on a record for an integrating resource, remember to update the linking fields in any related records! 

245 00 Resources for Swedish genealogical research
247 10 Swedish genealogical resources ‡f <Mar. 10, 2000>


Edition: Transcribe an edition statement if considered to be important. Give statements indicating regular revision or frequent updating (e.g., Rev. ed. issued every 6 months, Frequently updated) as frequency in the note area. AACR2 12.2B2.



Publication, distribution: Consider all remote access electronic resources to be published. (i.e. record publisher and place, even if they are not known. 260 [S.l. : |b s.n.],).  Consider the host site the publisher, unless there is a specific statement identifying the publisher as another body.  The place and publisher should be applicable to all online versions and thus, should not reflect a particular digitizer or provider version or interface.  If the place of publication, or the name of the publisher changes on a subsequent iteration: change the record (260 and 008) to reflect the current iteration and give the earlier place or publisher in a note if considered important.AACR2 12.7B11.2.  If the publisher and place of publication cannot be readily determined (1-3 clicks from the page being cataloged), record [S.l. : |b s.n.].

260 |c

Publication date: If viewing the first and/or last iteration, give the beginning and/or ending dates in the 260 |c. If not viewing the first iteration, and there is no explicit statement about the beginning date, then: do not record a 260 |c.  Give any available information about the beginning date in a 362 1_. Do not consider a copyright date (or span) as an "explicit statement" about the beginning publication date. Accept dates from member copy.


Current Frequency: Make notes on the frequency of the updates  to the integrating resource unless it is unknown. If the date is unknown, omit field 310.  Include the word "updated" or "updates" with the frequency word. 310    Updated quarterly, |b 2002-


Former Frequency: If the frequency of updates changes, change the record to reflect the current iteration and record the former frequency. 321    Updated monthly, |b 1998-2001

362 1_

Dates of Publication: Make a note giving date information when first/last iterations are not available.  Do not use 362 0 _ (formatted note style). 

Ex.: 362 1_ Began in late 1990s.  362 1_ Probably began after 2001.


Notes: Use as required


Source of title proper: Mandatory note.  Maybe combined with description based on note. 


Description based on note: Mandatory note.  Supply date resource viewed or "Description of resource as of [date viewed]" Title from home page, viewed on Oct. 27, 1999. Change the date viewed note when updating a record for changes in a later iteration of the resource being described. 


Restrictions on access note: When a publication is not freely available and the electronic location is given in field 856, catalogers may note the restriction.  Only use 506 if restrictions apply to all versions of the resource.

506__ $a Restricted to subscribing institutions.


Type of computer file or data note: Give information relating to the type and extent of the resource if it is considered to be important and not found elsewhere in the description. (AACR2 9.7B1, 9.7B8).  This field is reserved for really unusual file and data types in CONSER practice.


Summary: Mandatory note.  If summary text is available on the website, use it and edit out any evaluative wording.  If none exists, note the content of the resource and the functionality available (i.e., specific kinds of searching, data export, etc.). 


Other physical forms available note: Use when information about a different physical format is available. Prefer to use a 776 |i to provide notes about other formats when a linking field is being added to the record for the other resource, but do not include the 530 in these cases.  A 530 can be used if no linking entry is made or if more clarity is needed. 


System requirements: Use as necessary if a browser alone does not obtain access. System requirements: Adobe Acrobat Reader, ver. 3.0.


Mode of access: Mode of access: World Wide Web.


Former title proper complexity note: Only use in those situations where you need to provide more explanation than can be given in the 247 field (i.e., do not give a 547 just because there is a 247).


Issuing body note: Use to provide information about issuing bodies not included in the statement of responsibility or publication area.  Notes relating to commercial publishers, etc., are made in a 500 note if necessary.


Linking entry complexity note: If the relationship among linked resources cannot be made clear with 760-787 fields, explain the relationship in a 580.  Do not use a 580 just because multiple linking fields are used.  The 580 is mandatory for merger relationships.


Uncontrolled subject terms: Delete any found on record.


Subject headings: Use as needed.


Genre/Form Heading: Add the genre heading "Online resource" for all material that should appear in the Online Resources page.

655 _7 |a Online resource. |2 local

Delete any other 655’s.  If they come before the “Online resource” heading, they will cause the resource not to appear in the Online Resources page.

700- 710 

Personal and corporate added entries: Use as necessary. Authority records are created as necessary.  Do not add for publishers or digitizers, only for bodies responsible for content.


Added entry: Uniform title: Use as needed for title added entries.






Relationships with other resources: 776 (Additional physical form entry) ; 780 (Preceding entry) ;785 (Succeeding Entry) and 787 (Nonspecific relationship)

Links consist of catalog entry (|a, |t, etc.), ISSN (|x) or ISBN (|z), and record control numbers (|w). Don't imagine relationships; in case of doubt, don't include. When a relationship is known, but the "flavor" is not; don't guess, use 787. Include a 580 (Linking Entry Complexity) note whenever the indicators do not adequately describe the relationship.


Electronic location: Change |u to |x so URL will not display in PONI from bib record. Delete |z Public Note as necessary. 856 40 |x


|a zSTANDING ORDER Use if necessary if an acquisitions search reveals that the item is on a standing order.


Online resources keywords: Use the subject terms listed in the Subject Keywords document. Assign subject keywords and their corresponding broad topics as needed.  End each keyword string with a semicolon followed by a space. 953_ _ |a History; Humanities; Social Sciences;

Additional Sources For Cataloging Electronic Resources

·         AACR2 Chapter 9 & 12

·         Integrating resources: a cataloging manual (Appendix A to the BIBCO Participants’ Manual and Module 35 of the CONSER Cataloging Manual)

·         Introduction to Cataloging Electronic Integrating Resources: An Online Training Presentation (PowerPoint) (OLAC)

·         Cataloging Electronic Resources: OCLC-MARC Coding Guidelines

·         Guidelines for Coding Electronic Resources in Leader/06

·         Guidelines for the Use of Field 856

·         ISBD(ER): International Standard Bibliographic Description for Electronic Resources 

·         Source of Title Note for Internet Resources (3rd rev.) (OLAC)

·         Summary Notes for Catalog Records (OLAC)



smh 8/27/2008


For questions about the content of this page, please contact Sarah Haight

This page is maintained by  

Last updated 06/12/2009