[Koha-bugs] [Bug 7947] 440/490 Koha Mapping

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Apr 22 15:24:49 CEST 2020


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

--- Comment #17 from Frank Hansen <frank.hansen at ub.lu.se> ---
(In reply to Katrin Fischer from comment #15)
> I think it's good we can map multiple fields now :)
> 
> I've focused here on the change from 440 to 490. Would you all agree for
> this to be an improvement for now, so we could move further refinement to a
> separate bug?
> 
> The patches attached took me quite a while to write, as I am not a script
> wizard and did them manually. If one of you wants to have a go for
> additional changes, please go for it as I will have to foucs on my QA duties
> a bit more and probably won't find the time soon.
> 
> Generally:
> $n = number, 
> $p = part, 
> $v = volume (probably usually a number?)
> 
> The 8xx should usually appear with a 490 for traced series, although I am
> not sure every library sticks to that "ideal" cataloguing. Therefore I think
> mapping 490 is good and it's also needed for untraced series.
> 
> For 8xx we could then do:
> 
> http://www.loc.gov/marc/bibliographic/bd80x83x.html
> 800, 810, 811, 830
> $n = biblioitems.number
> $p = biblioitems.volume
> 
> All fields might appear multiple times, and the subfields are repeatable
> too. This So we will not end up with the perfect solution with the current
> db structure, but columns should be filled more often than not, being
> helfpul für reports and in other places.

I agree to work the 8xx fields in a separate bug since this might be more
complicated.

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


More information about the Koha-bugs mailing list