Hello Tibor, [...] > The above-mentioned 970/035 split for external sysnos is mostly > historical; there is no reason why we cannot apply the controlled > provenance concept to 970 too, if need be. > > Summa summarum: if you want to use a tag like 035 to store your > additional external system identifiers, then the latest git sources will > work for you out of the box. If you want to keep using multiple > external sysnos in 970 (and differentiate between them via $9), then it > is possible, but we shall have to patch bibupload slightly alongside > what was done for CFG_BIBUPLOAD_EXTERNAL_OAIID_PROVENANCE_TAG in order > to fit this use case. (I mean patch git sources, not v0.92.1.)
Thank you for your very clear explanation. As a matter of fact, and due to our recent ILS migration, we had to clarify those external sysnos for the other system, and there was a clear dictum to use 035. So we were also considering 035 for our Invenio, and our future is clearer now after updating our system in the next few weeks... > P.S. If you are sure that you don't have any extsysno clashes between > your sources, then you can simply hack your bibupload 0.92.1 > sources around that ``sysno = sysnos[0]'' line, in order to process > checking all sysno values, not only the first one. That's what I did a few minutes ago ;-) Vale, Ferran
