http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662
--- Comment #26 from Viktor Sarge <viktor.sa...@regionhalland.se> --- > Our use case > We are harvesting records from the Swedish union catalogue LIBRIS, which > provides records in Marcxml. Today only bibliographic records are harvested, > but we hope to add functionality in the future to also allow holdings to be > harvested (but this is a separate development and won’t be discussed further > here.) We have (as many others) the same use case. Getting holdings would be very great! > All in all, the harvester works as intended! Great news! > Matching rules > At the moment there are not matching rules for the harvester per se. The > only matching that is done is based on the OAI-PMH unique identifier. If > there’s already a record in Koha with the same title, but not the same > OAI-PMH unique identifier, you will get a duplicate. > > Not having matching rules will essentially make the harvester useless for > us, and I would guess anyone harvesting from a union catalogue. We don’t > want to add a lot of unnecessary duplicates to our local catalogue. In case > of libraries who are already running Koha and would want to start using the > harvester, there would be a lot of duplicates (possibly everything!). Also, > we do not want to limit libraries to use one source to harvest from – there > might be a need in the future to harvest from multiple sources. > > We suggest that the “Staged Marc Management” tool should be used to actually > import the records into Koha – then the matching rules that apply there > would be used. Or copying/mirroring this functionality for the harvester. Using the existing import tool sounds like a good plan - then there is a single point to work with for import rules even though we add a new import flow. Much better than building another place to poke around with it's own quirks. > Small issues > * Viewing a server target, the page doesn’t have a back button or working > breadcrumbs. David has suggested that he might not add a back-button but > will fix the breadcrumbs. Breadcrumbs is good enough if they work correctly and brings you one step up and not two-three steps up in the hierarchy. > * Using the daemon, all scheduling can be handled by the GUI A GUI is a selling point in my eyes! Everything that lets the library handle their Koha installation by themselves when they don't themselves have the Linux know how is great! Not having to bug the server people about changes is a big plus. > It would be good to have input from others in the community on the merits of > having the harvester run as a daemon! GUI and short intervals for harvesting gets daemon my vote. But that is without a deeper analysis of technical details. Although I know Zebra indexing can now as a daemon which is viewed as a plus so it can't be all that alien a concept. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/