Hello Alexander, > Good morning!
[I think that your intention was to respond to the whole list, so let me continue the disussion here.] > I agree with Ferran that 024 should be taken into account. From a > marcish perspective it seems better suited than 035. You may want to I was suggesting 024 instead of a 909, not 035. 035 is intended for external identifiers, so an external OAI id, a handle, a LCCN, a local library catalog number, whatever other identifier should definitively go to 035. http://www.loc.gov/marc/bibliographic/bd035.html The question is where we do store our own OAI id when generated by the oaiarchive daemon, and we think that 024 is correct. > note the marc mechanism using 024 7_ $2<src>. If I get your reqs > correctly, this is ecactly what is required, as you can store > provenance together with the Id in question. (Cf. stotage of doi > according to LoC.) The use of a $2<src> seems to be allowed only if your <src> belong to an approved list maintained by the Library of Congress. Or at least this is what we understood following the links from http://www.loc.gov/marc/bibliographic/bd024.html http://www.loc.gov/standards/sourcelist/standard-identifier.html http://www.loc.gov/standards/sourcelist/index.html so we thought that a first indicator 8 (Unspecified type of standard number or code) was a better choice. > Unfortunately, and I think this as a reason for its "missuse', dupe > checking is currently bound to 035. For compatibility with forghein > data this should, however, be expanded to 024. I don't follow you here. If I harvest your http://example.de/record/1234, I think that it should have a 024.8x $a oai:example.de:1234, value, and I'll be storing your oai:example.de:1234 in my 035 $a, with an $9 of my own choice. And I can re-expose it as oai:example.cat:2345, keeping your oai:example.de:1234 as dc:identifier (in our Marc21 to DC XSL we export them both). Example: http://ddd.uab.cat/record/77021/export/hm http://ddd.uab.cat/record/77021/export/xd Best regards, Ferran
