Thanks for this initiative to formalise the path language for MARC
records. In Catmandu our path language is better described at:
https://metacpan.org/pod/Catmandu::Fix::marc_map. It would be an easy fix
for us to follow Carsten¹s MARC spec rules and I will gladly implement it
for our community. 

We see these type of MARC paths in programming libraries such as the
projects mentioned below but also in products like XSTL, SolrMarc,
ILS-vendors who need them to define how to index marc, standardisation
bodies like e.g. that provide mapping rules (e.g.
http://www.loc.gov/standards/mods/mods-mapping.html). I tried to make a
small roundup in the past of these projects but it would be great to have
more extensive look at all current pratices.

In our Catmandu project we found that Xpaths are too verbose for our
librarians to interpret and in practise tied to XSLT-programming which
requires quite some programming skills to read and interpret.

Our paths are very much simplified but still seem to lack some things that
are available in the MARC data model which would be great to have
available in the MARCspec syntax:

 - Notion of pointing to the first item (first author)
 - Supporting local defined MARC (sub)fields (e.g. Ex Libris exports
contain all kind of Z30, CAT , etc fields)
 - Support for pointing to a subfields that follow a specific character
(e.g. In titles I would like to point to everything after the Œ/Œ in a 245

Cheers and have a nice holiday


On 19/12/13 13:16, "Jakob Voß" <v...@gbv.de> wrote:

>Carsten Klee specified a simple path language for MARC records, called
>"MARC spec". In short it is a formal syntax to refer to selected parts
>of a MARC record (similar to XPath for XML):
>Similar languages have been invented before but not with a strict
>specification, as far as I know. For instance the perl Catmandu::MARC
>supports references to MARC fields:
>Could you please have a look at MARC spec and join forces to get a
>common syntax that can be used among different tools? So
>- If your tool does not support all aspects of MARC spec, please
>implement the missing parts.
>- If your tool supports more than included in MARC spec, help extending
>the syntax at https://github.com/cKlee/marc-spec/
>- If you tool uses a different syntax to refer to parts of MARC,
>please think about modifying it to align with MARC spec.
>Jakob Voß <jakob.v...@gbv.de>
>Verbundzentrale des GBV (VZG) / Common Library Network
>Platz der Goettinger Sieben 1, 37073 Göttingen, Germany
>+49 (0)551 39-10242, http://www.gbv.de/
>librecat-dev mailing list

Reply via email to