Hello Samuele, [...] > In Invenio there is a special treatment for this 035 field, namely that > the couple OAIID_TAG + OAIID_PROVENANCE_TAG is used to identify uniquely > a record. > > So shall I simply add by default to 035 the above mentioned attributes? > > E.g. > > * baseURL -> $u (different than $9 which is a semantic string. The > baseURL might change because of technical reasons, and therefore the $9 > subfield, when present will receive priority in identify a record). > * identifier -> $a (as per CFG_BIBUPLOAD_EXTERNAL_OAIID_TAG) > * datestamp -> $d > * metadataNamespace -> $m > * originDescription -> $o > * harvestDate -> $h > * altered -> $a > > Is there anyone in the Invenio community whose system is harvesting > record (putting external IDs in 035) and is trying to expose them?
We also do it. After backporting your 2fb7275849e83f5afbb7915000e208a3e053889a patch to 0.99.1, now we store in 035 $a all kinds of external identifiers, including external OAI ids, with $9 acting as a kind of «namespace identifier» to avoid conflicts. As per our own OAI id, we spent some time to conclude that, instead of a local 9XX field, it should go to 024.8_: http://www.loc.gov/marc/bibliographic/bd024.html CFG_OAI_SET_FIELD = 0248_9 CFG_OAI_ID_FIELD = 0248_a So, even if we are re-exposing a small part of our harvested holdings, at this moment we don't reuse the same tag for both uses. I understand the need of your suggested fields ($d, $m, etc.), but please don't hurry up adding non standard subfields to 035. The more your default values depart from Marc21 standard, the more difficulties you are posing to interchange records with other databases, and more troubles to potential Invenio newcomers. I don't have the solution right now, but your fields don't appear in the standard: http://www.loc.gov/marc/bibliographic/bd035.html Maybe you can ask to some librarian before deciding them. Thanks, Ferran
