Variable Fields 245-490/830 (e-Monographs)

Variable Fields

In the variable fields of the bibliographic record, follow the current established guidelines and procedures for monographic cataloging in RDA for all elements, with particular emphasis on the instructions below.

The examples are taken from existing records. Some fields have been modified. Only those fields relevant to the point being explained are included. Follow the link in the 856 field to examine the resource being described. The text <URL> is used in place of the URL that would appear in the record.

020 - ISBN

Record the ISBN for the online format in subfield a. Do not transcribe hyphens. For born-digital resources, there should only be an ISBN for the online resource by definition.

Example

When cataloging an e-book where a corresponding record for the print version is not in OCLC, you may encounter 2 ISBNs. Publishers will sometimes include the ISBN for the print version as well as the online version in the resource. Record both ISBNs in separate 020 fields, with the ISBN for the online resource first, in ‡a and the ISBN for the print version in 020 ‡z. See first 245 example.

040

Besides ‡b and ‡e rda, include also ‡e pn (following rda)

Example

050 - Library of Congress Call Number

Supply an LC classification number for the item in subfield a. Do not add it to the MFHD. The call number will be reflected in the bibliographic record, but not in the OPAC. A book number (subfield b) is unnecessary. In the example, 336-338 code subfields are optional.

Example

24X - Title Area

RDA 2.3.2.2 follows 2.2.2.4.2 as explained on the previous page. In order of preference, transcribe the title proper from: a. text in the resource, b. embedded metadata. A lot of judgment is, therefore, left to the cataloger. In addition, 2.3.2.2 follows 2.2.4 when no title can be identified in a. or b. In such cases, in order of preference use a. accompanying material, b. other published descriptions of the resource, d. any other available source (e.g. a reference source).  2.2.4 c. is for containers, which would not be applicable for online monographs. If one of the 2.2.4 options has to be applied, use brackets.

Although updating websites often have introductory phrases (which, as in AACR2, should not be included in the title proper), this should be less common with online monographs.

The source of title is always given in a note. See 050 example above.  See 500 - Source of Title Note.

Select the title that applies to the resource at the level selected for description, typically the page at the URL given in the 856 field.

Reminder: the general material designator (GMD/ 245 ‡h) is never used in RDA records.

Note on the following example. If the resource has an ISBN for both the online and print versions, record them in separate 020 fields, with the online ISBN first.

Example

Online resources frequently display more than one form of title. Create a 246 field for any variant title that may reasonably be used for access.  Use 246 31 for parallel titles; use 246 1_ for all other variants, with subfield i if applicable.

Example

Example

In the (hypothetical) example above, the provider is Safari Tech Books Online. The publisher O'Reilly now publishes its titles only as e-books; the book is "born digital." On the right side of the window is a large icon with the message: Start reading Access2012 now! E-books licensed through Safari Tech have a standard configuration which includes entry of the title of the e-book on the Start icon of the e-book's opening window. It's reasonable to expect that this is a provider rather than a publisher quirk, so the provider-neutral note is evoked.

250 - Edition Area

Transcribe an edition statement, if the resource contains differences from other editions of the resource or is a named reissue of a resource. Take the presence of words such as edition, issue, version, release, and update as evidence that the statement is an edition statement (AACR2 9.2B2).

Do not treat an issue of a resource that incorporates minor changes (e.g., changes in look and feel or changes in navigation) or changes that apply to only part of a resource as a new edition (AACR2 9.2B4).

A new bibliographic record is required when a URL remains active but links to a different resource than that described in an existing record (LCRI 21.3B). The cataloger should create a new record, rather than modify the record for the resource previously at that location. If the resource previously at that location is not available at another URL, the record for it should be deleted.

264 - Publication Statement

Consider all remote access electronic resources to be published (AACR2 9.4B2).

Explicit publication information may appear on the home page, table of contents page, or about page. Examples of phrases that are considered explicit statements of publication include created by, hosted by, etc. Give the name of the publisher in the 260 field, even if already given in the title area. In accordance with the PCC guidelines, do not include the names of any distributors, if different.

Online resources often include many pieces of intellectual content that have different copyright dates. If there is no publication date which applies to the resource as a whole and the resource has multiple copyright dates, transcribe only the latest copyright date (AACR2 9.4F4).

300 - Physical Description

This field always begins with "1 online resource" (you may notice that NLM records leave out the 1, presumably because it's redundant, although one could catalog a collection of e-books).  Provide in parentheses the extent of the item, if readily available, e.g., the number of pages of a PDF document (AACR2 9.5B3). Record illustrative material in ‡b. The practice of recording "PDF" in ‡b is no longer followed.

Example. OCLC 858920669 rda/pn record, abridged for this example.

490/830 Series Statement/Series Added Entry

If a series is provider specific, do not transcribe as a series statement or make a series added entry. Publisher series should be transcribed. In some cases, the publisher is also the provider; in that case, treat the publisher as a publisher rather than as a provider.