1. About this document

Author

Corey Wallis, RUBRIC Technical Officer

Purpose

This technical report outlines the way in which the EndNote to Fedora data migration scripts map fields in the EndNote data to fields in the MARCXML data.

Audience

RUBRIC Project Partners and other users of EndNote and Fedora

Requirements

An understanding of the structure of EndNote data represented as XML

An understanding of the structure of MARC tags and how they're represented in MARCXML

References

RUBRIC Technical Report: Migrating EndNote data to Fedora

Official EndNote website
http://www.endnote.com/

Official ARROW Project website
http://www.arrow.edu.au/

Official MARCXML website at the Library of Congress
http://www.loc.gov/standards/marcxml/

Notes

2. Background Information

In preparation for the EndNote to Fedora data migration it was necessary to map the available data in the EndNote XML file to the fields specified by the MARCXML templates provided by the ARROW project.

The map outlined below was developed using sample data provided by the University of Newcastle. The map was then used to develop the XSL transformation used by the Python script as part of the EndNote to Fedora data migration.

It should also be noted that the map created for patent items is not based on an ARROW template. At the time the data migration was written the ARROW project had not yet decided on common rules for storing metadata about patents. When an official template is produced this map may need adjustment.

3. EndNote to MARCXML data map

3.1. Data map definitions

The EndNote data to MARCXML data map contains the following columns:

MARC field

The MARC field as specified by the ARROW template

MARC Subfield

The MARC subfield as specified by the ARROW template

Description

The description of the field

EndNote XPath

The XPath to the field in the EndNote XML data. Each record is stored as a child of a record node, therefore the XPath as listed here is relative to the following node:

/xml/records/record

3.2. Common data mapping

3.3. Journal Article Specific Mapping

A journal article is defined as an EndNote record having the following ref-type node:

<ref-type name=“Journal Article”>17</ref-type>

3.4. Conference Proceeding Specific Mapping

A conference proceeding is defined as an EndNote record with the following ref-type node:

<ref-type name=“Conference Proceedings”>10</ref-type>

3.5. Patent Specific Mapping

A patent is defined as an EndNote record with the following ref-type node:

<ref-type name=“Patent”>25</ref-type>

3.6. Building the Citation Field for Journal Articles

The ARROW MARCXML templates specify that field 787, subfield g, is used to store a citation. The EndNote data has components of a citation in different fields. The following map outlined the components of the citation, and how they are concatenated to create a complete citation.

The citation is compiled as follows to adhere to the style provided by ARROW.

Vol. [vol], no. [no] ([pub-date-1]. [pub-date-2]), p. [pages]

3.7. Building the Citation Field for Conference Proceedings

The ARROW MARCXML templates specify that field 787, subfield g, is used to store a citation. The EndNote data has components of a citation in different fields. The following map outlined the components of the citation, and how they are concatenated to create a complete citation.

The citation is compiled as follows.

[vol], ([pub-date-2]), p. [pages]

3.8. Static Information

There are a number of fields specified by the MARCXML templates that require data that is not stored in the EndNote XML file. These values are stored in the static-information.xml file and are retrieved during the XSL transformation. These fields are outlined below, instructions for editing the static-information.xml file are included in RUBRIC Technical Report: Migrating EndNote data to Fedora.