On Mon, 14 Mar 2011, Samuele Kaplun wrote: > OK, let's assume we would like at least to preserve the OAI ID in the > MARC, just to be sure if the record is in any time changed of recid, > the OAI ID is still preserved to guarantee uniqueness.
Yes, it is generally advantageous if OAI ID is kept in MARC together with the rest of the record metadata. > Still, what if instead storing OAI Set in the MARC, we store them > aside as something completely analogous to collections? > > Would we miss anything if we wouldn't put the Set information in the > MARC anymore? The OAI Set information may in principle live elsewhere more easily. For example, one may want to base OAI sets on other metadata fields, such as the subject category field, in which case the OAI Set field would not be really necessary for the run-time look-up. Having OAI Set information in MARC alongside OAI ID may be nice for consistency and other reasons though. It may be good for those Invenio instances that do not use OAI Repository Updater but manage OAI IDs and Sets otherwise. If all this information lives in MARC, then one may use regular cataloguing tools such as record editor, multi-record editor and friends in order to check and manipulate this information. I'd say let's keep both in MARC as a first reflex unless the split is really beneficial... Best regards -- Tibor Simko
