100% found this document useful (1 vote)
323 views

Dublin Core-To-RDA Mapping For Examples

DC-RDA draft does not map Subject; however, subject headings and the applicable vocabulary-encoding schemes are included applied. Information concerning condition of the fragment information 3 title 4 creator 19.2.1. For one person 5 subject 6 description as it impacts on the legibility of the text.

Uploaded by

imperatriz
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
323 views

Dublin Core-To-RDA Mapping For Examples

DC-RDA draft does not map Subject; however, subject headings and the applicable vocabulary-encoding schemes are included applied. Information concerning condition of the fragment information 3 title 4 creator 19.2.1. For one person 5 subject 6 description as it impacts on the legibility of the text.

Uploaded by

imperatriz
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

A B Dublin Core 1 Elements/Term RDA Rules 2 2.3.11.

3: devised title

C Notes (2010-11-08) Goodspeed Ms. 862 (qualified dublin core, record 2) Gregory A. Pass, Descriptive cataloging of ancient, medieval, Renaissance, and early modern ...(Chicago: ACRL, 2002): 1B1.6 Cannot encode names with roles; see DC-RDA mapping (Diane Hillmann, et al). Roles will need to be expressed as attributes, like this TEI example: <name reg="Kurdian, Harry, 1902-1976" type="person" role="owner">Harry Kurdian</name>. DC-RDA draft does not map Subject; however, subject headings and the applicable vocabulary-encoding schemes are included applied. concerns condition of the fragment Information

3 title

4 creator

19.2.1.3 for one person

5 subject

6 description

as it impacts on the legibility of the text. Also paleography is noted as providing the source of the date. Script is mentioned in Description, though there is a 7.10.1 summary of question in the draft mapping about whether it fits in that section. content Pass (4A.3). Information concerning source of supplied 2.7.6 date of date recorded in description, see also 4D.2. Note Julian production; 1.9.2.4 and Gregorian calendars use of Year 1 reckoning, e. g. range of dates 15th century, 1401-1500. 6.10.1.3 3.5 dimensions; 3.2 media type; 3.3 Manuscripts are measured in mm. Since Layout is carrier type. mapped to format, ruling type placed in this section. 3.4.1 3.6.1.3 recording base material 2.19.1.4 Neil Ripley Ker, Medieval manuscripts in British libraries (Oxford, Eng, 1969). Types from broad DC type vocabulary and narrower terms from Getty AAT.

7 date 8 type

9 format 10 extent 11 medium 12 identifier bibliographicCi 13 tation

Written space size and the side of the leaf measured are included.

A 14 language

B 7.12 language of the content

15 rights 16 provenance 17 Dublin Core Elements/Term RDA Rules 18 s 19

ISO639-3 language code used. Persistent url furnished by the Digital Library Development Center (DLDC), University of Chicago 4.1 Library. Can be used in a qualified DC record. Not included in DC-RDA mapping. Could add this information in Description.

Notes Jefferson Letter (qualified dublin core, record 1)

20 21 spatial bibliographicCi 22 tation 23 24 coverage

A number of the same rda rules used with Ms. 862 are applicable to this letter. 7.3 Narrow term Spatial refines Coverage. Chicago Manual of Style. Jefferson Letter (simple dublin core, record 1) Two Spatial terms replaced by one Coverage element.

25 date

26 description

Created term replaced by Date element. Extent, Medium, isPartOf terms, and the BibliographicDescription element, the content of the four was moved under Description.

27 Dublin Core Elements/Term RDA Rules 28 s

Notes

A 29

C Goodspeed Ms. 931 (qualified dublin core, record 3)

30 title 31 creator 32 publisher 33 identifier 34 created 35 language 36 description 37 format 38 extent bibliographicCi 39 tation

2.2.4 other sources of information (title) 19.2.1.1.1 (aiii) 21.3.1.1 2.19.1.3; 4.6 2.8.6 7.12 language of the content. 7.10.1; 7.15.1.3 3.2; 3.3.1.3 media type and carrier type 3.4.1.7.5 subunits For the online resource ISO639-3 language code used Local persistent identifier, and url

You might also like