http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6440 Frédéric Demians <frederic@tamil.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |frederic@tamil.fr --- Comment #1 from Frédéric Demians <frederic@tamil.fr> 2011-10-21 11:23:57 UTC ---
A starting point might be to define sets based on libraries/branches and/or item types. Taking it a step further one could imagine adding a config file that would let sysadmins define more sets with some kind of queries.
Koha OAI server requests directly MySQL database in order to get all biblio records biblionumbers. So for now, without changing Koha OAI engine, we would have to limit queries to MySQL queries. We could imagine something like: ALL: SELECT biblionumber FROM biblio; PER: SELECT biblionumber FROM biblioitems WHERE itemtype='PER';
This lack of sets seems to be a stumbling block when trying to integrate Koha with e.g. XC (http://www.extensiblecatalog.org/), which expects to get a list of sets from it's OAI-PMH sources.
We could very easily define a ALL set returning the whole catalog as it's already done. Koha OAI Server doesn't have also incremental harvesting capabilities. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.