_MARC mapping (new)
Contributor
see http://www.loc.gov/standards/mods/mods-mapping.html#name. The following specific guidelines apply for the DAMS: name[@type="personal"]/namePart 100$b Approximate mapping Not available for manual input through the DAMS metadata form, currently not used for display in the Collections portal. Approximate mapping Not available for manual input through the DAMS metadata form, currently not used for display in the Collections portal. Approximate mapping Not available for manual input through the DAMS metadata form, currently not used for display in the Collections portal. Approximate mapping Not available for manual input through the DAMS metadata form, currently not used for display in the Collections portal. 245$c Approximate mapping Not available for manual input through the DAMS metadata form. MARC subfield may include other information in addition to the display form of the name The displayForm subelement is currently not used for display in the Collections portal. Not available for manual input through the DAMS metadata form, currently not used for display in the Collections portal. Map MARC relator code into MODS roleTerm subelement that is part of a name element with correct type (e.g. personal, family or corporate). Not available for manual input through the DAMS metadata form, currently not used for display in the Collections portal. Map MARC relator code into MODS roleTerm subelement that is part of a name element with correct type (e.g. personal, family or corporate).MARC 21 field Mapping condition MODS element Notes MARC indicator 1 has values 0, 1 700 MARC indicator 1 has values 0, 1 name[@type="personal"]/namePart MARC indicator 1 has value 3 name[@type="family"]/namePart 700 MARC indicator 1 has value 3 name[@type="family"]/namePart name[@type="corporate"]/namePart 710 name[@type="corporate"]/namePart name[@type="conference"]/namePart 711 name[@type="conference"]/namePart name/namePart[@type="termsOfAddress"] 100$c name/namePart[@type="termsOfAddress"] 700$b name/namePart[@type="termsOfAddress"] 700$c name/namePart[@type="termsOfAddress"] name/displayForm name/role/roleTerm[@type="text"] Map MARC relator term into MODS roleTerm subelement that is part of a name element with correct type (e.g. personal, family or corporate). 7XX$e name/role/roleTerm[@type="text"] Map MARC relator term into MODS roleTerm subelement that is part of a name element with correct type (e.g. personal, family or corporate). name/role/roleTerm[@type="code"] 7XX$4 name/role/roleTerm[@type="code"]
Creation, Issuance, Copyright Date
see http://www.loc.gov/standards/mods/mods-mapping.html#publication. The following specific guidelines apply for the DAMS: 264$c 046$m MARC field 534 describes an original version, i.e. likely a different Expression/ Manifestation than what is described by the main bibliographic fields in the same record. Consider using a MARC record describing the same Expression/ Manifestation of a work that is digitized and ingested in the DAMS. Check textual statement in MARC subfield 534$c carefully to determine whether to map to dateCreated or dateIssued. MARC field 775 describes another available edition, i.e. likely a different Expression/ Manifestation than what is described by the main bibliographic fields in the same record. Consider using a MARC record describing the same Expression/ Manifestation of a work that is digitized and ingested in the DAMS. Check textual statement in MARC subfield 775$d carefully to determine whether to map to dateCreated or dateIssued. MARC field 776 describes another available physical form, i.e. likely a different Manifestation than what is described by the main bibliographic fields in the same record. Consider using a MARC record describing the same Manifestation of a work that is digitized and ingested in the DAMS. Check textual statement in MARC subfield 776$d carefully to determine whether to map to dateCreated or dateIssued.MARC 21 field Mapping condition MODS element Notes * *[@encoding] Only use encoding="w3cdtf" or do not use the encoding attribute at all. 260$g dateCreated The MODS field dateOther is not implemented in the DAMS. Map MARC field 260$g to dateCreated instead. 264$c MARC indicator 2 has values 0, 3 dateCreated The MODS field dateOther is not implemented in the DAMS. Map MARC field 264$c to dateCreated instead. MARC indicator 2 has value 2 dateIssued The MODS field dateOther is not implemented in the DAMS. Map MARC field 264$c to dateIssued instead. 033 note[@type="date captured"] The MODS field dateCaptured is not implemented in the DAMS. Map MARC field 033 to a note element with type "date captured" instead. N/A The MODS field dateValid is not implemented in the DAMS. 046$n N/A The MODS field dateValid is not implemented in the DAMS. 046$j N/A The MODS field dateModified is not implemented in the DAMS. 534$c dateCreated/ dateIssued 775$d dateCreated/ dateIssued 776$d dateCreated/ dateIssued
Description
see http://www.loc.gov/standards/mods/mods-mapping.html#abstract. The following specific guidelines apply for the DAMS: Formatted content, e.g. a table of contents. Map MARC 505 field content to abstract, as MODS element tableOfContents is not implemented in the DAMS. The displayLabel attribute always has value "Description". Map MARC 520 field content to abstract, as MODS element tableOfContents is not implemented in the DAMS. The displayLabel attribute always has value "Description". Map MARC 880 field content to abstract, as MODS element tableOfContents is not implemented in the DAMS. The displayLabel attribute always has value "Description".MARC 21 field Mapping condition MODS element Notes 505 abstract 520 abstract 880 abstract
Digital Collection
See http://www.loc.gov/standards/mods/mods-mapping.html#relateditem. The following specific guidelines apply for the DAMS:MARC 21 field Mapping condition MODS element Notes 590 relatedItem[@type="host" and @displayLabel="Digital Collection"]/* Check local note in MARC field 590 for information about Digital Collection.
Extent
see http://www.loc.gov/standards/mods/mods-mapping.html#physicaldescription. The following specific guidelines apply for the DAMS:
File Format
see https://www.loc.gov/standards/mods/mods-mapping.html#physicaldescription. The following specific guidelines apply for the DAMS: Approximate mapping. The information given in MARC field 347 typically does not align with the list of expected file format values. The information can be used, however, to determine a resource's file type. Approximate mapping. The information given in MARC subfield 352$q typically does not align with the list of expected file format values. The information can be used, however, to determine a resource's file type. Approximate mapping. Check if the value given in MARC subfield 856$q aligns with the list of expected file format values for the DAMS.MARC 21 field Mapping condition MODS element Notes 347 internetMediaType 352$q internetMediaType 856$q internetMediaType
Form or Medium
see http://www.loc.gov/standards/mods/mods-mapping.html#physicaldescription. The following specific guidelines apply for the DAMS:MARC 21 field Mapping condition MODS element Notes * form* The values suggested by the LoC's standard mapping for MODS form[@authority] attributes (marcform, marccategory, marcsmd) are currently not supported for manual ingest into the DAMS. Choose one of the suggested vocabularies for authority-controlled terms. 655 form Look for form terms in MARC field 655. This MARC field can also contain genre information, which should be mapped to DAMS MODS field <genre>.
Genre
see http://www.loc.gov/standards/mods/mods-mapping.html#genre. The following specific guidelines apply for the DAMS:MARC 21 field Mapping condition MODS element Notes * genre* The values suggested by the LoC's standard mapping for MODS genre[@authority] attributes (marcgt and marcmuscomp) are currently not supported for manual ingest into the DAMS. Choose from one of the suggested vocabularies for authority-controlled genre terms. 655 genre Look for genre terms in MARC field 655. This MARC field can also contain form information, which should be mapped to DAMS MODS field <physicalDescription><form>.
Identifier
see http://www.loc.gov/standards/mods/mods-mapping.html#identifier. The following specific guidelines apply for the DAMS: Currently, only the following identifier types are supported by the DAMS MODS: URIs recorded in MARC field 856 might be or might become outdated as content is migrated into the DAMS. Check if the URI recorded in field 856 is going to remain resolvable.MARC 21 field Mapping condition MODS element Notes * identifier[@type] 001 OCLC control/accession number of the bibliographic record refers to the analog/physical original. identifier[@type="oclcSource"] 001 OCLC control/accession number of the bibliographic record refers to a derivative/surrogate representation. identifier[@type="oclcSurrogate"] 856$u identifier[@type="uri"]
Language
see http://www.loc.gov/standards/mods/mods-mapping.html#language. The following specific guidelines apply for the DAMS: <languageTerm type="code" authority="iso639-2b" authorityURI="http://id.loc.gov/vocabulary/iso639-2">MARC 21 field Mapping condition MODS element Notes 041$a MARC subfield 041$2 is empty Do not use values other than "iso639-2b" for authority. 041$b N/A Do not use the objectPart attribute. 041$d N/A Do not use the objectPart attribute. 041$e N/A Do not use the objectPart attribute. 041$f N/A Do not use the objectPart attribute. 041$g N/A Do not use the objectPart attribute. 041$h N/A Do not use the objectPart attribute. 041$j N/A Do not use the objectPart attribute. 546$b N/A Do not use the subelement scriptTerm.
Note
Map notes from MARC 21 fields 5XX to <note> elements with an appropriate type from the set of types available in the DAMS (citation, condition, date captured, date issued, date other, description, file path, general, merged, origin, scale, utlGeoDataID). Cf. the following examples:MARC 21 field Mapping condition MODS element Notes 033 MARC indicator 2 has value 0 note[@type="date captured"] Approximate mapping. 500 note[@type="general"] Approximate mapping. Depending on the type of material described by the catalog record, other note types might be appropriate (e.g. when dealing with material cataloged according to DCRM, copy-specific descriptive information might be recorded in MARC field 500). 507 note[@type="scale"] 524 note[@type="citation"] Approximate mapping. 541 note[@type="origin"] Map together with information from MARC field 561, if available. 561 note[@type="origin"] Map together with information from MARC field 541, if available.
Place of Publication or Origin
see http://www.loc.gov/standards/mods/mods-mapping.html#publication. The following specific guidelines apply for the DAMS:MARC 21 field Mapping condition MODS element Notes 008/15-17 N/A Do not use coded data in DAMS MODS. 004$c N/A Do not use coded data in DAMS MODS. 260$a placeTerm[@type="text"]
Publisher
Map from MARC field 260$b - see http://www.loc.gov/standards/mods/mods-mapping.html#publication.
Related Resource
See http://www.loc.gov/standards/mods/mods-mapping.html#relateditem. The following specific guidelines apply for the DAMS: Approximate mapping Approximate mapping Check if MARC field 830 contains information about name/title authority. If a uniform title is used in the MARC record, set the appropriate title type attribute in your MODS data.MARC 21 field Mapping condition MODS element Notes 490 relatedItem[@type="series"]/titleInfo/title 830 relatedItem[@type="series"]/titleInfo/title 772 relatedItem[@type="host" and @displayLabel="Parent work"]/* Check if MARC field 772 contains information about name/title authority. If a uniform title is used in the MARC record, set the appropriate title type attribute in your MODS data. 773 relatedItem[@type="host" and @displayLabel="Parent work"]/* Check if MARC field 773 contains information about name/title authority. If a uniform title is used in the MARC record, set the appropriate title type attribute in your MODS data. 590 relatedItem[@type="host" and @displayLabel="Parent work"]/* Check local note in MARC field 590 for information about Related Resources. 79x relatedItem[@type="host" and @displayLabel="Parent work"]/* Check local added entries in MARC fields 790-799 for information about Related Resources.
Repository
Currently, only limited values from a list of controlled names are permitted.
Rights
See http://www.loc.gov/standards/mods/mods-mapping.html#accesscondition. If no notes on access restriction or reproduction rights are present in the MARC record, you need to make a determination about the copyright status while creating MODS metadata.
Source Collection
See http://www.loc.gov/standards/mods/mods-mapping.html#relateditem. The following specific guidelines apply for the DAMS:MARC 21 field Mapping condition MODS element Notes 590 relatedItem[@type="host" and @displayLabel="Source collection"]/* Check local note in MARC field 590 for information about Source Collection. 79x relatedItem[@type="host" and @displayLabel="Source collection"]/* Check local added entries in MARC fields 790-799 for information about Source Collection.
Subject: Cartographics
Page lookup error: page " Cartographics" not found.
If you're experiencing issues please see our Troubleshooting Guide.
Subject: Geographic Code
Page lookup error: page " Geographic Code" not found.
If you're experiencing issues please see our Troubleshooting Guide.
Subject: Geographic Term
Page lookup error: page " Geographic Term" not found.
If you're experiencing issues please see our Troubleshooting Guide.
Subject: Hierarchical Geographic Terms
Page lookup error: page " Hierarchical Geographic Terms" not found.
If you're experiencing issues please see our Troubleshooting Guide.
Subject: Temporal Coverage
Page lookup error: page " Temporal Coverage" not found.
If you're experiencing issues please see our Troubleshooting Guide.
Subject: Topic
Page lookup error: page " Topic" not found.
If you're experiencing issues please see our Troubleshooting Guide.
Title
see http://www.loc.gov/standards/mods/mods-mapping.html#title. The following specific guidelines apply for the DAMS: MODS element has no type attribute Approximate mapping. MARC 21 field 245 contains the title statement, which may include subtitles, alternative and parallel titles. The title proper is in subfield a, other parts of the title including the subtitle and alternative/parallel titles are in subfield b. Approximate mapping. Approximate mapping. Second indicator of MARC 21 field 246 has value 1 for Parallel Titles, i. e. titles in other languages. Approximate mapping. Second indicator has no value for Alternative Titles. See also title statement in MARC 21 field 245. 245$b MODS element has no type attribute Approximate mapping. MARC 21 field 245 contains the title statement, which may include subtitles, alternative and parallel titles. Subfield b may contain parallel titles. 242$bMARC 21 field Mapping condition MODS element Notes titleInfo/title titleInfo[@type="translated"]/title 246 MARC indicator 2 has value 1 titleInfo[@type="translated"]/title MARC indicator 2 has no value titleInfo[@type="alternative"]/title 740 MARC indicator 2 has value other than 2 titleInfo[@type="alternative"]/title Approximate mapping. titleInfo[@type="uniform"]/title Approximate mapping. 240 titleInfo[@type="uniform"]/title Approximate mapping. MARC indicator 2 has value other than 2 titleInfo[@type="uniform"]/title Approximate mapping. titleInfo/subTitle titleInfo[@type="translated"]/subTitle Approximate mapping. 246$b MARC indicator 2 has value 1 titleInfo[@type="translated"]/subTitle Approximate mapping. 246$b MARC indicator 2 has no value titleInfo[@type="alternative"]/subTitle Approximate mapping. 247 N/A MARC 21 field 247 contains former title(s) for serials. Currently there is no mapping target available for former titles in the DAMS MODS schema.
Type of Resource
Check LEADER pos. 06 - see http://www.loc.gov/standards/mods/mods-mapping.html#typeofresource.
Welcome to the University Wiki Service! Please use your IID (yourEID@eid.utexas.edu) when prompted for your email address during login or click here to enter your EID. If you are experiencing any issues loading content on pages, please try these steps to clear your browser cache.