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

--- Comment #18 from Marcel de Rooy <m.de.r...@rijksmuseum.nl> ---
(In reply to paxed from comment #17)
> (In reply to Marcel de Rooy from comment #16)
> > (In reply to paxed from comment #5)
> > > Comment on attachment 73805 [details] [review] [review] [review]
> > > Bug 20310: Introduce Koha::Biblio->host_record
> > > 
> > > Shouldn't this also check that the 003 fields match? AFAIUI, 001+003 is
> > > unique, 001 is not guaranteed to be - because you could import data from
> > > different organization.
> > 
> > Added a check with pref MARCOrgCode
> 
> But if you import data from another org then the orgcode (field 003) for
> those records won't be your org, but something else. You should match the
> 773$w orgcode to the host biblio 003

Hi paxed,
I understand your point. But I am not so sure if we do these checks somewhere
in Koha. In my proposal I ignore (Remote)x and only look at z or (My)z.
If record z from (My)z is found, I do not check if 001==z and 003==My.
Similarly, if record x from (Remote)x would be in our system (which I don't
know) we also don't know if 001==x and 003==Remote.
Practical question would be too: Do we really want to check all 773 contents
and pull all 001, 003s?

Since this logic is all about record control number handling in Koha and imo
outside the scope of this report, we c/should move further refinements to a new
report. But I have doubts about what we should check. This is a discussion on
its own..

Thx for your feedback though.

-- 
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/

Reply via email to