-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 25.02.2014 12:50, schrieb PHILLIPS M.E.:
> If we are just talking about ISO 2709, the whole family of MARC formats in
> general, then you have to remember that UNIMARC and obsolete formats like
> UKMARC
> have very different requirements. UKMARC a
> You also could consider to grok Jason Thomale's "Interpreting MARC:
> Where's the Bibliographic Data?" < http://journal.code4lib.org/articles/3832 >
That's a very good article, as it highlights the problems of the prescribed
punctuation both getting in the way of extracting parts of the data an
Carsten,
> Thank you both for bringing the discussion forward. I must admit that I'm
> having some problems following here. I read your mails multiple times, really
> trying to understand your demands. After reading this [1], I hope I'm getting
> closer.
You also could consider to grok Jason Tho
det: Mittwoch, 19. Februar 2014 23:06
> An: Klee, Carsten; 'Patrick Hochstenbach'
> Cc: v...@gbv.de; librecat-...@mail.librecat.org; perl4lib@perl.org
> Betreff: Re: [librecat-dev] A common MARC record path language
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Carsten,
> I think the whole problem lies in the limited expressivity of strings.
> MARCspec is pretty much close to XPath at its approach, but without regular
> expressions and functions like first(), last() etc. But even with XPath it
> would
>
7;t...@gymel.com'; Patrick Hochstenbach
Cc: v...@gbv.de; librecat-...@mail.librecat.org; perl4lib@perl.org
Subject: AW: [librecat-dev] A common MARC record path language
Hi Thomas and Patrick!
I think the whole problem lies in the limited expressivity of strings. MARCspec
is pretty much close to XPath at i
Dienste IIE
Staatsbibliothek zu Berlin - Preußischer Kulturbesitz
Fon: +49 30 266-43 44 02
> -Ursprüngliche Nachricht-
> Von: Thomas Berger [mailto:t...@gymel.com]
> Gesendet: Mittwoch, 19. Februar 2014 01:04
> An: Klee, Carsten; 'Patrick Hochstenbach'
> Cc: v...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 18.02.2014 17:47, schrieb Klee, Carsten:
> I understand that there is MARC data combined with cataloging rules. We
> don't use this approach within our MARC. So I'm not really aware of the
> problematics.
"Your" MARC however will be very much i
ick Hochstenbach [mailto:patrick.hochstenb...@ugent.be]
> Gesendet: Dienstag, 21. Januar 2014 09:57
> An: Klee, Carsten; v...@gbv.de; librecat-...@mail.librecat.org;
> perl4lib@perl.org
> Betreff: Re: AW: [librecat-dev] A common MARC record path language
>
> Hi Carsten
>
>
thek zu Berlin – Preußischer Kulturbesitz
>
>Fon: +49 30 266-43 44 02
>
>> -----Ursprüngliche Nachricht-
>> Von: Patrick Hochstenbach [mailto:patrick.hochstenb...@ugent.be]
>> Gesendet: Freitag, 20. Dezember 2013 14:06
>> An: v...@gbv.de; librecat-...@mail.lib
___
Carsten Klee
Abt. Überregionale Bibliographische Dienste IIE
Staatsbibliothek zu Berlin – Preußischer Kulturbesitz
Fon: +49 30 266-43 44 02
> -Ursprüngliche Nachricht-
> Von: Patrick Hochstenbach [mailto:patrick.hochstenb...@ugent.be]
> Gesendet: Freitag, 20. Dezember 2
Hi
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
12 matches
Mail list logo
