[Koha-bugs] [Bug 25603] Add 001 and 003 to biblio table

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25603

--- Comment #4 from David Cook <dcook at prosentient.com.au> ---
I'm trying to think how we could do this in a more extensible way... and I
might have an idea.

MARC:
001 - Control Number
003 - Control Number Identifier
005 - Date and Time of Latest Transaction

OAI-PMH:
identifier
baseURL
datestamp

These two schemas actually overlap pretty much perfectly, and those are the 3
criteria I use when I'm matching for my OAI-PMH imports. 

It's basically a record number, a record origin, and a last modified date. When
matching, if the record number and origin match and the inbound record is
newer, update the record. Easy.

Thinking about other metadata schemas... 
- Unqualified Dublin Core wouldn't fit that pattern, but that's partially
because it's too simplistic of a schema. Qualified Dublin Core could. 
- I don't know BIBFRAME well enough. Looking at
https://www.loc.gov/bibframe/implementation/register.html, I see a
bf:changeDate. I suppose maybe their "Control Number Identifier" or "baseURL"
could be empty since the BIBFRAME URI should be globally unique. Although
BIBFRAME is just a whole other ball game anyway...
-MODS has a recordIdentifier for 001, and recordIdentifier "source" attribute
for 003, and recordChangeDate for 005...

I suppose the reality is that we just support MARC for the time being, and we
have no idea what a post-MARC world will actually look like, so maybe we should
just develop against a MARC world.

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