SULAIR Home

CD-ROMs, DVD-ROMs, and other tangible computer file carriers (floppies, cartridges, drives, etc)--RDA Cataloging

*Revised  May, 2014

Examples:

These are the most commonly found types of CD-ROMs and DVD-ROMs, but do not exhaust the possibilities

Textual CD-ROM (Symphony view)

Rec_Type a     Bib_Lvl m       TypeCtrl            Enc_Lvl        

Desc i              Entrd                Dat_Typ s        Date1 2004

Date2               Ctry xxu          Illus  a              Audience

Form   q            Cont b              GovPub           ConfPub  0

Festschr 0        Index 0            LitForm 0         Biog

Lang eng          Mod_Rec         Source d         

             

006                  006       m**** **qd* ******

007                  co cg

020                  ISBN if present

024      1          UPC all 12 digits

040                  CSt$beng$cCSt$erda

043                geographic area code

100      1          Author Last name, First name (authorized NAF form),$eauthor.

245      10        Title :$bsubtitle /$cstatement of responsibility ; different functions separated by semicolons.

246      1          $iTitle on container:$aVariant title if there is one

250                  Edition as it appears on the item.

264        1        Place of publication :$bPublisher,$cDate.

300                  1 computer disc (xi, 512 pages) :$bcolor illustrations ;$c 4 ¾ in..

336                  text $2 rdacontent

337                  computer $2 rdamedia

338                  computer disc $2 rdacarrier

347                text file $b PDF $c 1.2 MB $2 rda

490      0          Series title as transcribed if not in NAF [if in NAF, see 4xx]

538                  System requirements as given on item.

538                Disc characteristics: CD-ROM.

520                  Brief objective summary.

650       0         Subject.

 

 

 

Multimedia CD-ROM

Rec_Type m    Bib_Lvl m       TypeCtrl            Enc_Lvl        

Desc i              Entrd                Dat_Typ s        Date1 2004

Date2               Ctry xxu          Audience          Form  q

FileType m or i  GovtPub          Lang eng          Mod_Rec        

Source d         

             

007                  co cga

020                  ISBN if present

024      1          UPC all 12 digits

040                  CSt$beng$cCSt$erda

043                geographic area code

100      1          Author Last name, First name (authorized NAF form),$eauthor

245      10        Title :$bsubtitle /$cstatement of responsibility ; different functions separated by semicolons.

246      1          $iTitle on container:$aVariant title if there is one

250                  Edition as it appears on the item.

264         1       Place of publication :$bPublisher,$cDate.

300                  1 computer disc :$bcolor ;$c 4 ¾ in..

336                  [give a separate 336 for each applicable content type] $2 rdacontent

337                  computer $2 rdamedia

338                  computer disc $2 rdacarrier

347                $b PDF, MP3 $2 rda

347                $b Flash

490      0          Series title as transcribed if not in NAF [if in NAF, see 4xx]

538                  System requirements as given on item.

538                  Disc characteristics: CD-ROM.

520                  Brief objective summary.

650       0         Subject

700      1          Name, Other,$erelationship designator.

 

Computer game   [no authoritative source on how to do this]

Rec_Type m    Bib_Lvl m       TypeCtrl            Enc_Lvl        

Desc i              Entrd                Dat_Typ s        Date1 2004

Date2               Ctry xxu          Audience         Form  q

FileType g        GovtPub          Lang eng          Mod_Rec        

Source d         

             

007                  co cg

020                  ISBN if present

024      1          UPC all 12 digits

028      52        number$bCompany name

040                  CSt$beng$cCSt$erda

245      10        Title :$bsubtitle /$cstatement of responsibility ; different functions separated by semicolons.

246      1          $iTitle on container:$aVariant title if there is one

250                  Edition as it appears on the item.

264         1       Place of publication :$bPublisher,$cDate.

300                  1 computer disc :$sound, color ;$c 4 ¾ in..

336                  two-dimensional moving image $2 rdacontent

336                  computer program $2 rdacontent

337                  computer $2 rdamedia

338                  computer disc $2 rdacarrier

344                digital $b optical $2 rda

346                  $b NTSC or PAL $2 rda

347                $b GAME ENCODING IF APPLICABLE Xbox 360 OR PlayStation 3 ǂe REGION

490      0          Series title as transcribed if not in NAF [if in NAF, see 4xx]

538                  System requirements as given on item.

538                  Disc characteristics: DVD-ROM.

520                  Brief objective summary.

650       0         Subject

655      0          Genre

710      2          Company that developed game

710      2          Publisher,$e publisher

CD-ROM of spoken word MP3 files 

Rec_Type i      Bib_Lvl m       TypeCtrl            Enc_Lvl  I     

Desc i              Entrd                Dat_Typ s        Date1 2004

Date2               Ctry xxu          Comp  nn         Format n

Parts                 Audience         Form  q            Accomp  0

Ltxt  __            Ararng             Lang eng          Mod_Rec

Source d         

             

006                  m**** **qh* ******

007                  sd fsngnnmee

007                  co nga

020                  ISBN if present

024      1          UPC all 12 digits

040                  CSt$beng$cCSt$erda

100      1          Author Last name, First name (authorized NAF form), ,$erelationship designator.

245      10        Title :$bsubtitle /$cstatement of responsibility ; different functions separated by semicolons.

246      1          $iTitle on container:$aVariant title if there is one

264        1        Place of publication :$bPublisher,$cDate.

300                  1 audio disc (duration maybe?) , $c 4 ¾ in.

336                  spoken word $2 rdacontent

337                  audio $2 rdamedia

337                  computer $2 rdamedia

338                  audio disc $2 rdacarrier

338                  computer disc $2 rdacarrier

538                  System requirements as given on item

344                digital $g stereo $2 rda

347                audio file $b MP3 [or WAV, etc.] $2 rda

538                  Disc characteristics: CD-ROM.

505      0         Title / Statement of responsibility (duration) – etc.

650       0         Subject

700      1          Name, Other,$erelationship designator.

 

Which format to use? (Leader 06)

Most CD-ROM/DVD-ROM monographs will be cataloged either on the workform for books or on the workform for computer files/electronic resources.  Rec_type (Symphony)/Type (OCLC) field would be “a” or “t” if it is on the books workform and “m” if it is in the computer files workform.  Definitions for those values are as follows:

a   Text. Use when the content is primarily text (it may have incidental illustrations, search software, etc.  Use also when the content is textual spreadsheets, such as Excel.

t  Manuscript text. Use when the content is a reproduction of a text manuscript, including theses

m Computer file. Items included in the following classes of electronic resources: computer software (including programs, games and fonts), numeric data, computer-oriented multimedia, online systems or services. For these classes of materials, if a significant aspect causes it to fall into another Type category, code for that significant aspect. In case of doubt or if the most significant aspect cannot be determined, consider the item a computer file.

If the primary content type is something other than the above, use the workform and record type for the letter corresponding to the type of content that is on the disc. Cataloging this material would involve combining procedures in this document with procedures for that particular type of content.

g  Video. Use for digital video files, such as MPEG, Flash, Quicktime.  However, DVD-video discs and VCD (video CD) discs, which will play in a conventional DVD video player, should be cataloged as videodiscs  [link to our video documentation] rather than computer disks.

k  Pictures. Use when the content is primarily still pictures.

i Non-musical sound recordings. Use for digital sound  files for such as mp3, win, ram etc. files that cannot be played in a conventional CD player and the content is non-musical sound recording rather than music.

e  Maps. Use when the content is primarily cartographic data, such as maps and GIS data.  Normally the Branner Map Library will catalog these.

c  Notated music. Use when the content is primarily musical notation.   Normally the Music Library will catalog this

d  Manuscript music. Use when the content is primarily a reproduction of a music manuscript.   Normally the Music Library will catalog these

j Musical sound recording. Use for digital music files such as mp3, win, ram etc. files that cannot be played in a conventional CD player [Nancy, is this right?].   Normally the Music Library will catalog these

 

Fixed fields/008

 

The examples in this table are the most common in CD-ROM cataloging in the book or electronic resources format. For further descriptions of the fixed fields for other formats, and for other applicable values, see the MARC 21 Format for Bibliographic Data in Catalogers Desktop or online.

When using the books workform:

Field Name                 Value   Description

Bib_Lvl                       m         Monograph

TypeCtrl                     blank  

Enc_Lvl                      blank   Blank for full level [question which OCLC values do we use?]

Desc                            i           RDA

Dat_Tp                        s           single known publication date, or single questionable date, decade, or century .

                                     q          questionable date when there is more than one questionable date in the 264$c, as in [between 1997 and 2010]

                                     r          MARC21 defines this field for use with eye-readable reproductions.

                                     t           Use this when there is both a publication date (even an inferred one) and a copyright date in the 264 c, even if both dates are the same  (per message from D. Reser, LC)

Date1                                      4 digit beginning date (for, Dat_Tp s, p. and q). This should be the date as in the 264$c, or the first date when there is more than one. Unknown digits may be represented with a "u" For a locally made reproduction, this should be the date of the reproduction.

Date2                                     4 digit date to be used when Dat_Tp is r,q, or t. Unknown digits may be represented with a "u".When there are 264 fields with publication date and a copyright date, the copyright date goes in Date2  . For questionable dates, Date2 would be the last date in a date range given in the 264$c (e.g. between 1997 and 2004 would have Date1 2004 and Date2 1997).  When a date of publication and a date of copyright are given in the record, put the date of publication in Date1 and the date of copyright in Date2.

Ctry                                        Use for the country of publication. For a list of country codes, see the MARC Code List of Languages on Cataloger's Desktop, or online.  For dissertations, use xx.

Illus                             blank               No illustrations

a          Illustrated

b          maps

Audience                     blank   No special audience

j           For children

Form                               q          Electronic, physical media (CD-ROM, floppy, flash drive, etc., not online)

Content                       blank   No special content

b          Includes bibliography

s           statistics

            For a  list of other types of content, see the OCLC Bibliographic Formats and Standards or MARC21

GovtPub                      blank  not a govt. pub

f           federal

s           state

l           local

i           international

If none of the above apply, see OCLC Bibliographic Formats and Standards or MARC21

ConfPub                    0          Not a conference publication

                      1          Conference publication

Festschr                      0          Not a Festschrift

                      1          Festschrift

Index                          0          No indeex

                                    1          Has index

LitForm                      0          No special literary form

                                    f           fiction

For other codes, see OCLC Bibliographic Formats and Standards or MARC21

LitForm                      blank   Not biographical

For biography codes, see OCLC Bibliographic Formats and Standards or MARC21

Lang                            eng      3 letter language code. For a list of language codes, see the MARC Code List of Languages on Cataloger's Desktop, or online. See also 041.  When no spoken or written language is present, code language zxx.

Mod                             blank   modified record

Source                             c          PCC (in which case, must also have 042 pcc)

d          non LC, non PCC. Unless one is doing BIBCO cataloging, "d" is the default value

 

When using the computer files workform:

Field Name     Value   Description

Bib_Lvl                       m         Monograph

TypeCtrl                     blank  

Enc_Lvl                      blank   Blank for full level [question which OCLC values do we use?]

Desc                            i           RDA

Dat_Tp                        s           single known publication date, or single questionable date, decade, or century .

                                     q          questionable date when there is more than one questionable date in the 264$c, as in [between 1997 and 2010]

                                     r          MARC21 defines this field for use with eye-readable reproductions.

                                      t           Use this when there is both a publication date (even an inferred one) and a copyright date in the 264 c, even if both dates are the same  (per message from D. Reser, LC)

 

Date1                          4 digit beginning date (for, Dat_Tp s, p. and q). This should be the date as in the 264$c, or the first date when there is more than one. Unknown digits may be represented with a "u" For a locally made reproduction, this should be the date of the copy.

Date2                         4 digit date to be used when Dat_Tp is r,q, or t. Unknown digits may be represented with a "u". When there are 264 fields with publication date and a copyright date, the copyright date goes in Date2  For questionable dates, Date2 would be the last date in a date range given in the 264$c (e.g. between 1997 and 2004 would have Date1 2004 and Date2 1997).

Ctry                            Use for the country of publication. For a list of country codes, see the MARC Code List of Languages on Cataloger's Desktop, or online.  For dissertations, use xx.

Audience                     blank   No special audience

j           For children

FileType                      a            Numeric data. Files that are mostly numbers or representation by numbers (e.g., student test scores, football team statistics, etc.). The information may be original surveys or information that has been summarized or statistically manipulated

                        b          Computer program. Ordered sets of instructions directing the computer to perform operations and identifying the information and mechanisms required. A program is a series of instructions given to complete a task. Use for micro-computer software. Use also for computer models, which are a characterization in mathematical terms of a process, object or concept, that enables the manipulation of variables to determine how the process, object or concept would behave in different situations

c          Representational. Files that have pictorial or graphic data. The pictorial and graphic data can be manipulated in conjunction with other types of files to produce graphic patterns, which can be used to interpret and give meaning to the information. Use for both still and moving images.

d          Document. Files that are mostly alphabetic information (words or sentences) converted into a code that can be processed, sorted and manipulated by machine and then retrieved in many optional formats. Use for records containing full text of documents and material intended to constitute a textual document, whether represented as ASCII or image data.Use for both single bibliographic entities or a collection of bibliographic entities. Documents whose primary purpose is textual, even if search software is present, are coded d.

e          Bibliographic data. Data that are bibliographic citations, including library catalogs or citation databases. May be structured or unstructured.

                           f           Font. File contains information for a computer to produce fonts.

g          Game. File is for recreational or educational use. Usually text and software, including videogames.

 

h          Sounds. File has data encoding computer producible sounds.

i           Interactive multimedia. Item supports navigation through and manipulation of many kinds of media (audio, video, etc.) in which the user has an almost conversational interaction with the computer.

j           Online system or service. Record is for an online system or service that may contain nonbibliographic information. An online system or service supports system based user interaction. For example, online library systems, FTP sites, electronic bulletin boards or network information centers

m         Combination. Computer models and numeric data files or computer programs and text files. [Look at MARC definition vs OCLC]

u          Unknown

z          Other

GovtPub          blank  not a govt. pub

f           federal

s           state

l           local

i           international

If none of the above apply, see OCLC Bibliographic Formats and Standards or MARC21

Lang                eng      3 letter language code. For a list of language codes, see the MARC Code List of Languages on Cataloger's Desktop, or online. See also 041.  When no spoken or written language is present, code language zxx.

Mod                 blank   modified record

Source               c          PCC (in which case, must also have 042 pcc)

d          non LC, non PCC. Unless one is doing BIBCO cataloging, "d" is the default value

 

006 

 

The 006 field is something akin to a supplemental 008 field and has many of the same values.  Include an 006 field whenever the Type is not “m”, that is, if you catalog on the workform for books, include an 006 for computer files so that the values what would have been in the 008 for computer files may be encoded in the record as well as the values for books.  Also use the 006 when a computer disc is accompanying material for some other resource.  Use the OCLC guided entry and choose the 006 for computer files (alternatively, use a text string).  The first position will be m.  The value for “file” should be one of the values listed under 008 FileType above, and the value for “form” should be q.  The only other value to be filled in would be if it were a government publication.

 

Symphony Example for an electronic document:

006       m**** **qd* ******

OCLC Example for an electronic document:

007    m      q  d    

In Symphony the 007 can be added or edited from a drop down menu—the asterisks are added when the menu is closed.

 

007

Symphony Example for a CD-ROM with sound:

007       co cga

OCLC Example for a CD-ROM with sound:

007    c $b o $d c $e g $f a    

OCLC  gives each subfield a separate delimeter, while in Symphony they go by position from a drop down menu.

Values:

$a  c   computer file

$b  o  for optical disc (covers CD-ROMs and DVD-ROMS [question—how about blu-ray? Or CD-R or DVD-R or should those be m Magneto-optical disc.?] .  j is for a floppy (i.e. a "magnetic disc").  b is a chip cartridge (like a game cartridge).  g is a disc cartridge (like a UMD disc).  Use z for "other" for a USB flash drive or hard drive.

$d is for color (values c for color, b for black and white (text with no color), m for mixed  (text with some color)   

$e  g for 4 ¾ in.  Look in OCLC Bibliographic standards and formats http://www.oclc.org/bibformats/en/0xx/007comp.shtm if the item is an odd size

$f a for sound.  If no sound, use blank

Also add another 007 for computer discs which contain primarily sound or video (except for video games)

 007                  sd fsngnnmee

007                    vz czazzu

020  ISBN

Record an ISBN that appears on the item (RDA 2.15.1.4).  Do not include the hyphens (OCLC Bibliographic Formats and Standards)

024 Other Standard Identifier (UPC)

This field is optional. Put other standard identifiers in the 024 field ((RDA 2.15.1.4 presumably). The UPC is 12 digits (including the smaller ones before and after the main sequence, and the first indicator is 1. The EAN is 13 digits

024      1          014381848120

024      3          1345678912343

 

028  Publisher number

The 028 field contains a publisher number, if applicable (another standard identifier, RDA 2.15.1.4). This is typically found on the spine of the container, though sometimes it is on the disc label or somewhere on the lower half of the back of the container. Subfield $a contains the number and subfield $b contains the name of the publisher. Use 1st indicator 5: The publisher number is not one of the other values (i.e., it is not a publisher number for a sound recording, music, or a videorecording).

028      52        52V 00385 $bMicrosoft Game Studios

 

040 Cataloging agency

For original cataloging in OCLC use:

040                 STF $b eng $e rda $c STF

For original cataloging in Symphony use:

040                 CSt$beng$erda$cCSt

041    Language

Use when there are multiple languages on the resources. 

Spanish language translation from English.

040      1          spa$heng

Multilingual

040      1          eng$aspa$afre$ager$aita$achi$ajpn

Conference proceedings with some papers in English and some in German (i.e. no translations involved).

040      0          eng$ager

 

043 Geographic area code

This should be used for nonfiction materials which are about a specific geographic place (PCC RDA BSR). See the MARC21 codes list at www.loc.gov/marc/geoareas/ (or the Cataloging calculator at calculate.alptown.com/) for appropriate values.

 

100/110/111 Creator main entry

For personal or corporate main entry, follow the same procedures as would be followed for the material in regular format (i.e. for text, follow books practice, for music, follow music practice). In general, if there is a single person who created the work, put that name in the 100 field (RDA 6.27.1.2).  .  Of two or more are responsible, see if one person has principal responsibility and put that name in the 100 field (RDA 6.27.1.3).   If the principal responsibility is not indicated, use the first named person and make 700s for the rest of the people (RDA 6.27.1.3).    If the work is a compilation of works by different persons, do not use a 100 field (RDA 6.27.1.4) unless it is conference proceedings (see next paragraph).  If there is a named editor, put his name in the 700.

Only make a corporate body the 110 field when the corporate body issued a work or caused it to be issued AND the work is either  a work about itself, a work that records the collective thought of a body (reports  of commissions or, official statements of position, etc (RDA 19.2.1.1.1).  Rules are different for cartographic, legal, and music works, see RDA 19.2.1.1.1 for those).  For conference proceedings,  put the name of the conference in the 1XX field when the conference is named in the resource being cataloged, and add the number of the conference (RDA 11.6), the date (RDA 11.4.2) and the location or associated site when the local place name is not known (RDA 11.3.2, 11.5).  A conference is put in the 111 field, unless the name is subordinated to a corporate body, such as an annual meeting of a body, in which case the name of the body goes in the 110 field and the conference designation goes in the $b.

110      2          American Library Association. $b Meeting$d(2011 : $c New Orleans, La.)

111      2          Joint Conference on Digital Libraries $n (4th :$d2004:$cTuscon, Ariz.)

 

Look up the name of the person or corporate body in NAF and use that form.  If the name is not in NAF, formulate as per RDA, and, if doing BIBCO cataloging, create a NAR. In general, use the name as it is given (RDA 9.2.2), if a fuller name is known, add those additional parts in parentheses (RDA 9.5.1, LC-PCC-PS 9.5), add appellations like Jr. (9.2.2.9.5), routinely add birth and death dates if known (RDA 9.3), use an open date if the birth date but not death date is known, even if the person is obviously dead (LC-PCC-PS 9.3.2.3), flourished or active dates are permissible, and, if there is no other way to distinguish the heading, add an indication of their field of activity (RDA 9.15) or profession or occupation (RDA 9.16), e.g. biologist, economist, statistician, etc. in parentheses.

When using a 100, 110, or 111 field, it is usually necessary to add a $e with a relator term (PCC Guidelines for the Application of Relationship Designators in Bibliographic Records says to add relators to all creators). Per RDA 18.5, and using terms in RDA Appendix I,  find a relator term which describes the relationship of the person or corporate body to the resource and put that in a $e.  If there are multiple applicable terms, put them in repeated $e subfields. The terms are in lower case.  There is a comma preceeding each term, except for open dates.   If there is no appropriate relator term, either make up a suitable term or do not add a term.  There is as yet no appropriate term for a conference (Message from J. Kuhagan, LC), and if there were, the term would go in $j instead of $e (MARC21).

100      1          Shakespeare, William, $d 1564-1616,$eauthor.

111      2          Joint Conference on Digital Libraries $n (4th :$d2004:$cTuscon, Ariz.)

This field should end with a period or other mark of punctuation (LC-PCC-PS 1.7.1)

NACO catalogers should make a NAR in most cases for a heading which is not established. BIBCO records must have all headings established.

When there is no person or corporate body who qualifies as main entry, then it will be a title main entry.  A 130 field might be necessary.

 

130  Preferred title (when there is no 1xx field)

A 130 field may be necessary if there is no 100, 110, or 111 field. Generally this field would be used (1) when the resource being cataloged was originally issued under another title or has a title in NAF that is different than what would be in the 245 field or (2) when the resource being cataloged is or contains a translation (and is the only version in the resource), or (3) if it is the same as a subject heading or (4) if it has the same preferred title as a different resource in OCLC (LC-PCC-PS 6.27.1.9, section on monographs). If the title is in NAF, enter that title in the 130.  If the resource is a translation, add a $l with the language of the translation.  If there is the original language and a translation, make a 730 for each language and do not use a 130.  If the title is the same as a subject heading or the same as the preferred title of a different resource, qualify  with one or more of the following: corporate body, date of publication, descriptive data elements (e.g. edition statement), place of publication.  These are not in priority order, use whichever makes the most sense in the circumstance.  Politely ignore the fact that you are qualifying a work with attributes of the manifestation.

 

130      0          Bible.$lLatin.$sVulgate.

130      0          Bolivia (2012)

 

This field should end with a period or other mark of punctuation (LC-PCC-PS 1.7.1)

 

240 Preferred title (when there is an 1xx field)

Generally this field would be used when there is a 100, 110, or 111 field and (1) when the resource being cataloged was originally issued under another title or has a title in NAF that is different than what would be in the 245 field or (2) when the resource being cataloged is or contains a translation.   If the title is in NAF, enter the $t subfield into the 240 $a and include any subsequent subfields from the NAR.  If the resource is a translation, add a $l with the language of the translation.  If there is the original language and a translation, use the original language in the 240 and make a 7xx name-title added entries for the other language or languages.

 

100      1          Shakespeare, William, $d 1564-1616,$eauthor.

240      10        Hamlet.$lMauritian French Creole

 

This field should not end with a period unless the last element is an abbreviation (LC-PCC-PS 1.7.1)

 

245 Title Proper

This field should end with a period (LC-PCC-PS 1.7.1)

Choose the title which appears on the source of information (RDA 2.3.1.4).  

Per LC-PCC-PS 2.2.2.2, take the title from the label (RDA 2.2.2.2 says if the resource is digital text or music and has a title page, use  the title page or, alternatively, the label).  If there is no label, use the title page.  If the resource lacks a label or title page but has the image of a cover, use that.  If neither of those apply and the resource has an internal title screen or splash or  start screen or home page, use that for the title or use the label (RDA 2.2.2.4, if interpreting the title screen as embedded metadata rather than the image of a title page)  If the resource consists of multiple works, with or without their own titles, try to find a collective title.  Prefer the label, but if there is not an adequate title on the label, look for an internal title screen or splash or start screen, and, lastly, the container.  If the resource is video files, use the procedures for video [RDA 2.2.2 3link to video rules].  For a video game, though RDA 2.2.2.3 says to use the title frame, follow LC-PCC-PS 2.2.2.2 instead and  use the label—one generally doesn’t have the equipment to load most video games anyway.

When transcribing the title, either follow RDA Appendix A (basically the old AACR2 capitalization practice) or transcribe the title exactly as it appears, including capitalization and punctuation (RDA alternative for 1.7), whichever is easier and clearer (SUL decision).  Don't change the capitalization, however, if you are deriving from another record or copying and pasting data (SUL decision).  You may supply missing diacritics if known.

Many video game titles consist of a franchise title and either a number or a specific title of that work.  Avoid giving the franchise title alone as the title proper, as under the provisions noted in the 130 the franchise title will conflict with other games from the same franchise as well as any associated motion picture or television programs. Within the gaming world these games are referred to by the full title, so generally either run all the title elements together or, if that's too gramaticalll weird, separate with a comma.  A game individual title could be treated as a subtitle in the case of the franchise title with a number that uniquely identfies that work.  Avoid treating individual titles and numbers as parts.

 

245      10        Hamlet

245      10        Camp Lazlo, Leaky Lake games

 

If there is no title anywhere devise a title (LC-PCC-PS 2.3.2.11) that indicates the nature of the resource, its subject (e.g., names of persons, corporate bodies, objects, activities, events, geographical area and dates) or a combination of the two, as appropriate (RDA 2.3.2.11).  The title should be in English (LC-PCC-PS 2.3.2.11) and should be in brackets (RDA 2.2.4, LC-PCC-PS 2.2.4).

If there is a statement of responsibility, add it in $c.  Only the first is required (RDA 2.4.1), but that one should be transcribed in full, unless there are so many names as to be burdensome (SUL decision).  If that’s the case, transcribe the first and follow with [and number others].  Remember to trace all creators, though, even if not transcribed.  Optionally, transcribe other statements of responsibility if they are important.

 245    10    PRESERVING VIRTUAL WORLDS / $c Jerome McDonough [and nine others].

Collections with a collective title

For a disc or other computer carrier consisting of  multiple works issued as a single unit (e.g. 1 CD-ROM) with a collective title use the collective title as the title proper in the 245 (RDA 2.3.2.6, 2.1.2.2: “choose a source of information identifying the resource as a whole” However, if one work is predominant and the others are subsidiary or minor works. choose the source related to the predominant work (RDA 2.1.2.2), If the resource is issued in more than one part, choose the lowest number or earliest date, if applicable. If not applicable, choose a source of information identifying the resource as a whole (RDA 2.1.2.3). If neither is applicable, choose the source for the predominant part. (RDA 2.1.2.3)

In these cases, use either formal or informal contents notes to list the rest to list the titles of the individual works. [RDA 24.4, 25.5.1.3]. Use an informal contents note in a 500 field  for miscellaneous minor works  or works with weak or nonexistent titles.  You may also  make title added entries for the individual titles (RDA25.1), for significant works that may be sought out on their own (Generally, do not apply this core element to anthologies of poetry, conference proceedings, journals, collections of interviews or letters, and similar resources, c.f. LC RDA FAQ). When doing this, Use field  700 with a $t subfield for works with personal authors or 730 for works with title main entry, and also use 740s if any of the works require a variant title. (LC-PCC-PS 25.1.1.3 is not to use enhanced contents.) There is no limit on the number of works to list in the contents unless “the content note would be SO LONG it would be burdensome to input that much information..”(LC RDA FAQ) and no limit on added entries, though only the first is required.

500                 Also contains reports from the various subsidiary groups and QuickTime videos of the opening and closing ceremonies.

505      0          Title one / Statement of responsibility – Title two / Statement of responsibility – Title three / Statement of responsibility.

Collections without a collective title:

For a resource consisting of multiple works with no collective title that is issued as a single unit (e.g. 1 CD-ROM) treat the sources of information identifying its individual contents as a collective source of information for the resource as a whole (RDA 2.1.2.2). Record the titles proper of the parts in the order in which they appear in the resource. (RDA 2.3.2.9). If the resource is issued in more than one part, choose a source of information identifying the main part, if there is one part that can be considered the main part of the resource. Otherwise, treat the sources identifying the individual parts as a collective source of information for the resource as a whole (RDA 2.1.2.3). Note that the titles of different works are separated by a period (followed by two spaces) if they are by different persons or bodies, but by a semicolon if they would have the same statement of responsibility (assume the first example would have the same credits) (ISBD punctuation described in AACR2 1.1G3, not in RDA Appendix D.1.1)

245      00        Title of first work ;$bTitle of second work.

245      00        Title of first work /$cstatement of responsibility for the first work. Title of second work/ statement of responsibility for the second work.

 

Note that when the second or subsequent titles follow a statement of responsibility, they are not individually tagged. In other words, once there is a $c, no other tag can follow it. In practical terms, this method doesn’t work well if there are more than two works, particularly if there are statements of responsibility. If it seems more practical, devise a title (RDA 2.3.2.9 Alternative, though LC says generally not to do this in LC-PCC-PS 2.3.2.9) This works best if the titles are related in some way (a common theme or topic, or all associated with the same person or body) so that one can devise a title English (LC-PCC-PS 2.3.2.11) that indicates the nature of the resource, its subject (e.g., names of persons, corporate bodies, objects, activities, events, geographical area and dates) or a combination of the two, as appropriate (RDA 2.3.2.11). The title should be in brackets.

Be sure to trace all the titles in 730 fields , and 740 fields if any of the title have variants on the item that are not the same as the 730. These titles should not be traced individually the 246 field.  

245      00        BANJO-KAZOOIE : $b NUTS & BOLTS / $c RARE. VIVA PIÑATA / RARE.

730      02        $i Contains (work) $a Banjo-kazooie.

730      02        $i Contains (work) $a Viva piñata.

 

 

246 Title variations

Record variant versions of the title that are important for identification and access (RDA 2.3.6.3)  in the 246 field (LC-PCC-PS 2.3.6.3) This is only for variants of the main work or collective title (e.g. the work or title that appears in $a of the 245 field. Separately titled works go in the 730  (RDA 2.1.1.3). Variant for a title of a component work when the resource contains more than one work would be recorded in 740 (LC-PCC-PS 2.3.6.3)

This field does not end with a period unless the last element is an abbreviation (LC-PCC-PS 1.7.1)

 

 250 Edition

Transcribe an edition statement that appears on the source of information (RDA 2.5.1.4)   You may transcribe it exactly as it appears, including capitalization and punctuation or apply Appendix A (old AACR2 capitalization), whichever is easier (SUL decision).  However, do not abbreviate anything which is not abbreviated on the piece.  The source should be, in order of preference, the same source as the title, another source within the resource, accompanying materials, or container, or an outside source such as a reference source (RDA 2.2.4).  If it comes from outside the resource, put it in brackets (RDA 2.2.4 LC-PCC-PS 2.2.4). In case of doubt about whether a statement is a designation of edition, consider the presence of a word such as edition, issue, release, level, state, or update or a statement indicating: difference in content, a difference in geographic coverage, a difference in language, a difference in audience, a particular format or physical presentation, a different date associated with the content, a particular voice range or format for notated music as evidence that such a statement is a designation of edition.  If  the edition is merely a number or other such designation with no accompanying words, add an appropriate word in brackets (RDA 2.5.2.3). If a resource lacks an edition statement but is known to contain significant changes from other editions, supply an edition statement, if considered important for identification or access.  Bracket this statement (RDA 2.5.1.4 optional addition)

End the field with a period.  If an abbreviation with a period has already been recorded, add another period. (RDA D.1.2.5)

250                 2nd edition. [appears as 2nd edition on the piece]

250                 2nd ed..  [appears as 2nd ed. on the piece]

250                 CLASSROOM VERSION.

250                 [Version] 10.

 

 

264 Place of Publication, Publisher, Date

This field should end with a period or other mark of punctuation (LC-PCC-PS 1.7.1), except for a copyright date (PCC 264 guidelines).

Computer discs often present challenges in this area. There are often many corporate bodies listed on the disc or container and sometimes difficult to decide which is the publisher. Some are the names of the sponsoring or distribution corporate body, some are the names of content developers, as is often the case with computer games.

The source of information would preferably be from the same source as the title, but if it is not there it may be taken from the disc label, accompanying material, or container (RDA 2.2.4)

Transcribe places of publication and publishers' names in the form in which they appear on the source of information (RDA 2.8.1.4) You may transcribe it exactly as it appears, including capitalization and punctuation or apply Appendix A (old AACR2 capitalization), whichever is easier (SUL decision).  However, do not abbreviate anything which is not abbreviated on the piece

If there is more than one publisher, record the first place and publisher (RDA 2.8.2)  Record the others if recording only the first would be misleading.  If there is no publication information stated, always try to infer it, to avoid the complications noted below.

When transcribing the place of publication, include both the local place name (city, town, etc.) and the name of the larger jurisdiction or jurisdictions (state, province, etc., and/or country) if present on the source of information (RDA2.8.2.3). If there is no place of publication stated on the item, try to infer a place of publication.  If the publishers name is known or is represented by a URL, search the web to see the location of that publisher and put it in brackets unless the country is obvious. If you cannot infer or locate a place of publication, you must input the phrase: “Place of publication not identified” in brackets (RDA 2.8.2.6.) in the 264$a, and you must add a place of distribution, if stated, in another 264 field with a second indicator 2 (RDA 2.9). If there is no place of distribution, transcribe a place of manufacture in another 264 with second indicator 3 (RDA 2.10)  [can you abbreviate inferred places? No per Appendix B]

Optionally, when transcribing a publisher name, omit levels in a corporate hierarchy that are not required to identify the publisher. Do not use a mark of omission (…) to indicate such an omission (RDA 2.8.1.4).  If there are multiple publishers, they go in the same 264 field.  If there is no publisher stated on the item, try to infer a publisher.  If there is a URL and no named publisher, generally assume that the URL belongs to the publisher and search the URL to see if you can find the name and put it in the record in brackets. If you cannot infer or locate a publisher, you must input the phrase: “Publisher not identified” in brackets (RDA 2.8.4.7) in the 264$b, and you must add a distributor, if stated, in another 264 field with second indicator 2. If there is no distributor, transcribe the manufacturer in another 264 field with second indicator 3 (RDA 2.10)

Here are some random examples:

264      _1        Genève :$bUNIVERSITÉ DE GENÈVE, Département de minérologie, FACULTÉ DES SCIENCES, $c2009.

 

264       _1       Bern, Switzerland :$bPresence Switzerland PRS,$c[2006]

 

264      _1        [Place of publication not identified] : $b [publisher not identified],],$c [2002]

264      _2        Chatsworth, Calif. :$bImage Entertainment,$c[2002]

 

 

264      _1       [Ghana] :$bGhana Geological Survey Department ;$a[Germany] :$bBGR, Bundesanstalt für Geowissenschaften und Rohstoffe,$c[2006?]

 

264      _1       [Place of publication not identified] :$b [publisher not identified],$c [Between 1997 and 2011]

264      _3       Palo Alto, CA : $b Acme Duplication Service, $d [2011]

If the resource is unpublished, the place of production and the producer are optional if known (RDA 2.7, only date is core).  If not known, simply supply the date of production (RDA 2.7, message from D. Reser, Oct. 16, 2010), and do not bracket it if it is a known date.  Only bracket if the date is approximate or inferred from the copyright date (LC-PCC-PS 2.8.6.6).  Use field 264 with second indicator 0.

If the resource is an unpublished reproduction,  input the place of production of the copy (RDA 2.7.2) and the name of the person or corporate body which created the copy (RDA 2.7.4), unless it is a locally-made reproduction.  If they are not given on the item but may be inferred, supply them and bracket them (RDA 2.7.2.2, 2.7.4.2).  If they cannot be determined, omit the $a and $b and only give the date in $c.  For locally-made reproductions, only supply $c and not $a or $b.  Second indicator will be 0.

264      _0        $c[between 2000 and 2010?]

Date of Publication

Record the date of publication as stated on the item (RDA 2.8.6.3).   If the date of publication is not identified in the resource, supply the date or approximate date of publication (RDA 2.8.6.6). Apply the instructions on supplied dates given under RDA, 1.9.2 and put it in brackets.  If inferring the publication date from the copyright date you may follow it with a question mark if you feel uncertain.  Here are various examples of inferred dates:

[1969?]

 [1971 or 1972]  

 [between 1970 and 1979?]

[not after 2010]

If an approximate date of publication for a resource that is in a published form cannot reasonably be determined, record the phrase : “date of publication not identified” in $c in brackets. (RDA 2.8.6.6, LC-PCC-PS 2.8.6.), but LC says generally don’t do this. 

Though LC-PCC-PS 2.8.6.6 and 2.11 say that LC policy is to not add a copyright date in most cases, it is not incorrect to do so, and SUL policy is to leave it to cataloger's judgement.  When adding a copyright date, you would put the copyright date in a second 264 field with second indicator 4 and precede the copyright date with the copyright symbol © and not end with a period.  In this case you would code the 008 DATE “t”.

264      _1        $cBern, Switzerland :$bPresence Switzerland PRS,$c[2006]

264      _4        $c ©2006

If the resource is unpublished, supply a date (RDA  2.7.6.3). and do not bracket it if it is a known date. Only bracket if the date is approximate. If the item is a locally-made reproduction, the date should be for the date the copy was made.

264      _0        $c2010.

264      _0        $c[between 2000 and 2010?]

Also, it is permissable to record multiple copyright dates that apply to various aspects (text, sound, presumably packaging ....), according to RDA 2.11.1.3. 

 

300 Physical Description 

In $a, state what type of computer medium it is according to the list of official terms in RDA 3.3.1.3 listed below, and give the number of units.  If more than one unit, give the name of the unit in plural (RDA 3.3.1.5).

computer card

computer chip cartridge

computer disc

computer disc cartridge

computer tape cartridge

computer tape cassette

computer tape reel

If there are multiple pieces with different characteristics (e.g. a  CD-ROM and a floppy ), choose one as the predominant component and the other as the accompanying component (LC-PCC-PS 3.1.4).  Either put the accompanying component in a separate 300 field or in a $e (LC-PCC-PS 3.1.4, No SUL decision.  My opinion: Prefer a separate 300 field unless the accompanying component is clearly supplementary, such as an accompnying booklet or instruction sheets)

If the resource consists of one or more files in a format that parallels a print, manuscript, or graphic counterpart (e.g., PDF), specify the number of subunits by applying the instructions for extent in parentheses after the name of the unit ( RDA 3.4.1.7.1—for cartographic resources see 3.4.2,  for notated music see 3.5.3,  for  still images see 3.4.4, for text see 3.4.5), as appropriate.  Don't add if it is difficult to determine or burdensome.

1 computer disc (1500 remote-sensing images)

1 computer disc (xv, 300  pages, 150 maps)

1 computer disc

 

 For other types of files (e.g., audio files, video files, data files), specify the number of files using one or more terms listed under  3.19.2.3 to designate the file type. If there are many files or files of different types, do not include this information.  Put it in a 516 note if considered important. See also the 347 field.

 

1 computer disc (8 audio files)

1 computer tape (3 data files)

1 computer disc (1 audio file, 3 video files)

 

Optional Addition:  For a resource consisting of one or more program files and/or data files, add the number of statements and/or records, as appropriate.

1 computer tape (3 data files: 100, 460, 550 records)

 If the number of subunits cannot be stated succinctly, record the details in a note if they are considered important for identification or selection, (RDA 3.4.1.7.1, with instructions to see RDA 3.22.2.10)

Note, RDA gives the option of a term in common usage (presumably CD-ROM, DVD-ROM, Blu-Ray, Game cartridge, as well as  USB flash drive, etc). for the 300 $a,  (RDA 3.4.1.3 option—LC-PCC-PS says generally use the list in 3.1.1.3, but can  use catalogers judgment on the option and report any new names to PSD).

If the resource is not primarily audio, add "sound" if present, (RDA 7.18). See also field 344 for sound information.  If the content is primarily textual, state whether there are illustrations ( RDA 7.15), and give color if present (7.17.3). 

300                  1 computer disc (xi, 525 pages ) :$b color illustrations ;$c4 ¾ in.

300                  1computer disc (15 video files) :$b sound, color, ;$c4 ¾ in.

300                  1 audio disc (140 audio files ) ;$c4 ¾ in.

300                  1 computer disc :$bcolor illustrations;$c4 ¾ in.

300                  1 computer disc :$bsound, color ;$c 4 3;4 in.

300                  1 computer disc :$bsound, color, $c4 3/4 in.

300                  1 USB flash drive :$bcolor, $c 7 cm


In $c, give the diameter of a disc in inches and fractions of inches: CD-ROMs, DVD-ROMs and Blu-Ray discs  are usually  4 3/4 in.  (LC-PCC-PS 3.5.1.3).  For cards record height × width in centimeters  (RDA 3.51.4.1); for cartridges record the length of the side of the cartridge that is to be inserted into the machine in centimeters (RDA 3.5.1.4.2);  for cassettes, measure the length x height of the face in centimeters  (RDA 3.5.1.4.3) ; for computer tape reels, record the diameter of the reel in centimetres followed by the width of the tape in millimeters.  Centimeters and millimeters are represented as cm and mm respectively, with no periods.  There are no instructions on how to measure a USB flash drive; so, since the size of the plug is standard, local decision is to just measure the length.  If on copy more measurements ae given, accept without editing.

9 × 6 cm

Dimensions of a computer card

10 cm

Dimensions of a computer chip cartridge

6 cm

Dimensions of a computer cassette

31 cm, 13 mm tape

Dimensions of a computer cassette

 

When the field ends with “in.” (RDA B.7), which does have a period, and there is a series statement, add a second period.  (ISBD presumably).  If the field ends with a cm, add a single period.

300                  1 computer disc (xi, 525 pages ) :$b color illustrations ;$c4 ¾ in..

490      0          Bogus series ;$v volume 3.

 

300                 1 computer chip cartridge :$b black and white ;$c10 x 7 cm.

490      0          Bogus series ;$v volume 1.

 

If there is accompanying material, it all goes into one $e.   Use the name of a carrier type from RDA 3.3.1.3  (LC-PCC-PS 3.1.4), unless it is a booklet or some other material not on that list (email from Judith Kuhagan, Sept. 14, 2010).  Size and pagination of accompanying booklets are optional but may be useful for identification, if given, are in parentheses.   Information that would normally go in a 300$b and $c may also be recorded if they seem useful, but in $e there are no further subfields.  That information also goes into the parentheses (RDA D.1.2.6, LC-PCC-PS 3.1.4). Note these only if substantial or necessary for the use of the item.  Ignore minor materials, such as a sheet with chapter listings.  If there is accompanying material in a paper format, record the size of that material in centimeters.  Use “cm” and only add a period if it is the end of the field and there is a series statement.   If you include accompanying material within the description, you need 336,  338 fields and 337 if for the accompanying material, too (email from Judith Kuhagan, LC, Sept. 20, 2010)

300                  1 computer disc :$b color illustrations ;$c4 ¾ in. +$e1 booklet (29 pages : color illustrations, 19 cm)

 

336   Content type

Record the content type from the list in RDA 6.9.1.3.  Record as many as are applicable, including for accompanying material (email from Judith Kuhagan, LC, Sept. 20, 2010). Alternatively, record only for the predominant part of the work or most substantial parts if applicable (RDA citation?).  If adding for accompanying material, begin each field with a $3 to denote to which object the term applies (Music best practices)

336                  $a text $2 rda content

 

336                  $a two-dimensional moving image $2 rdacontent

 (for a digital movie, such as MPEG, flash, etc.)

 

336                  $a three-dimensional moving image $2 rdacontent

 

336                  $a performed music $2 rdacontent

(for a sound or video file of a musical performance or performances)

 

336                  $a spoken word $2 rdacontent

(for a sound  file of human speech)

 

336                  $a sounds $2 rdacontent

(for a sound file of  sounds which are not language or music)

 

336                  $a still image $2 rdacontent

(for still images)

 

336                  $a two-dimensional moving image $2 rdacontent

336                  $a text $2 rdacontent

(for a disc containing substantial textual and moving image content)

 

336                  $a two-dimensional moving image $2 rdacontent

336                  $a computer program $2 rdacontent

(for a two-dimensional video game per JSC/OLAC example.  Per RDA 6.9.1.3 a video game which is not three-dimensional is a two-dimensional moving image)

  

336                  $a computer dataset $2 rdacontent

336                  $a computer program $2 rdacontent

(for a disc with data and software with neither clearly predominant)

  

336                  $a two-dimensional moving image $2 rdacontent $3 computer disc

336                  $a text $2 rdacontent $3 volume

(for a disc containing  moving image content with an accompanying book)

 

When the content type can’t be described by any of these, use “other.”  If the content can’t be determined, use “unspecified” (RDA 3.9.1.3)

 

 

337 Media type

This field indicates the “General type of intermediation device required to view, play, run, etc..” (RDA 3.2, LC-PCC-PS 3.2).  Use “computer.”  Also add for accompanying material (email from Judith Kuhagan, LC, Sept. 20, 2010, if going beyond RDA core).  When using theis field for multiple objects such as accompanying material, add a $3 at the beginnindenoting to which object the term applies.

337                  $a computer $2 rdamedia

337                  $a computer $2 rdamedia

337                  $a audio $2 rdamedia

(for a disc primarily of sound on a computer disc, e.g. MP3 files) (Music Best Practices)

 

337                  $a computer $2 rdamedia $3 computer disc

337                  $a unmediated  $2 rdamedia $3 volume

(for an accompanying book)

 

338 Carrier type

This field indicates the storage medium and housing of the resource.  (RDA 3.3)  If more than one type is applicable, record all that are applicable (see RDA 3.3.1.3 for the list of perissible values) or alternatively to the predominant part or most substantial part—use your own judgement on which to do (RDA alternatives and options -- LC proposed practice for the RDA Test). For sound encoded on a computer disc (e.g. MP3 files), encode both audio disc and computer disc. If you have an accompanying booklet in the 300 $e, add a 338 for volume (RDA 3.1.4.1).  (SUL policy?  This seems like it should be catalogers judgement)  When encoding this field for multiple objects, add a $3 to the beginning of each to denote to which object the term applies (Music best practices)

338                  $a computer disc $2 rdacarrier

 

For a computer disc encoded with sound files (e.g. MP3 files) (Music best practices)

338                  $a computer disc $2 rdacarrier

338                  $a audio disc $2 rdacarrier

For an accompanying book

338                  $a computer disc $2 rdacarrier $3 computer disc

338                  $a volume $2 rdacarrier $3 volume

  

For a USB flash drive or a hard drive

338                 $a other $2 rdacarrier

 

344  Sound characteristics

For resources with sound (including audio and video resources) record "digital" in $a (RDA 3.16.2.3) with $2 rda.   Optionally, add $b optical (RDA 3.16.3.3); $e mono, stereo or surround (RDA 3.16.8.3), and in $h, other special playback characteristics such as Dolby (RDA 3.16.9.3)

344                  digital  $2 rda

 

346  Video characteristics

For resources with video (including some types of video games), record the video broadcast standard if applicable in $b. RDA gives the types HDTV, NTSC, PAL and SECAM, so if it's one of those, also add $2 rda (RDA 3.18.3.3)

346                  $b NTSC  $2 rda

 

347  Digital file characteristics

File type

Give the file type, in singular, from the list in RDA 3.9.2.  Repeat the $a when there are multiple file types (SUL decision).  Do not give the file type for complex resources with multiple files of various types (e.g. multimedia, games, etc.)

audio file
data file
image file
program file
text file
video file

Encoding format

In $b, give the encoding format if readily discernable (RDA 3.19.3). If encoding format is too complicated to be explained in the 347 $b and is considered important, explain it in a second 538 field (RDA 3.19.3.4, RDA Appendix D.2).  Use     $2 rda when the term used is on the list at 3.19.3.  If it is not in the list, do not a $2 rda.  If there are multiple files with different encodings and some are on the list and some are not, make two 347 fields, one with the rda terms and one with the others.

347                  text file $b  PDF $c 1.2 MB  $2 rda

347                  video file $b MPEG4 $c3 GB $2 rda

347                  audio file $bMP3 $2 rda

347                  text file $a image file $b PDF, HTML, JPEG $2 rda

347                  $b Xbox 360

347                 $b PlayStation 3

 

347                  video file $c3 GB $2 rda

347                  $b Flash

(the latter two being for a CD-ROM with a Flash video--esentially forcing the 347 to have a mix of rda and non-rda terms.  In this case, make two 347 fields, one with the RDA terms and one without.

 

File size

In the $c, add the file size if it can be readily ascertained and is considered important. Give file size in bytes, kilobytes (KB), megabytes (MB), or gigabytes (GB), as appropriate. (RDA 3.19.4)

Resolution:

In $d, add resolution (RDA 3.19.5) if known and considered to be important.

Region coding

Video games may theoretically be region coded.  If that occurs, put the region in. U/C (as in NTSC U/C) is the region code for US and Canada, J is for Japan.  It is unclear whether RDA can be construed to have a list of region codes (it gives only region 4 and all regions in RDA 3.19.6.3) so it's best not to use $2 rda.

 

380 Form of work

(RDA 6.3) Record the form of the work if it seems useful to do so. Form is a class or genre to which a work belongs. [No idea how this should be punctuated]

380                  Computer game (SUL interim policy: give type of game like first-person shooter) 

380                  Video game

380                  Video games.  Banjo-Kazooie is a three dimensional platform style action game; Viva piñata is a life development simulation game.

380                  Novel

4xx Series (490, 830)

 

Transcribe the series from the resource (RDA 2.12.2.3, refers to 2.3.1).  You may transcribe it exactly as it appears, including capitalization and punctuation or apply Appendix A (old AACR2 capitalization), whichever is easier (SUL decision).  If the source of information for the series title proper bears a title in more than one form, and if both or all of the titles are in the same language and script, choose the series title on the basis of the sequence, layout, or typography of the titles on the source of information. If the sequence, layout, and typography do not provide the basis for a clear choice, choose the most comprehensive title. (RDA 2.12.2.5 refers to 2.3.2.5)

Search NAF for a series.

If the series is not in NAF and you don’t feel strongly that it should be established in NAF, record it in a 490 field with first indicator 0.

490                  0          Example

If the series is found in NAF, follow the tracing practice indicated. If the authorized title is exactly the same as that on the item, put the series in the 490 field with a first indicator 1, and put the same thing in the 830 field with a second indicator 0. Include numbering if appropriate.

490                  1          Example ;$v. 1

830                  0          Example  ;$v. 1

 

If the authorized form of the series is not identical to that on the item (often due to the addition of a parenthetical qualifier or an initial article), transcribe the form that's on the item in the 490 field with a first indicator of 1. Transcribe the authorized form in the 830, with a second indicator of 0. Include volume numbering if present.

490                  1          Example

830                  0          Example

 

 

If the series in NAF is for the paper version and you are cataloging the CD-ROM version, use the form given in NAF (SUL decision).

 

490                  1          Example

830                  0          Example

 

 

If the item is a reproduction of a previously published resource (as opposed to a simultaneously published one) , transcribe the series statement in the 776 $k.  If there is a series authority record for the series on the original resource, use that form in the 830 (LC-PCC-PS 6.27.1.9)

 

490                  1          Example

830                  0          Example

 

If uncertain if a statement is really a series, alternatives include: ignoring it, putting the statement in quotes in a 500 notes, or making a 246 title added entry with the wording "additional title on container" or "at head of title on disc" or something of the like.

 

5XX Notes

For 5XX notes, an ending mark of punctuation is a period ( . ), quotation mark ( " ), question mark ( ? ), exclamation mark ( ! ), hyphen ( - ; used at the end of an open date, etc.), and (LC practice/CONSER practice) angle bracket ( > ). End each note with a period or other mark of ending punctuation. (LC-PCC-PS 1.7.1)

 

538 System requirements

Record any equipment or system requirements as they are presented on the resource (RDA 3.20.1.3 alternative, LC-PCC-PS 3.20.1.3).  There is no requirement to begin with the term: System requirements, transcribe whatever it says on the piece.  It does not appear that this needs to be a quoted note (based on example in RDA 3.20.1.3)

538                  For use only with Xbox 360 entertainment systems with "NTSC" designation; Xbox live

features optional.

The list of encoding formats at RDA 3.19.3.3 currently includes some disc types (DVD-R, Blu-ray is ambiguous as to whether they mean encoding or disc type).  Those are in error and are probably going to be removed. CD-ROM and DVD-ROM are not mentioned as data elements in RDA.. Moreover, it is often important to note whether a disc is a recordable disc rather than the standard pressed discs.  Recordable discs can be told by the bluish hue of the recorded side of the disc.  These do not always play in all machines.  When cataloging a computer disc, make a disc characteristics note giving the type of disc (no official RDA mapping, this is based on OCLC Bib Formats 538 and MARC 538 examples)

 

538                  Disc characteristics: CD-ROM.

538                  Disc characteristics: CD-R.

538                  Disc characteristics: DVD-ROM.

538                  Disc characteristics: Blu-ray.

 

500  Source of title note

 

Make a note on the source from which the title was taken if  the title was taken from the label.  If the title was not taken from the label, make a source of title note unless 1.) the contents are textual and are presented as images of pages and the title was taken from the title page, or 2.)  if the contents are video and the title is taken from the title frames (RDA 2.17.2.3, LC-PCC-PS 2.17.2).

 

502  Dissertation note

 If the video is a theses, dissertation or anything else produced for academic credit, put the note in a 502 field (RDA 7.9.1, 7.9.2, 7.9.3)  Use subfields a,b,c, and d for the information (LC-PCC-PS 7.9.1.3)

502                  $b Ph. D. $c University of Toronto$d 1974.

 

If the resource lacks a formal thesis statement containing information related to the sub-elements, state its origin as a thesis in a general note (MARC field 500) when this information is readily available. Include in the note only the sub-elements (degree, institution, date) that are available. (LC-PCC-PS 7.9.1.3)

500                   Originally presented as the author’s thesis under title: …

516  Type of computer file/data

If the number and type of files could not be included in the 300, they may be described in this field if considered important (RDA 3.19.2.3).  Do not do this routinely (Local decision)

 

538 Digital file characteristics

If it is considered to be important, record the resolution in a separate 538 field (RDA 3.19.5), For digitally encoded cartographic content, record (in addition to the applicable characteristics listed above) data type, object type, and number of objects, as instructed under RDA 3.19.8.  If encoding format is too complicated to be explained in the 300 and is considered important, explain it here (RDA 3.19.3.4, RDA Appendix D.2)

538      2048×1536 pixels.

 

546   Language note

(RDA 7.12, 7.14) Record details of the language or languages used to express the content of the resource if they are considered to be important for identification or selection. Include when the content is in more than one language, or if the language of the item is not obvious from the rest of the record.

546                 In German with English summaries.

546                 In English, French, German, Italian, Spanish, Portuguese, Chinese, Japanese, Thai.

546                 In Mauritian French Creole with French introduction.

 

500 Related works/expressions/manifestations

Make a note if the resource being cataloged  is based or related to another work. (RDA 24.4.3, D.1.1 says 25.1). This note is not required, and should not be made if it merely duplicaties the information in the related work added entry.  The note may be structured or unstructured.

500                  Activities are based on the book How the brain learns, by David A. Sousa, 3rd edition, 2006

You may also use the 500 for an informal contents note (RDA 24.4, 25.5.1.3). Use an informal contents note for miscellaneous minor works  or works with weak or nonexistent titles, or to summarize a collection with too many works to list in a 500

500                 Also contains reports from the various subsidiary groups and QuickTime videos of the opening and closing ceremonies.

 

505  Contents note

 

If there is more than one work in the resource and those works are formally titled works which have had or could have an independent existence, use a formal contents note. (RDA 24.4, 25.5.1.3, LC-PCC-PS 25.1.1.3). Do not use an enhanced contents note (LC-PCC-PS 25.1.1.3).  Record the titles proper that appears in the source that provides the best identification (LC-PCC-PS 25.1.1.3).   Also record the first statement of responsibility (LC-PCC-PS 25.1.1.3). For publications in one unit, omit chapter and section numbering.  Use a space-dash-space to separate the components. (LC-PCC-PS 25.1.1.3).  For publications in two or more units, give the volume designation that is found on the resource; separate the volume designation from the title by a period-space.

For the works named in the 505, also trace them in 7xx fields if considered important (27.1.1.30).  When tracing, use field  700 with a $t subfield for works with personal authors or 730 for works with title main entry, and also use 740s if any of the works require a variant title. Generally, do not add 7xx fields for titles contained in anthologies of poetry, conference proceedings, journals, collections of interviews or letters, and similar resources ( LC RDA FAQ). There is no limit on the number of works to list in the contents and no limit on added entries unless “the content note would be SO LONG it would be burdensome to input that much information..” (LC RDA FAQ). 

 

505      0          Title one / Statement of responsibility – Title two / Statement of responsibility – Title three / Statement of responsibility.

 

520 Summary

Provide a brief, objective summary (RDA 7.10.1.3).  Generally do not provide a summary for textual resources when you would not have done so if the work was in print format, unless a summary that can be copied and pasted is available.  If it is, quote it and provide attribution.  For video games, paste in summaries from the All Game Guide, with attribution.  Do not provide attribution for summaries devised by SUL library staff.  For summaries encountered in copy and derived cataloging, leave the summary and any attribution already present. 

520                  Multimedia disc on the history and culture of Poland.

520                  “Blah blah blah.”‑‑ Unedited summary from container.

520                  “Blah blah blah.”‑‑ Edited summary from container.

520                  “Blah blah blah.”‑‑ Provided by publisher.

520                  “Blah blah blah.”‑‑ Unedited summary from publisher’s website.

520                  “Blah blah blah.”‑‑ World Bank Web site.

520                  “Blah blah blah.”‑‑ Edited summary from All game guide.

 

6xx Subjects and Genres

Provide Library of Congress subject headings according to LC policy given in the LC Subject Headings Manual.  For computer/video games, a topical heading may be used with the $v subdivision Computer games or $x Simulation games.

650      0         Stock car racing$vComputer games.

651      0          Rome$xCivilization$xSimulation games.

 

Supply appropriate genre headings for games.  LC has not yet developed formal genre headings (authority record tag 155) for games, but according to the LC Frequently asked Questions on form genre headings (http://www.loc.gov/catdir/cpso/genre_form_faq.pdf) question 34, “If the scope note says that the heading is used for works of a given type, then it can be used as a genre/form heading. If the scope note says that a heading is used for works about (or on) a given topic, then it cannot be used as an LC genre/form heading. If there is no scope note, then the cataloger should use his or her best judgment … If a topical heading cannot be used as an LC genre/form heading, but a library would like to use it in that way, the cataloger may code it as a local heading: 655 #7 $a Interactive art. $2 local.”  And more of a clarification (sort of ) from CONSER/BIBCO operations meeting of  May 2008 “BIBCO catalogers can add 655 genre headings to BIBCO records coded with the 2nd indicator of "0". In response to a query on this topic, it was later clarified that indeed a 155 subject authority record does not need to exist in LCSH in order for it to be used as a 655-0 on a BIBCO record. The caveat is that this applies only to topical headings coded that LC uses as a form (e.g., Constitutions, but not Treaties).”  LC has in the past used “Video games” and “Computer adventure games” as headings on actual games, so it appears that those and similar headings should be authorized for use as 655s, and such records may be coded as BIBCO.  The heading “Computer games” has a scope note identifying it a topic only and may only be used as 655 _7 $2local.  Since there are no headings for specific video game genres, when cataloging a video game use the heading “Video games” and, if applicable, one or more of the specific game genres.  Many actual game genres have no LC headings, so those terms may be used in the 380 field to describe the type or genre of the game. LC also has headings for specific brands of games, such as Sega Dreamcast video games, but not for all brands.  Local policy is not to use those headings as genres.  Genre terms are not subdivided.

Presumably authorized genres are:

Video games

Computer adventure games

Computer baseball games

Computer flight games

Computer war games

Computer word games

Educational games

Simulation games

Fantasy games  (this is a narrower term from Role playing)

 

 

7xx Added Entries and linking entries

Added entries for persons and corporate bodies

These fields end in a period or other mark of punctuation (LC-PCC-PS 1.7.1)

Provide added entries for all creators (RDA 9.2, 19.2 SUL policy).   See Appendix I, RDA for roles that they seems to define “creators” (includes artists, authors, compilers of a new work (i.e. a bibliography, directory, etc.), photographers, programmers, etc.).   Use catalogers judgment to give added entries for others who are considered to be important.  For games, the person or corporate body that was game developer should generally be traced.  Search names in NAF and use that form. If there is no form in NAF, formulate a heading according to the cataloging rules.  See the 100 field for guidelines on formulating headings.

NACO catalogers should make a NAR in most cases for a heading which is not established. BIBCO records must have all headings established.

Per RDA 18.5, and using terms in RDA Appendix I,  find a relator term which describes the relationship of the person or corporate body to the resource and put that in a $e.  If there are multiple applicable terms, put them in repeated $e subfields. If you wish to trace the publisher, "publisher" is an acceptable relator term despite not being on the list (PCC Guidelines for the Application of Relationship Designators in Bibliographic Records). The terms are in lower case.  If the person’s function cannot be determined, omit the relator term.  So far, there is no term for game developer.

 

700      1          Shakespeare, William, $d 1564-1616,$eauthor.

711      2          Joint Conference on Digital Libraries $n (4th :$d2004:$cTuscon, Ariz.)

710      2          Rare (Firm)

 

 

Added entries for titles

Added entries are made for related works and for analytical works (i.e. when there is more than one work on the disc or accompanying materials).

Related work added entries (other than component part/analytical entries and reproductions)

Related work added entries are for works somehow related to the work being cataloged. This may be  the work upon which it is based, or some other relation. This work is traced in its catalog entry form: i.e. main entry and title in the original language (RDA 24.4.2, 6.27). Look for the work in NAF and use what is there. If not found there, look for an LC bibliographic record in RLIN or in the Library of Congress online catalog (consider "DCLF" records as LC records). If found, use the main entry/title combination found there (if the record has a 240 field, use instead that title, without any subfield additions). Make sure the name part of the heading is in NAF, and if they differ, use the form of the name found in NAF. If no LC record is found, find a record in RLIN or in the Stanford catalog. In this case, a NAR must be made if the record is to be a PCC record. If no record is found, trace only the author, and do not code as PCC.

Add a designator specifying the relationship (RDA 24.5.1.3) based on the list in RDA Appendix J. Put this in $i preceding the title. The relationship designation is capitalized and is followed by a colon.   Do not  add a $e designator specifying the relationship of the author to the title. (per PCC Guidelines for the Application of Relationship Designators in Bibliographic Records). The field ends with a period or other mark of punctuation (LCPS 1.7.1)

700      1          $i Based on (work):$aDoyle, Arthur Conan, Sir,$d1859-1930.$tValley of fear

700      1          $i Translation of (work): $aDoyle Leroux, Gaston,$d1868-1927..$tFantome de l'Opera.

700      1          $i Guide to (work):$aOrnstein, Robert E.$q(Robert Evan),$d1942- $tEvolution of consciousness.

730      0          $i Free translation of (work): $aBhagavadgita.

 

Analytical title added entries

Analytical added entries are made for component works within a resource--such as separately titled accompanying works or multiple named works on one disc for which it is deemed useful to have an added entry.  For analytical added entries, the second indicator is always 2. Generally, do not add 7xx fields for titles contained in anthologies of poetry, conference proceedings, journals, collections of interviews or letters, and similar resources (LC RDA FAQ). There is no limit on added entries , and only the first is required.

Do not make title added entries for routine accompanying materials such as guidebooks, study guides, instruction booklets, etc. Only make an added entry if the work looks significant enough to be sought be a user on its own, or if the title is different from the main piece and it is deemed useful to trace in case the piece becomes separated from the main work.  In this case, use a 740 to trace (LC-PCC-PS 25.1.1.3, SUL proviso).

Use a 700 name title added entry or 730 uniform title as appropriate.   For analytical added entries, the second indicator is always 2, and, precede the title with: $iContainer of (work) or Contains (expression) (per PCC Guidelines for the Application of Relationship Designators in Bibliographic Records)  Do not  add a $e designator specifying the relationship of the author to the title.  (per PCC Guidelines for the Application of Relationship Designators in Bibliographic Records) 

For example, an accompanying book by an author would be appropriate to trace:

700      12        $iContainer of (work):$aCarver, Raymond.$tShort cuts.

If it were also to contain the French as well as the English version, then two added entries would be made: one for the original language (English), and one for the translation (French version).  On this heading the language of the translation (French) would be added  in a $l. (LC-PCC-PS 6.27.3)

700      12        $iContainer of (expression):$aCarver, Raymond.$tShort cuts.

700      12       $iContainer of (expression):Carver, Raymond.$eauthor.$tShort cuts.$lFrench.

740  Uncontrolled added entries

Use 740 when a work that you are making an analytical added entry for has a variant title which should be traced.  Also use for accompanying materials if the title is different from the main piece and it is deemed useful to trace in case the piece becomes separated from the main work.  Second indicator is 2.

775, 776  Linking entry for reproductions

If the resource is a digitized version of another manifestation (an electronic reproduction), give a structured note describing the original version (RDA 27.1.1.3).  Use field 775 if it is in the same format as the original (a CD-ROM copy of a CD-ROM) and field 776 if it is not the same as the original ( a CD-ROM digital version of a book) (LC-PCC-PS 27.1.1.3).  If the original is in a series, put the series in the 775/776 in a $k and, if there is a NAR for the series, give also an 830 field. Generally punctuate fields as they would be punctuated if they were in the main body of the record (e.g. put a period at the end of $h if it is followed by $k but not otherwise (Per J. Kuhagan, there is a discrepancy between the format of  LC-PCC-PS examples and RDA examples, and the LC-PCC-PS examples are not correct)

775      0          $i Reproduction of (manifestation): $aLee, Luke S.  $ Investigation of integrity and effectiveness of RC bridge deck rehabilitation with CFRP composites  $d La Jolla, CA : Deptartment of Structural Engineering, University of California, San Diego, [2004] $h 1 CD-ROM (xxii, 296 pages) : illustrations ; 4 ¾ in. $w (OCoLC) 62115146  $w (DLC) 76005217

776      0          $i eElectronic reproduction of (manifestation): $a Ringwalt, J. Luther (John Luther) $t Anecdotes of General Ulysses S. Grant $d Philadelphia : J.B. Lippincott Company, 1886 $h 118 pages ; 18 cm $k Example series ; number $x ISSN $z ISBN  $w(OCoLC) 228784799 $w (DLC)   10032685

 

830  See 490

856 URL

If there is an online version of the resource, add an 856 field containing the URL for the online version. For the 856, use 1st indicator 4 and second indicator 1. In the $u insert the URL copied from the location window of the item

856      41       $uhttp://www.jstor.org/journals/10510761.html

Sometimes material available on the internet for a particular resource is only a subset or related material. This means materials which are not a full-text equivalent, but are instead abstracts, selected articles, tables of contents, supplementary materials, publisher information, finding aids, etc. Add an 856 field, with an appropriate public note explaining the relation of the internet materials to the work described in the record. Use $3 subfield for the note. Use 2nd indicator 1 when the material is a subset of the item, use 2nd indicator 2 when it is a related item, such as a supplement, finding aid, or publisher website.

856

42

$3Supplemental material online$uhttp://journals.wiley.com/0192- 8651/wilma/wilma.cgi/v19

 

*Revision history:

 

Updated May 2014

Per 1914 update: Updated rule number 3.4.1.5 to 3.4.1.3 for terms in common usage. Updated references from 2.20 to reflect re-numbering to 2.17

Per 6JSC/Sec/12 [2014/02/25] Fast Track document:  Changed relationship designator Contains (work) and Contains (expression) to Container of (work) and Container of (expression)

Per Fast track document of May 1, 2013, added explicit reference to 6.9.1.3 , which added video games as a two-dimensional moving image.  Still not clear when the 3-D definition changed.

 

Updated January 7, 2014

Great, i see that the text of 6.9.1.3 has been changed between the time i wrote this document, but it was never flagged in the RDA updates.  "3-D video games" is now explicitly listed as an example of 3-D moving image. So at least at this point, the intent of that category is to include games labeled as 3-D, even though it's a different sort of 3-D than 3-D movies are.   Also updated description of cartridge from inches to centimeters (sorry about missing that). Also added a tracing for publisher to the video game example and clarified the treatment of game franchise titles.  And OCLC is now specifying that $3 for 33x fields should go at the end of the field, so changed that as well.

 

Updated December 3,  2013

Oops, sorry for having forgotten to update the examples for Form in the 008!

 

Updated November 21  2013

Clarified region coding for video games.  No updates noted from November 2013 RDA updates.

 

Updated July 15,  2013

RDA July 2013 updates.  Major change per 2.1.2.2 and 2.1.2.3 to return to AACR2 practice of cataloging from the predominant work for resources which contain a predominant work plus subsidiary works.  Also some changes in the precedence of sources (2.2.2.4), allowance for a made-up edition statements (2.5.1.4), multiple copyrights (2.11.1.3)

 

Updated May 30,  2013

RDA May 2013 updates: : redefinition of two-dimensinal moving images to include video games.  PCC Guidelines for the Application of Relationship Designators in Bibliographic Records: removed $e from analytical and related work added entries, reinstated using $i for works and expressions contained, "publisher" as relator term.

  

Updated April 12, 2013

Added 007, 300 and 338 information for USB flash drive and hard drive.

 

Updated February 26, 2013

Per BSR and Music best practices, added 043, 344, 346 and 347 fields and edited 300 to remove those data elements.

Updated December 20, 2012

Changed 007 on mp3 example and add q to 006 on examples.

Updated Sept. 21, 2012 per LCPS update August 2012

Per PCC decision on LCPS 0.12, rely on 2nd indicator 2 in 700-730 fields to express Contains (work) or Contains (expression).

August 2012 LCPS update

Eliminated requirement to add language to access point for work in its original language.

June 28 2012 LCPS update June 2012

Changed instructions and examples from 260 to 264

February 21, 2012, LCPS update #2

2.3.2.9 Generally do not devise a collective title.

2.8.6.6, 2.11.1.3 copyright dates

6.27.1.9  Differentiate all titles of works, including monographs

 


« Back