Hello Samuele, [...] >> 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 > > And this is precisely what is finally supported by the new branch that > will soon be merged. OTOH you use the default shipped invenio.conf
Well, no, sorry for the poor example. What happens is that this particular record is no re-exposed, and I didn't find a quick example of a record with an external OAI id *and* a local 024. This is better, because it has a few 035 (but no OAI ids due to a recent external migration) and a local 024: http://ddd.uab.cat/record/70053/export/hm > (which is trying to be as much backward compatible as possible, and > therefore keeping on using 909CO as default), but with the more OAI-PMH I'm afraid I'll challenge you here ;-) Soon I'll be opening a task in invenio-software.org trac requesting that the default Marc values of Invenio should match the standard, for the benefit of all, specially newcomers. Experienced Invenio admins already know how to tune, change, etc. But we should be more friendly to newcommers, and if we say that we follow Marc21, we should comply much better than now, don't you think? Thanks, Ferran
