[Koha-bugs] [Bug 10662] Build OAI-PMH Harvesting Client

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Nov 30 00:41:13 CET 2015


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662

--- Comment #47 from David Cook <dcook at prosentient.com.au> ---
Leif and Andreas:

If I understand correctly, your main use case for matching would be to make
sure that records previously imported from the union catalogue aren't
duplicated when you start using OAI-PMH, yes?

In that case, would matching on the 001 be suitable? 

You could configure your OAI-PMH importer module to look for "metadata.value ==
incoming record 001" and update the matching record. That would prevent
duplication in this situation.

I think in that situation it would also be good to add a "metadata.value" for
the unique OAI-PMH Identifier... and only update a record if it has no OAI-PMH
identifier or if it has a OAI-PMH Identifier that matches the incoming record.

That way, you might prevent different OAI-PMH repositories from updating each
other's records if you're matching using 020 instead of 001. 

Since I want the OAI-PMH importer to be plugin based, the rules will be
customizable. 

But if we're not going to use Zebra or some other third-party index, I think
Leif's suggestion of a new "exported" metadata table might be necessary. 

Failing that "metadata" table... there is the "import_biblios", "import_items",
and "import_auths" tables which might be re-purposed. "import_biblios" and
"import_auths" both have a "control_number" field which I think may be
unused... but that won't work in the case that you already have records in Koha
which need to expose data for matching.

In an effort to move this matching discussion along, I'm going to submit a
message to the koha-devel listserv as well to discuss the "metadata" table
idea.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list