https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27121 --- Comment #2 from Séverine Queune <severine.queune@bulac.fr> --- Hi Katrin! Here are two cases we've got at BULAC. 1/ A lot of our collections are still on card catalog only. Some of my colleagues are working on cataloging them : they work on SUDOC (the French collective catalogue for Higher Educational and Research libraries) and each night, items and biblios enter Koha with unique identifiers linking to SUDOC ('ppn' for biblios and 'epn' for items). Sometimes, for various reasons, some of the items were quickly and locally created in Koha, because it was important to have them there to follow a specific circuit (external loan for exhibition, etc.), and we regularly find duplicates. The problem is that most of the case concerns our old and precious collections that have change of callnumber so we've got: - a local item with the new callnumber and informations about some physical peculiarities we noticed - an item created in SUDOC with the old (and now wrong) callnumber and a unique 'epn' The idea was to have a tool, like it exists for biblios, to select the 2 items and to check wich datas we want to keep from each items, in the present case all the datas of the local item + the epn for the SUDOC item. 2/ We had a problem during the initial loading of the datas in Koha for subscriptions. The first load in March 2011 created items with callnumber and serial history only. The second load in May 2011 creates duplicates with callnumber and all the datas about origin of the collection and the 'epn', but no serial history. We still have about 1800 identified duplicates to manually merge... I attach an exemple of a duplicates for subscription linked to items with, in green, the datas we want to keep from form each item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27121 --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hi Severine, thx for the summary, that makes a lot of sense! We should note that a merge tool needs to be aware of updating the links to subscriptions (serialitems) and to the acquisition order (aqorders_items). And possible course reserves (course_items). Any others we could think of? I think it might also be nice to log the merge in the cataloguing logs so there is still a way to figure out the merged itemnumbers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27121 --- Comment #6 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I think a new user permission makes sense. I am not sure what to do about the last borrower in this case. Would it be possible that both items have a 'last borrower'? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27121 --- Comment #8 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Sounds like we almost have a spec now - who will write it? :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.