TWO DOCUMENTS:
A)
In general, E-books that maintain the pagination of the original are treated as reproductions, and require the following fields:
Fixed Field: Type: a Blvl: m Form: s
Note: all other fields coded as in the original print publication, including dates and Ctry.
Typical coding of Control Fields:
006 T006: m File: d (other codes as appropriate)
007 c $b r $d c $e n
020 Should contain only the ISBN of the e-book, not the original. You may provide the ISBN of the original in a 776 field. Example:
020 0585325634 (electronic bk.) : $c $20.95
Variable fields:
All descriptive fields coded as in the original, including 260 (edition of original) and 300 (pagination of original).
The 245 should be identical to the original, except you must add $h [electronic resource] after the title proper
Treatment of Fields specific to e-book reproductions:
Omit 256 Electronic file characteristics. Comment: Only required if item is coded in the primary fixed field as e-resources (type: m, blvl: m).
516 Type of computer file -- Generally omitted (LCRI 1.11A " Transcribe the bibliographic data appropriate to the original work being reproduced in the following areas: title and statement of responsibility; edition; material (or type of publication) specific details; publication, distribution, etc.; physical description; series.")
538 System requirements - Omit
538 Mode of access - Omit because it will be supplied in 533 $n
500 Source of title - Omit
530 Also available in print - Omit (again, the 533 will cover this).
Note: These fields are required only when cataloging e-resources that are not reproductions. For reproductions, the 533 field is required.
533 with details of the e-book publishing. Here's a typical netLibrary example:
533 Electronic reproduction. $b Boulder, Colo. : $c NetLibrary, $d 2000. $n Available via World Wide Web. $n Access may be limited to NetLibrary affiliated libraries.
Also add:
- Optional local genre/form heading, example: 655 7 Electronic books. $ 2 local
- Corporate author added entry, example: 710 2 NetLibrary, Inc.
- Additional physical form entry (which allows access via the print ISBN), example: 776 1 $ c Original $ z 0664256716 $ w (DLC) 99026278 $ w (OCoLC)41086743
Note: The presence of the 533 provides the justification for the 710 and the 776 fields.
And, of course:
- Electronic location/access, example: 856 4 $3 Bibliographic record display $u http://www.netLibrary.com/urlapi.asp?action=summary&v=1&bookid=41201 $z An electronic book accessible through the World Wide Web; click for information
PS E-books that don't carry the same pagination as the original are generally not treated as reproductions. Instead, they follow the rules for a monographic e-resource, in which most of the fields you listed as required are included, and there is no 533. The fixed field generally reflects the e-resource and not any print equivalent.
B)
I have received several questions about the different treatment of
electronic book reproductions and just plain electronic monographs. I would
like to clarify my previous posting, as follows:
My previous posting covered only remotely accessed electronic reproductions
of works previously published in printed form (including electronic books.
My coding suggestions also assume that the content is presented in a form,
such as PDF, or a proprietary format, like netLibrary's that preserved the
pagination and presentation of the original. This, to me, is what qualifies
the resources as a reproduction.
Here are some additional comments for dealing with non-reproduction e-books:
Typical coding for a remote monographic, textual electronic resource:
Type: a
Blvl: m
Form: s
006 T006: m File: d (and the other elements/values as appropriate)
007 c $b r (if a remote resource ) or for CD-ROMs 007 c $b o For both:
code additional characteristics as appropriate to the item.
245 .....$h [electronic resource]
250 If appropriate
NO 256 (item is not Type: m)
NO 300 (item is remote, has no physical characteristics. Handle any physical
detail in a note if needed).
500 Source of title note is required
505 (only if appropriate), if not, consider 520
538 Mode of access: Internet
538 System requirements: World Wide Web Browser software. (you may also
include any plug-ins required in this field) NOTE: This is a free text area.
Most libraries have established standard language for this area.
856 Electronic Location
Optionally:
516 Electronic text (optionally, include format, eg HTML, PDF, ASCII)
530 Other versions available
655 7 Electronic books. $ 2 local
776 Additional Physical Form Entry
Guidelines for other types of e-books:
Homemade "collections" distributed by circulating e-book readers, such as
Rocket and RCA ebook readers, Franklin eBookman, etc.:
In this situation, the library is creating a local collection of
e-books, circulated together. The actual device is what gets cataloged.
Contrary to anyone's instinct, a 3-D object is covered in Chapter 10 of
AACR2 2002 rev. MARC coding handles realia such as this as Visual material
(Type: r; Blvl: m). You could include a 505 note for the specific titles
available, and add title added entries if necessary for access. This type of
treatment is generally informal, and may lack the "official" GMD [Realia]
from list 2 in AACR2 2002rev Rule 1.1C1. I have seen libraries use $h
[Electronic book reader], which is certainly not AACR2 approved, but
probably is much more understandable to their patrons.
Ebooks available for download from the Internet
These are straightforward remote access monographic texts. If they do not
meet my pagination test, then they would be treated as a separate instance
of the work, and not as a reproduction. Therefore the FF and variable fields
would describe the e-resource (not the original print edition). You would
still code it as Type: a; Blvl: m Form: s. You would use specific notes
fields to handle Mode of Access and System requirements, and of course if
the file required an e-book reader to actually read it, you would put that
in the 538 System Requirements note. The GMD would be $h [electronic
resource]. You would include 006 and 007 to describe the electronic
characteristics of the resource.
Ebooks delivered on CD-ROM or other direct access media
These are straightforward electronic monographic texts. If they do not meet
my pagination test, then they would be treated as a separate instance of the
work, and not as a reproduction. Therefore the FF and variable fields would
describe the e-resource (not the original print edition). You would still
code it as Type: a; Blvl: m Form: s. You would use specific notes fields to
handle System requirements, and of course if the file required an e-book
reader to actually read it, you would put that in the 538 System
Requirements note. Instead of mode of access, you would include a 300 field
describing the carrier. The GMD would still be $h [electronic resource], and
you would still include 006 and 007 to describe the electronic
characteristics of the resource.
HTML or ASCII e-books on the Internet:
Again, these are straightforward remote access monographic texts. ASCII and
HTML do not meet my pagination test, so these types of e-books and e-texts
would be treated as a separate instance of the work, and not as a
reproduction. Therefore the FF and variable fields would describe the
e-resource (not the original print edition). You would still code it as
Type: a; Blvl: m Form: s. You would use specific notes fields to handle Mode
of Access and System requirements. You would certainly include a source of
title note, and you might opt to include a 516 Type of computer file or data
note. The GMD would be $h [electronic resource]. You would include 006 and
007 to describe the electronic characteristics of the resource.