Developing MARCXML Guidelines for the Digital Repository of Ireland
•Download as PPTX, PDF•
0 likes•238 views
Presented at CONUL conference, May 2018, Galway, Ireland
Recommended
Recommended
More Related Content
Similar to Developing MARCXML Guidelines for the Digital Repository of Ireland
Similar to Developing MARCXML Guidelines for the Digital Repository of Ireland (20)
More from CONUL Conference
More from CONUL Conference (20)
Recently uploaded
Recently uploaded (20)
Developing MARCXML Guidelines for the Digital Repository of Ireland
- 1. DRI Presentation Clare Lanigan Education & Outreach Manager, Digital Repository of Ireland Kevin Long Digital Archivist, Digital Repository of Ireland Kathryn Cassidy Software Engineer, Digital Repository of Ireland Developing MARCXML Guidelines for the Digital Repository of Ireland
- 2. DRI Presentation DRI Metadata Guidelines
- 3. DRI Presentation MARCXML and DRI
- 4. DRI Presentation Factors in development of MARCXML Guidelines • choosing the appropriate MARC fields to be selected as mandatory • deciding which DRI UI fields these should be mapped to • creating examples that were correct technically and bibliographically
- 5. DRI Presentation Mandatory MARC fields • Type of Record / Leader/06 • Main or Added Entries / I 100 or 110 or 111 or 700 or 710 or 711 • Title / 245$a • Date / 008/07-14 or 260$c or 264$c • Description / 300 or 500 or 520 • Rights / 506 or 540 or 542$f
- 6. DRI Presentation Mapping Mandatory fields to DRI UI fields
- 7. DRI Presentation Example MARC record of Joyce’s Ulysses Examples of Values
Editor's Notes
- The Digital Repository of Ireland is a trusted national infrastructure for the preservation, curation and dissemination of Ireland’s humanities, social sciences, and cultural heritage data. Ours is a repository system flexible enough to handle the four most commonly-used metadata standards in use within the designated community. In this short talk, we aim to give an overview of the process of selecting metadata standards for guideline publications, and the relevant factors involved in developing the MARCXML guidelines.
- Our metadata guidelines[1] are developed with a view to making multiple, sometimes very different and inconsistent, metadata formats appear consistently and be cross-referenceable in the DRI repository. [1] http://dri.ie/publications#guidelines
- DRI recently published MARC metadata guidelines: MARC21 encoded as MARCXML and the Digital Repository of Ireland.[2] As MARCXML facilitates the sharing of, and networked access to, bibliographic information worldwide, accurate guidelines on its effective use are very important to the operations of modern, innovative libraries. [2] Digital Repository of Ireland, & O'Neill, Jenny. MARC21 encoded as MARCXML and the Digital Repository of Ireland, Digital Repository of Ireland [Distributor], Digital Repository of Ireland [Depositing Institution], https://doi.org/10.7486/DRI.1831s091f
- DRI's ingest process selects a minimum set of required fields and recommended fields. It is necessary to give some indication of which fields are mandatory, recommended, etc. within DRI. It is also important that users have some understanding of how their metadata displays within the DRI front-end.
- Reasons why these had to be the mandatory fields: Type of Record / Leader/06 –Type is a mandatory DRI field when creating records within the UI, and is mandatory in Dublin Core. The leader is a mandatory fixed field within a MARC record and character 06 describes the type of record. We indexed this to display as ‘Type of Record’ in the UI. 336 (Content type), 380 (form of work), and 655 (index term - genre/form of work) are optional bibliographic fields that we have also mapped to ‘Type’ in the UI when they are used. Within the full metadata, all of these fields display in conventional MARC XML form (e.g. the leader is displayed <leader>#####nam#0000#a#4509</leader>, where n signifies language material. Main or Added Entries / 100 or 110 or 111 or 700 or 710 or 711 – these are the fields that correspond to a creator, a mandatory field in DRI. Title / 245$a [245 including subfield a] – corresponds to title, a mandatory field in DRI. Date / 008/07-14 or 260$c or 264$c - corresponds to date, a mandatory field in DRI. Description / 300 or 500 or 520 - corresponds to description, a mandatory field in DRI. Rights / 506 or 540 or 542$f - corresponds to rights, a mandatory field in DRI. The mandatory fields in DRI are Title, Description, Type, Date, Creators and Rights – we index these to the closest equivalent within a metadata record of any standard etc. (DC, EAD, MARCXML, MODS).
- In this example, MARC values are mapped to DRI UI fields [Show link to PDF of the report in the repository so can display the XML]
- Explanatory information about this record – how does it show compliance with the requirements listed? How is it correct bibliographically and technically? Would display in DRI record as ‘Ulysses’. 245 is the equivalent MARC field – ‘title statement’ $a is a subfield code – mandatory if you are using MARC XML in DRI – that indicates that this title statement is specifically the title proper as opposed to other kinds of title statements used in MARC. Other kinds of title statement are recommended but not enforced by DRI. (This record contains an example of one - $c – meaning statement of responsibility, in this case James Joyce).