Indeed, the contributors to this document have produced a detailed
mapping, which has been largely implemented in the MARC-to-TEI (but not
TEI-to-MARC) direction in http://wiki.tei-c.org/index.php/Thutmose .
However, Mark's idea of appropriating the global @n attribute to store a
MARC field is an intriguing one. It certainly makes it easy to map from
TEI to MARC, though it assumes that there is always a one-to-one mapping
of elements to MARC fields, and that the @n attribute isn't needed for
another purpose in the header. Even without re-familiarizing myself
with the mapping, I can imagine both of these situations occurring.
On 2:59 PM, Stuart A. Yeates wrote:
> I suggest that you read
> http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html which
> covers the relationship between TEI and MARC in considerable detail.
> On Fri, Apr 19, 2013 at 7:35 AM, Mark Sgambettera <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
> Hi All,
> I admit to doing very little research on this subject via the
> listserv archive or online. That noted, is it possible and advisable
> to hang MARC21 field values on an n attribute for a given element in
> the teiHeader for the purpose of harvesting attribute values and
> element text nodes to create a draft bibliographic record.
> I appreciate any feedback.
> Mark Sgambettera