SULAIR Home

Online Monographs--Cataloging (RDA)

 

Revised May 2014 per RDA April 2014 update
 
These guidelines apply to internet resources that are issued monographically (i.e. not continuing resources). The guidelines address chiefly online textual monographs but also include instructions for other types of online content.  Stanford is using the PCC P-N (Provider-Neutral) policy for most online resource cataloging, which instructs catalogers to derive cataloging for the online version from the record for the print version. However, the current PCC P-N policy appears to be to use this document:www.loc.gov/aba/pcc/scs/documents/PN-RDA-Combined.docx for deriving from RDA records and this document: www.loc.gov/aba/pcc/scs/documents/PNRDAReport20120415.docx for deriving from AACR2 records.  This is a bit of a quandary since Stanford policy is to produce all RDA records.  For the time being, try to apply the P-N policy, but for data elements that would be recorded differently in RDA, use RDA practice rather than copying from the print record (e.g. spelling out abbreviations).   The Stanford exception to P-N policy is for EEMs documents digitized from unpublished materials and mounted locally (which we do not consider to be published)
 
Sample record template for an online textual monographs (in Symphony)
 
Rec_Type a       Bib_Lvl m        TypeCtrl     Enc_Lvl   
Desc i            Entrd            Dat_Typ s  Date1 2004
Date2             Ctry xxu         Illus a    Audience
Form o           Cont b           GovPub      ConfPub  0
Festschr 0        Index 0          LitForm 0   Biog
Lang eng          Mod_Rec           Source d   
       
006         m**** ***d* ******
007        cr mn
020        ISBN if present
040        CSt$beng$erda$epn$cCSt
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     $i Available from some providers with title: $a
250        Edition as it appears on the item.
264    1    Place of publication of original :$bPublisher of original,$cDate of original.
300        1 online resource (xxx pages) :$b color illustrations. (period if there is a 490 field)
336        text$2rdacontent
337        computer$2rdamedia
338        online resource$2rdacarrier
490  0     Series title as transcribed if not in NAF [if in NAF, see 4xx]
538        Special software or hardware requirements.
500        Source of title note if needed.
588        Either Description based on online resource; title from PDF title page ([provider name], viewed [date]) or Description based on print version record.
650   0    Subject.
700  1     Name added entries,$erelationship designator.
776  08    $i Print version: $a author. $t title. $d place : publisher, year. $h xxx pages ; cm $k series $z ISBN $w (DLC) $w (OCoLC)
856   40    $u URL
 
 
Which format to use? (Leader 06)
 
Online monographs which are chiefly textual will be cataloged on the workform for books. Rec_type (Symphony)/Type (OCLC) field would be a or t. 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.
 
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.
 
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.
 
g        Video. Use for digital video files, such as MPEG, Flash, Quicktime.
 
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.  
 
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. Normally the Music Library will catalog these
 
 
Fixed fields/008
These examples in this table are the most common in online textual monographic cataloging in the book format. For further descriptions of the fixed fields for other formats, and for other applicable values, see the OCLC Bibliographic Standards and Formats or MARC 21.
 
Field Name Value       Description
 
Bib_Lvl     m     Monograph
 
TypeCtrl   blank
 
Enc_Lvl    blank  Blank for BIBCO full level cataloging, I for non-BIBCO full, 4 for local less than full catalogin.
 
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 appears to reserve the use of this code for 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). For a locally made reproduction, this should be the date of the original.
 
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      o       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 index
                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 PCC, "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. 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. The only other value to be filled in would be if it were a government publication.
 
Symphony Example for an electronic document:
006       m**** **od* ******
OCLC Example for an electronic document:
006       m      o d    
 
In Symphony the 006 can be added or edited from a drop down menu. The asterisks are added when the menu is closed.
 
 
007
 
Symphony Example for an internet resouce without sound:
007       cr cn
OCLC Example for an internet resource without sound:
007       c $b r $d c $e n
Symphony Example for an internet resouce with sound:
007       cr cna
OCLC Example for an internet resource with sound:
007       c $b r $d c $e n $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 r  for remote access
$d     for color content (values c for color, b for black and white (text with no color), m for mixed (text with some color)   
$e n  not applicable
$f  a   sound. If no sound, use blank
 
 
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).  If there is an ISBN associated with the online version, enter that ISBN.  If there is an ISBS specifically associated with the print, but it in the 020 $z and also put it in the 776 field along with the other information about the print record.  If it is unknown whether the ISBN is associated with the print or online version, put it in $z of the 020 field. (PCC P-N policy)
 
024 Other Standard Identfier
 
Some online documents contain a DOI (Digital Object Identfier).  It is core if present (RDA 2.15).  However, be careful with documents made of multiple articles in separate files, as there may be a DOI associated with each file.  Only record a DOI if it relates to the whole resource.
024    7_   10.2765/54811      $2 doi
 
 
040 Cataloging agency
 
For original cataloging in OCLC using the P-N (Provider-Neutral) pratice use:
040        STF $b eng$e rda $e pn $c STF
For original cataloging in Symphony use:
040        CSt$beng$erda$epn$cCSt
 NOTE: there may be occasions when you do not want to use Provider-neutral practice, as when you are cataloging unpublished materials mouted locally, or cataloging an online resource which has a physical counterpart but it is impossible to determine the original publication information of the original.  In these cases, simply remove the $e pn from the 040 and make the record a non-pcc record.
 
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
 
 
042   Authentication code
 
 
Use for BIBCO cataloging
 
042                   pcc
 
 
043   Geographic area code
 
 
Follow MARC instructions for this field.
 
 
100/110/111 Creator main entry
 
For personal or corporate main entry, follow the same procedures as would be followed for the material in physical formats (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).  If 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 resource 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 that 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,) unless works associated with the person are not in Roman script.  If a fuller name is known, add those additional parts in parentheses (RDA 9.5.1, LCPS 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 (LCPS 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 when using a 111 (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 (LCPS 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  a translation (and is the only version n 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 (LCPS 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.
 
Follow Capitalization practices from RDA appendix A (6.2.1.4), don't use found capitalization. This field should end with a period or other mark of punctuation (LCPS 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, do not use a 240 but make 7xx name-title added entries for both  languages.  In the rare instance that there would be a 100/240 combination that would be identical for two different resources, qualify the 240 as indicated above in the section on the 130 field.
 
100   1     Shakespeare, William, $d 1564-1616,$eauthor.
240   10    Hamlet.$lMauritian French Creole
 
Follow Capitalization practices from RDA appendix A (6.2.1.4), don't use found capitalization. This field should not end with a period unless the last element is an abbreviation (LCPS 1.7.1)
 
 
245 Title Proper, subtitle, statement of responsibility
 
This field should end with a period (LCPS 1.7.1)
 
Choose the title which appears on the source of information (RDA 2.3.1.4).  
 If the resource is digital text or music and has a title page, use the title page (RDA 2.2.2.2). If the resource lacks a title page but has the image of a cover or jacket, use that.  If neither of those apply and the resource has a home page or splash screen ... [Not mentioned in RDA except in a note, don't know the precedence, sent question to LC, 10/15/2010]. If neither of those apply, use embedded metadata such as an HTML header (RDA 2.2.2.4).  If the resource is video files, use the procedures for video.  If the resource consists of multiple works, with or without their own titles, try to find a collective title [can this be from a home page?. Note that RDA defines a "single unit" in 1.1.3, 2.13.1.3, the glossary, and other places as"in the case of  an intangible resource, as  a single logical unit (e.g., as a PDF file mounted on the web)." but does not define "logical unit."  Local decision: assume logical unit includes a resource made of multiple files brought together by a home page or table of contents]
 
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.
 
245 10    GRASSES found in the Jasper Ridge Biological Preserve
245 10    SOME RECOLLECTIONS OF THE HISTORY OF DEPARTMENTAL LIBRARIES AT STANFORD UNIVERSITY
 
If there is no title anywhere, devise a title (LCPS 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 (LCPS 2.3.2.11) and should be in brackets [RDA 2.2.4 LCPS 2.2.4]

If there is a subtitle, enter it in $b preceded by a colon.  It should come from the same source as the title proper (RDA 2.3.4.2).
 
245    10          Knowledge=Information in Context :$b on the Importance of Semantic Contextualisation in Europeana
 
Transcribe the first statement of responsibility in full (RDA 2.4.1.4, 2.4.2.3).  Only the first statement is required (2.4) but generally give all that are important. Prefer a statement  from the same source as the title, but if there isn't one, a statement from somewhere else is acceptable.  Bracket only if from outside the resource.  Give all names and associated information unless there are so many as to be burdensome (SUL decision). Generally give information such as titles, affiliation,  etc., but omit full addresses.  Do not use ... when abridging.  If the quantity of names is burdensome, give the first and follow it with [and number others.].  Remember to trace all creators, even if not transcribed in the statement of responsiblity.
 
245    10    PRESERVING VIRTUAL WORLDS / $c Jerome McDonough & Robert Olendorf, Graduate School of Library & Information Science, University of Illinois at Urbana-Champaign, Matthew Kirschenbaum, Kari Kraus, Doug Reside & Rachel Donahue, College of Information Studies, Maryland Institute for Technology in the Humanities,  Andres Phelps & Christoper Egert, Interactive Games & Media Department, B. Thomas Golisano College of Computing & Information Science, Henry Lowood & Susan Rojo, Humanities Research Group, Stanford University Libraries  [full addresses omitted]
or
 245    10    PRESERVING VIRTUAL WORLDS / $c Jerome McDonough [and nine others].
 
Collections with a collective title
 
For an online resource consisting of multiple works issued as a single unit 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.") Do the same even if one work is predominant and the others are subsidiary or minor works.
In these cases, use either formal or informal contents note 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. analytical authorized access point for the predominant or first work in the compilation when it represents a substantial part of the resource (RDA25.1). You may also make title added entries for the individual titles  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 (RDA25.1). 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. (LCPS 25.1.1.3 is not to use enhanced contents.) 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).
 
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.
 
 
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 (LCPS 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). Variants for a title of a component work when the resource contains more than one work would be recorded in 740 (LCPS 2.3.6.3).
 
If the title on an HTML document home page or a list from a provider differs from the title on the item itself (or, for an HTML document, if the title differs from the print version or other known versions), create an 046 field with the text: 
 
246 1_ $i Available from some providers with title: $a <title >
 
The rational here is that if there are other online versions, they may refer to the document by using a variant title that might not appear on the versions by other providers.  This particular situation is generally present on IEEE conference proceedings, where the website uses a conventionalized title with the subject words rotated to the front, which may be considerably different from the title on the PDF title page, and will generally not appear in the cases when the conference proceedings appear in print or on another site (such as ACM). (PCC P-N policy)
 
There is often introductory information before the title in the form "Welcome to ...." Ignore this information when formulating the title and statement of responsibility, but you may give the information in a title added entry in the 246 field, if it is important for identification and access (RDA 2.3.1.6 optional addition, LCPS 2.3.6.3 indicates that such additions should be made with the proviso "but generally do not make a variant title that is not sufficiently distinctive to be a useful access point"). The below example is included for illustrative purposes, but generally do not make unless it seems useful.
 
245   04    The delights of chemistry
246   1     $iTitle appears on resource as:$a Welcome to the delights of chemistry
 
This field does not end with a period unless the last element is an abbreviation (LCPS 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, or an outside source such as a reference source or information from elsewhere on the publisher's site (RDA 2.2.4). If it comes from outside the resource, put it in brackets (RDA 2.2.4 LCPS 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.  However, don't use an edition statement that only refers to a particular provider and doesn't apply to all online versions (or potential online versions) of the resource nor to the print version from which an online resource was digitized (PCC P-N policy).  Record a date that appears with an edition statement as part of the edition statement (RDA 2.5.2.3)
 
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 Revised and Enlarged.
250        2nd ed.. [appears as 2nd ed. on the piece]
250        Version 5.3.
 
264 Place of Publication, Publisher, Date
 
This field should end with a period or other mark of punctuation (LCPS 1.7.1) unless there is no date.
Online resources present challenges in this area. The source of information would preferably be from the same source as the title (RDA 2.2.4), however, very often the publisher, or particularly the place of publication, is not within the resource itself because the item may be a digital reproduction.  Under RDA, the publication information should be for the online version, not the paper original.  However, according to the PCC P-N policy, one should use the publication information that's common to all versions of the online resource.  Practically speaking, if it is a digitization of a printed text, use the publication information of the printed text.  If it exists only as a PDF, use the publication information within the PDF file, appearing in the conventional places that one would look for its physical counterpart (i.e. same source as the title, PDF t.p. verso, PDF last page or back cover image, etc.). 
Sometimes neither of the above is applicable.  In this case you may have to resort to finding the publisher of the individual web instance.  Sometimes the publisher may be found by lopping off the end of the URL and finding the home page associated with the site.  From there, the "contact us" or other similar link will often give the physical location of the organization.  However, some websites are not associated with any organization or company with a physical location.
 
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).  Use a 264 field with second indicator 1.   However, if basing the description on the print resource, take the information as it appears in the OCLC record for the print version. [however, if this is formatted according AACR2 and is incompatable with RDA, SUL interim policy is to change to RDA formatting]
 
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 found elsewhere in the website but not in the resource itself, put it in brackets. 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 second 264 field with place of distribution, if stated (RDA 2.9). This 264 would have a second indicator 2.
 
Here are some random examples:
 
264   1    [Seoul, Korea?] :$b [NKDB Center],$c 2009.
264 1    [Stanford, California] :$b [Daniel Jacobson],$c[2010]
264 1    [Place of publication not identified] : $b [publisher not identified], $c [2012]
264   2    [United States] :$b H.W. Wilson, $c [2012]
264 1    [Piscataway, New Jersey] :$b IEEE,$c[2010]
264 1    [Boston, Massachusetts?] :$b World Society for the Protection of Animals,$c[2010]
264   1    [Paris] :$b [Direction de l'information legale et administrative], $c [2012]
264 1    Cambridge, Mass. :$b Harvard University Press ;$c 2010.
264 1    [Place of publication not identified] :$b [publisher not identified],$c [Between 1997 and 2011] 

 
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 is no publisher stated on the item, try to infer a publisher. If you find the name of the publisher elsewhere on the site but not in the resource itself, 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 a second indicator 2e (RDA 2.9). If there is no distributor, transcribe the manufacturer another 264 field with second indicator 3 (RDA 2.10).  If there is no information of any sort available, only include the statements about the lack of place of publication and publisher (LC document "Publication, distribution and/or manufacture statement) (Is this document still current?)
 
Per the PCC P-N policy, all web resources should be considered published per RDA 2.8.1.1.  However, RDA says nothing about this issue and the CC:DA did not wish to make that assumption.  So, generally consider web resources to be published, except for locally-made reproductions that is not available elsewhere on the web.   This includes EEMS materials digitized locally from unpublished materials (as opposed to published materials, which would have the 264 of the original publication).  Do not catalog such materials as pcc. [Locally we need to decide if dissertations should be considered unpublished]
 
If the online resource is to be considered unpublished, simply supply the date of production (RDA 2.7.6.3), and do not bracket it if it is a known date. Only bracket if the date is approximate(message from D. Reser, Oct. 16, 2010), or if you use the copyright date to infer a publication date(LCPS 2.8.6.6). [Per RDA  the place of production and the producer are optional if known. (RDA 2.7, only date is core), so SUL policy is to supply only the date].
 
 
264  0 $c[between 2000 and 2010?]
264  0   $c 2011.
 
Date of Publication
 
Record the date of publication as stated on the item (RDA 2.8.6.3).  If the item is a digital reproduction of a paper original, use the date of the print original (PCC P-N policy). 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, LCPS 2.8.6.6)  
 
264    1    [Seoul, Korea?] :$b [NKDB Center],$c 2009.
264    1    [Stanford, California] :$b [Daniel Jacobson],$c[2010]
264    1    [Place of publication not identified] : $b [publisher not identified], , $c [2012]
264    2    [United States] :$b H.W. Wilson, $c [2012]
264    1    [Piscataway, New Jersey] :$b IEEE,$c2010
264    1   Cambridge, Mass. :$b Harvard University Press ;$c 2010.
264    1   [Place of publication not identified] :$b [publisher not identified],$c [Between 1997 and 2011]
 
Though LCPS 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    [Stanford, California] :$b [Daniel Jacobson],$c[2010]
264    4    $c©2010
 
Per the PCC P-N policy and RDA 2.8.1.1, all web resources should be considered published.  So, generally consider web resources to be published, except for locally-made reproductions that is not available elsewhere on the web.  This includes EEMS materials digitized locally from unpublished materials (as opposed to published materials, which would have the 264 of the original publication).  Do not catalog such materials as pcc.  [Locally we need to decide if dissertations should be considered unpublished]
 
If the online resource is to be considered unpublished, simply supply the date of production (RDA 2.7.6.3), and do not bracket it if it is a known date. Only bracket if the date is approximate.(message from D. Reser, Oct. 16, 2010). [Per RDA  the place of production and the producer are optional if known. (RDA 2.7, only date is core), so SUL policy is to supply only the date].  This is input in a 264 field with second indicator 0.

 
264  0 $c2010.
264  0 $c[between 2000 and 2010?]
 
 
300 Physical Description
 
Give "online resource "as the carrier type of all online resources (RDA 3.1.5).  If it is complete, also record the extent if redily ascertainable ((RDA 3.1.5). 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.  Count or estimate unnumbered pages (For PDFs the total number of pages can be seen within the program window), and describe them as such (RDA 3.4.5.3, 3.4.5.8).  If the number of pages in the conventional sequence is misleading compared to the total number of PDF pages, give the number, followed by "that is" and the corrected number (RDA 3.4.5.5)
 
300   1 online resource
300   1 online resource (1500 remote-sensing images)
300   1 online resource(xv, 300 pages, 150 maps)
300   1 online resource (41 unnumbered pages) 
300   1 online resource (155 pages in various pagings, 2.8 MB)
300   1 online resource (29, that is, 45 pages) 
 
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.  However, per the PCC P-N policy, one should omit this information unless it is applicable to all possible versions of the resource, so generally don't include (PCC P-N policy), unless you are cataloging music (Best practices for cataloging music using RDA and MARC21).  If there are many files or files of different types, do not include this information ; put it in a 516 note if considered important.
 
300   1 online resource(8 audio files)
300   1 online resource (3 data files)
300   1 online resource (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 online resource (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)
 
In $b, state whether there are illustrations (if the content is primarily textual, RDA 7.15), and give color if present (7.17.3). Add "sound" if present, (RDA 7.18). Give the encoding format if readily discernable (RDA 3.19.3). If encoding format is too complicated to be explained in the 300 and is considered important, explain it in a second 538 field (RDA 3.19.3.4, RDA Appendix D.2).  If the resource is primarily audio, begin the field with "digital" (RDA 3.16.1.3, 3.16.2.3).  Note that the LC document "Replacement of GMD and carrier description has an example placing "text file" in $b preceding PDF, but that does not agree with the RDA mapping in Appendix D.
 
300        1 online resource (ix, 120 pages ) :$billustrations (chiefly color)
300        1 online resource (15 video files) :$bcolor, sound, MPEG4
300        1 online resource (140 audio files ) :$bdigital, mp3, sound [???--shouldn't this be structured as a resource that is primarily sound? Doesn't seem to be covered in Music Best Practices]
300        1 online resource :$bcolor illustrations
 
Field 300 either ends in no punctuation or ends in a right parenthesis when the last element of the field is a parenthetical qualifier, unless there is a 490 field.  If there is a 490 field, add a period (LCPS 1.7.1)
 
336   Content type
 
Record the content type from the list in RDA 6.9.1.3. Record as many as are applicable.Alternatively, record only for the predominant part of the work or most substantial parts if applicable. 
 
336        $a text $2 rda content
(for an online text document such as an e-book)
 
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 site containing substantial textual and video content)
 
336        $a computer dataset $2 rdacontent
 
336        $a computer program $2 rdacontent
 
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, LCPS 3.2). Use "computer."
 
337        $a computer $2 rdamedia
 
338 Carrier type
 
This field indicates the storage medium and housing of the resource (RDA 3.3).  Use "online resource."
 
338        $a online resource $2 rdacarrier
 
347   Digital file characteristics

The $a of this field, file type, is core only for cartographic files.  If it were included for text, it would be "text file" in singular.  Since it is not core, don't generally include as it's similar to information in the other 3xx fields.  $b would be for file encoding such as HTML or PDF, but that was omitted from the P-N standard as not applicable to all iterations, as was file size ($c). (PCC P-N policy)

 
380 Form of work [are we using this? Or is it supposed to be part of heading?]
 
(RDA 6.3) Record the form of the work. Form is a class or genre to which a work belongs.
 
380         Computer game.
380         Play
380         Poem.
 

 

4xx Series (490, 830)
 
Transcribe the series statment 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 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 title proper 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)  Per the PCC P-N policy,transcribe  the form of the series only if it applies to all known iterations of the online resource. Do not use for package/provider series. When the e-version is being used as the basis of the description and only one ISSN appears in the resource being described, record that ISSN in the 490 field. If both a print ISSN (p ISSN) and an electronic ISSN (e ISSN) appear in the resource being described, transcribe the e ISSN. When the physical format version record is being used as the basis of the description, use whatever ISSN appears on that record
 
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 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
 
Per the PCC P-N policy, Use the authorized form of the heading for the physical format when providing an added entry for a series that exists in physical format as well as online. For series that exist only online, use the authorized form of the online series. Do not use for package/provider series (records for DLF Registry of Digital Masters, HathiTrust Digital Library and other digital preservation projects excepted)
 
Use the print ISSN rather than the online ISSN for series that exist in print as well as online. Per Stanford policy, put the ISSN in th 490 fiend and not in the 830.
 
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 home page" or "at head of title" or something of the like.
For historical purposes, below, with the text crossed out, is the old RDA LCPS policy
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 or CD-ROM version and you are cataloging the online version, you have several possible scenarios:

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 (LCPS 6.27.1.9)

776   08     $i Electronic 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    0     Example (Qualifier from NAR)

If the series is has some issues published in print or CD-ROM and some online, consider it the same series and use the form in the NAR (LCPS 6.27, Series section Different carrier/media types).

If the series changes from one computer carrier (CD-ROM, DVD-ROM), etc. to online, consider the series to be the same and use the form in the NAR (LCPS 6.27, Series section Different carrier/media types).[what if the qualifier was CD-ROM?  Asking LC]

If all issues of the series are published in a computer carrier (CD-ROM, DVD-ROM), etc. and online, consider the series to be the same and use the form in the NAR (LCPS 6.27, Series  section Different carrier/media types). 

490   1     Example

830 0 Example (Qualifier from NAR)

If the series changes from print. to online, consider the series to be different and either do not trace the series (i.e. use 490 first indicator 0) or create a series authority record for the online series with the qualifier "Online." (LCPS 6.27, section Different carrier/media types). Consider the latter if the authoritized heading for the print already has a qualifier.

If all issues of the series are issued both in print. and online, consider the series to be different and either do not trace the series (i.e. use 490 first indicator 0) or create a series authority record for the online series with the qualifier "Online." (LCPS 6.27, section Different carrier/media types). Consider the latter if the authoritized heading for the print already has a qualifier.

490   1     Example

830   0     Example (Qualifier from print : Online)

In case of doubt, consider the series to be a single series until other information is available (LCPS 6.27, section Different carrier/media types)

 

 

  
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. (LCPS 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, LCPS 3.20.1.3). There is no requirement to begin with the term "System requirements:" transcribe whatever it says on the resource. It does not appear that this needs to be a quoted note (based on example in RDA 3.20.1.3). Generally use this note if software or hardware beyond what is normal and obvious for the type of carrier or type of file (e.g., the make and model of equipment or hardware, the operating system, the amount of memory, or any plug-ins or peripherals required to play, view, or run the resource).  However, RDA also gives an example: "System requirements: Adobe Acrobat Reader" which seems normal and obvious for the type of file.
 
 
502  Dissertation note
 
 If the resource 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 (LCPS 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. (LCPS 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 (SUL decision)
 
 
538 Digital file characteristics
 
If they are considered to be important, record here in a separate 538 field: resolution (RDA 3.19.5), whether it is streaming media (RDA 3.18.2.4), Transmission speed (RDA 3.19.7) in kilobytes per second kbps  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 347 and is considered important, explain it here (RDA 3.19.3.4, RDA Appendix D.2)  This data element is only mentioned in the PCC P-N policy as field 347, which states that the information should generally not be added to the record as it may not be the same for all online iterations.
 
538   2048x1536 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        Interface in English, documents in English, German, French, and Italian.
546        Latin and Greek with English or German interface.
 
 
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 505.0
 
500        Also contains reports from the various subsidiary groups and QuickTime videos of the opening and closing ceremonies.
 
 
588  Description based on (date viewed) note and source of title note.
 
(RDA 2.17.13.5).  This note is used to give the date upon which the resource was viewed for cataloging.  Below are the two formulations specified by the PCC P-N document.  This is combined with the source of title note per the PCC P-N document, which they require whenever the description is based on the online resource (It is not technicallly required per RDA 2.17.2 unless the title of a textual resource does not come from the title page).
 

588         Description based on print version record.

588         Description based on online resource; title from PDF title page ([provider name], viewed [date])


 
 
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, LCPS 25.1.1.3). Do not use an enhanced contents note (LCPS 25.1.1.3). Record the titles proper that appear in the source that provides the best identification (LCPS 25.1.1.3).   Also record the first statement of responsibility (LCPS 25.1.1.3). Omit chapter and section numbering. Use a space-dash-space to separate the components. (LCPS 25.1.1.3). 
 
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 -PCC-PS 25.1). 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.   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. If there is no attribution, .. [we will revisit this issue re necessity for summaries in view of LCPS, foreign language summaries, attributions]
 
520         Multimedia website on the history and culture of Poland.
 
 
533   Reproduction note
 
Do not use. This can only be used for Hathi Trust and Google Books records.  However, accept copy with these fields as provider-neutral records.
 
6xx Subjects and Genres
 
Provide Library of Congress subject headings according to LC policy given in the LC Subject Headings Manual. 
 
For resources which are primarily video or games, supply appropriate genre headings as per the instructions for those formats.
 
7xx Added Entries and linking entries
 
Added entries for persons and corporate bodies
These fields end in a period or other mark of punctuation (LCPS 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 as "creators" (includes artists, authors, compilers of a new work (i.e. a bibliography, directory, etc.), photographers, programmers, etc.).   Use  Search names in NAF and use that form, [but for the RDA test follow test guidelines]. 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. PCC 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.
 
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 in the resource).
 
 
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 OCLC or in the Library of Congress online catalog. 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 OCLC or in the Stanford catalog.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 Translation of (work): $aBhagavadgita.
 
Analytical title added entries
Analytical added entries are made for component works within a resource. 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.
 
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 Container of (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, for a resource that includes an e-book, it would be appropriate to trace in this format:
 
700   12    $iContains (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 (LCPS 6.27.3)
700   12    $iContainer of (expression).$aCarver, Raymond.$tShort cuts.
700   12    $iContainer of (espression).$aCarver, Raymond.$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.  Second indicator is 2.
 
776 Linking entry for reproductions
Required if the description is based on the record for another format; otherwise provide if readily available. 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) This applies to resources that are either reproductions or are simultaneously issued in more than one format (PCC P-N  policy).  Take the information from the OCLC record for the print.  If you lack a record for the print or other physical version, still provide a 776 ,providing only subfields $a (if applicable) and $t, as well as the ISBN in $z if available.  If there is no information indicating the existance of a print version, do not include a 776 field.
 
When there is an OCLC record for the print, you may create a 776 field through the use of the "Insert from Cited Record" function in OCLC.  First copy the OCLC number of the print record. Then create a blank field in the OCLC record for the reproduction, with the field tag 776 and indicators 08.  Paste the print record number in the text field of the 776, and click Edit on the top of the OCLC screen and on the drop-down menu, click "Insert from Cited Record.  This will give you the required fields and numbers but does not include $h for the pagination, size, etc.  nor $k for series. You may either or both fields if you fell it would be useful.  If the record not an RDA record, still leave the information in the format of that record instead of converting it to RDA.

Per the PCC P-N policy, use $iPrint version: as the relationship designation, instead of the text in RDA Appendix J. The relationship designation is capitalized and is followed by a colon, and the field ends with a period or other mark of punctuation (LCPS 1.7.1) Input a period following subfield $a, $s and $t. 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 LCPS examples and RDA examples so, and the LCPS examples are not correct) .All initial articles in the entry of the related record are omitted in the linking entry field with the exception of the personal or geographic names that file on the article (Conser Editing Guide, linking fields, general information--referred from LCPS 1.7.1)
 
776 08     $i Print version : $aLee, Luke S. $t 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 3/4 in. $z 97891234567891 $w(OCoLC) 62115146 $w (DLC) 76005217
776   08     $i Print version: $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 $s ISBN  $w(OCoLC) 228784799 $w (DLC)   10032685
 
 
830  See 490, 775/776
 
 
856 URL
 
Add an 856 field containing the URL for the online version. For the 856, use 1st indicator 4 and second indicator 0. In the $u insert the URL copied from the location window of the item.  If the resource is one that is one that we pay for or is otherwise restricted to Stanford users, precede the $u with the $z phrase "Available to Stanford-affiliated users"
 
856   40 $uhttp://www.jstor.org/journals/10510761.html
856   40   $zAvailable to Stanford-affiliated users.$uhttp://www.jstor.org/journals/10510761.html
 
For additional details on local practices for 856 subfields, see the Stanford 856 field guidelines:  https://lib.stanford.edu/?q=metadata-department/guidelines-marc-field-856-data
 
 
Revision history:
 
Updated May 2014.
Per 1914 update: 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).  Corrected  a reference from RDA 2.7.6 to 2.8.1.1 for instructin that all online materials be considered published.
 
November 21, 2013
Added 024 coding for DOI.  Also added local decision regarding "single logical unit" which I first noticed in the November 2013 RDA updates.  No other changes added from that update.
 
July 24, 2013
Code "pn" for provider neutral practice authorized in OCLC 040 and change local note in URL.

July 13, 2013

RDA July 2013 updates:  Image of jacket added to sources per 2.2.2.2,

 

May 30, 2013

RDA May 2013 updates:  spell out months in viewed-date note. 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. 

 
February 21, 2013
Interim workarounds regarding RDA and the PCC P-N policy
 
January 17, 2013
PCC P-N policy
 
Sept. 21, 2012
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).
 
Aug. 23, 2012
LCPS August 2012 update
Eliminated requirement to add language to access point for work in its original language.
 
LCPS June 2012 update
LCPS update #2
2.8.6.6, 2.11.1.3 copyright dates
6.27.1.9  Differentiate all titles of works, including monographs (presumably shoud apply to collective DVD title)
 


« Back