JATS-to-MARC mapping
From jats
(forgot to put second table under a different heading) |
(disclaimer about main and added entries) |
||
| (One intermediate revision not shown.) | |||
| Line 1: | Line 1: | ||
If you have articles in JATS format, you may want to generate MARC analytic records containing the metadata for each article. | If you have articles in JATS format, you may want to generate MARC analytic records containing the metadata for each article. | ||
| - | The initial version of the mapping below was created based on information from Steven Holloway at the American Theological Library Association and modified by Kevin Hawkins in consultation with him and colleagues at the University of Michigan Library. It will be incorporated into [http://www.lib.umich.edu/mpach mPach]. | + | The initial version of the mapping ("crosswalk") below was created based on information from Steven Holloway at the American Theological Library Association and modified by Kevin Hawkins in consultation with him and colleagues at the University of Michigan Library. It will be incorporated into [http://www.lib.umich.edu/mpach mPach]. |
| - | Note that the resulting data will not strictly conform to RDA or to AACR2, but it should reasonably be able to interoperate with catalog records created according to RDA or AACR2 stored in MARC. | + | Note that the resulting data will not strictly conform to RDA or to AACR2, but it should reasonably be able to interoperate with catalog records created according to RDA or AACR2 stored in MARC. Note that it does not assign a ''main entry'' for the article but simply makes all authors ''added entries''. |
== MARC analytic record fields that will be the same (or are figured the same way) for all articles == | == MARC analytic record fields that will be the same (or are figured the same way) for all articles == | ||
Current revision
If you have articles in JATS format, you may want to generate MARC analytic records containing the metadata for each article.
The initial version of the mapping ("crosswalk") below was created based on information from Steven Holloway at the American Theological Library Association and modified by Kevin Hawkins in consultation with him and colleagues at the University of Michigan Library. It will be incorporated into mPach.
Note that the resulting data will not strictly conform to RDA or to AACR2, but it should reasonably be able to interoperate with catalog records created according to RDA or AACR2 stored in MARC. Note that it does not assign a main entry for the article but simply makes all authors added entries.
[edit] MARC analytic record fields that will be the same (or are figured the same way) for all articles
| MARC field | Value |
|---|---|
| Leader/00-04 | generated at time of creation |
| Leader/05 | n |
| Leader/06 | a |
| Leader/07 | b |
| Leader/09 | (depends on how you create MARC) |
| Leader/10 | 2 |
| Leader/11 | 2 |
| Leader/12-16 | generated at time of creation |
| Leader/17 | 3 |
| Leader/18 | u |
| Leader/19 | r |
| Leader/20 | 4 |
| Leader/21 | 5 |
| Leader/022 | 0 |
| Leader/23 | 0 |
| 001 | nine-digit ID beginning with “2”. What follows should be unique for each article ever submitted through mPach. A resubmission would get the same ID as the previous version. |
| 005 | timestamp for last update |
| 008/00-05 | timestamp for initial creation |
| 008/15-17 | (depends on where the content was published) |
| 008/23 | s |
| 008/29 | <== This is a pipe character. |
| 008/30 | <== This is a pipe character. |
| 008/31 | <== This is a pipe character. |
| 008/32 | <== This is a pipe character. |
| 008/33 | <== This is a pipe character. |
| 008/39 | d |
[edit] JATS elements to MARC fields
| XPath to JATS element and notes | MARC field(s) and notes |
|---|---|
| article-meta/title-group/article-title (mandatory) | 245 $a
Add a second indicator to indicate filing if you are able to determine. |
| article-meta/title-group/subtitle (optional) | 245 $b
Since the field can repeat in JATS, add subsequent subtitles after the first one, each separated by “space, em dash, space”. |
| article-meta/title-group/trans-title-group/trans-title (required only if there is a container <trans-title-group>) | 245 $a (after “ = ”) |
| article-meta/title-group/trans-title-group/trans-subtitle (optional) | 245 $b (after “ = ”)
Since the field can repeat in JATS, add subsequent subtitles after the first one, each separated by “space, em dash, space”. |
| contrib/name/surname (optional) | If there is a <surname>, put a “1” for first indicator on 700, and put <surname> in 700 $a.
If there is no <surname>, put a “0” for first indicator on 700. |
| contrib/name/given-names (mandatory) | 700 $a (If the value of <surname> was inserted, then, after the value of <surname>, insert “, “ and then <given-names>.) |
| contrib/name/prefix (optional) | 700 $c (can repeat, so use a separate one from <suffix>) |
| contrib/name/suffix (optional) | 700 $c (can repeat, so use a separate one from <prefix>) |
| journal-meta/publisher (optional) | 260 $b |
| journal-meta/journal-title-group/journal-title (optional) | 740 $a
one component of 773 $a |
| journal-meta/journal-title-group/journal-subtitle (optional) | 740 $a (after “: ”) |
| journal-meta/journal-title-group/trans-title-group/trans-title (mandatory only when there is a container <trans-title-group>) | 740 $a (after “ = “ after the value of journal-subtitle, if applicable) |
| journal-title-group/trans-title-group/trans-subtitle (optional) | 740 $a (after “: ” following the value of journal-title-group/trans-title-group/trans-title already inserted) |
| journal-title-group/trans-title-group/trans-subtitle (optional) | 740 $a (after “: ” following the value of journal-title-group/trans-title-group/trans-title already inserted) |
| article-meta/issue-title (optional) | 500 $a |
| article-meta/volume (optional) | one component of 773 $a |
| article-meta/issue (optional) | one component of 773 $a |
| article-meta/pub-date (optional) | For its children, insert in parentheses in this order:
<date> <month> <year> as one component of 773 $a |
| article-meta/pub-date/year (optional) | Insert value of first <year> as a four-digit number in 008/07-10.
Insert value of second <year> (if present) as a four-digit number in 008/11-14. Also insert all values of <year>s into 260 $c, separated by commas. Also insert “s” in 008/06 if one <year> element and “m” if there are multiple <year> elements. |
| article-meta/fpage | one component of 773 $a |
| article-meta/lpage | one component of 773 $a |
| article-meta/page-range | one component of 773 $a |
| article-meta/isbn (optional)
While a JATS article may but need not have an ISSN or ISBN at various points in its metadata, only <isbn> within <article-meta> would give an identifier for the article itself. | 020 |
| article-meta/abstract (optional) | 520 $a |
| article-meta/trans-abstract (optional) | 520 $a (after “ = ” after the value of abstract, if applicable) |
| article-meta/product/name (optional)
article-meta/product/string-name (optional) article-meta/product/article-title (optional) article-meta/product/source (optional) article-meta/product/series (optional) article-meta/product/publisher-place (optional) article-meta/product/publisher-name (optional) article-meta/product/year (optional) article-meta/product/page-range (optional) article-meta/product/isbn (optional) These elements contain bibliographic data about book(s) reviewed in a book review, but practice varies from publisher to publisher. | concatenate fields in the order shown at left (and any descendants, in the serialized order from the XML) in 500 $a, with each separated by “. ” |
| body@xml:lang (if present); otherwise, article@xml:lang (optional)
If no value is found in either location in the JATS, assume English (per JATS spec). This is the primary language of the article. A user can’t always tell from the title, especially in closely related languages. | 008/35-37
Will need to map from BCP 47 codes (used in JATS) to MARC codes. |
| Various elements inside of article-meta/counts/page-count (optional)
This gives the pagination of the article. While mPach supports born-digital publication, some publishers may in fact typeset the articles and number pages continuously through the volume (or issue), so we might need to record this information in the analytic record. | 300 $a |
