Hi Craig, I think I'd be using 001/003 or 035 with a prefix identifying the source of the number. I would not change Koha's default mappings or use the biblionumber/biblioitemnumber subfields - I'd expect this to cause problems quite easily.
Hope this helps, Katrin Am 08.07.2016 um 00:09 schrieb Craig Butosi: > Hi Joy, > > Thank you for the heads-up about indexed fields. I forgot about this. Looks > like MARC 887 isn’t indexed > (http://manual.koha-community.org/16.05/en/kohasearchindexes.html), so I’ll > consider 999 or 001; I have record matching rules for both. Still open to > what others have done in the past too. > Many thanks, > C > > Craig Butosi, MA, MLIS, B Mus (Hons.) > LIBRARY SERVICES MANAGER > the royal conservatory > TELUS Centre for Performance and Learning > 273 Bloor Street West > Toronto, ON M5S 1W2 > 416.408.2824 x338 > www.rcmusic.ca<http://www.rcmusic.ca/> > > From: Joy Nelson [mailto:[email protected]] > Sent: July-07-16 4:42 PM > To: Craig Butosi > Cc: [email protected] > Subject: Re: [Koha] Koha 16.05 - Legacy Bibliographic Unique ID numbers > mapped to Koha 999c/d? > > I've done this a few ways. It depends on if you will need to match incoming > data to the records after you import them. > I generally leave the legacy bib id in a 9xx tag (either 998 or 907), however > if you want to match against that number in the import stage marc records you > will want to use a field that is indexed. Another good choice is the 001 > (control-number) if you are not already using that field for some other > purpose. > joy > > On Thu, Jul 7, 2016 at 2:36 PM, Craig Butosi > <[email protected]<mailto:[email protected]>> wrote: > Hi all, > > Koha 16.05 on Ubuntu 14.04, package install. > > A brief question about bibliographic record unique identifiers and importing > records into an empty Koha instance: > > Is it advisable to map the unique ID numbers from a legacy system's > bibliographic records to Koha 999c/d? I am attempting to find a way to > connect our items database data to our bibliographics data once the latter > has been uploaded to Koha. I imagine the best way to do this is to preserve > the unique IDs (i.e., primary key in biblio, foreign key in items) from the > legacy system, but I'm not quite sure how I should go about mapping this: > should I go for Koha 999c/d, Marc 887, or some other field? The record > matching module in Koha gives me much choice, but what does the collective > wisdom think? > > Thank you! > > C > > Craig Butosi, MA, MLIS, B Mus (Hons.) > LIBRARY SERVICES MANAGER > the royal conservatory > TELUS Centre for Performance and Learning > 273 Bloor Street West > Toronto, ON M5S 1W2 > 416.408.2824 x338 > www.rcmusic.ca<http://www.rcmusic.ca><http://www.rcmusic.ca/> > > > > Note: This email message and any attachments are intended only for the use of > the individual to which it is addressed, and may contain information that is > privileged, confidential and exempt from disclosure under applicable law. If > the recipient of this email is not the intended recipient (or the employee or > agent responsible for delivering the email to the intended recipient), you > are hereby notified that any review, dissemination, distribution or copying > or other use of this message is strictly prohibited. If you have received > this communication in error, please notify the sender immediately by return > email and delete this message and attachments from your system, thank you. > _______________________________________________ > Koha mailing list http://koha-community.org > [email protected]<mailto:[email protected]> > https://lists.katipo.co.nz/mailman/listinfo/koha > > > > -- > Joy Nelson > Director of Migrations > ByWater Solutions<http://bywatersolutions.com> > Support and Consulting for Open Source Software > Office: Fort Worth, TX > Phone/Fax (888)900-8944 > What is Koha? <http://bywatersolutions.com/what-is-koha/> > > > Note: This email message and any attachments are intended only for the use of > the individual to which it is addressed, and may contain information that is > privileged, confidential and exempt from disclosure under applicable law. If > the recipient of this email is not the intended recipient (or the employee or > agent responsible for delivering the email to the intended recipient), you > are hereby notified that any review, dissemination, distribution or copying > or other use of this message is strictly prohibited. If you have received > this communication in error, please notify the sender immediately by return > email and delete this message and attachments from your system, thank you. > _______________________________________________ > Koha mailing list http://koha-community.org > [email protected] > https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ Koha mailing list http://koha-community.org [email protected] https://lists.katipo.co.nz/mailman/listinfo/koha
