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

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

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

--- Comment #62 from David Cook <dcook at prosentient.com.au> ---
It's worth mentioning that my above comment regarding holdings is probably only
relevant for some systems like Voyager, and are not relevant for all holdings
records...

Those comments are based on the following pages:

http://library.princeton.edu/departments/tsd/katmandu/voyager/holitmono.html
http://library.princeton.edu/departments/tsd/katmandu/voyager/relink.html
http://library.princeton.edu/departments/tsd/katmandu/voyager/chgloc.html
http://www.library.illinois.edu/cam/training/voyagerscript.html

However, it does appear that there are fields in holdings records for
individual items:

876$a is an "Internal item number"
(http://www.loc.gov/marc/holdings/hd876878.html). While I haven't seen this in
LIBRIS holdings data, it is a field/subfield which exists. 876$p could then be
used for the barcode. 

Looking at this example:
852     0#$aTxAM$bStacks$hHD9195.A5$iW5
876     ##$aAAH8128-1-1$c$13.75$pA14802137389

852$a = Location (ie Library)
852$b = Sublocation/Collection (Branch)
852$h = Classification part (start of call number)
852$i = Item part (end of call number)

876$a = Internal item number (itemnumber)
876$c = Cost (cost)
876$p = Piece designation (barcode)

However... the 876 subfields are really only useful if they're present. If your
record just has a 852 without any actual item-level data... you can't very well
do add/match/update items in Koha without it. 

Even in the event though that you have 876 data, there are hurdles as outlined
below.

It's not too bad when there is one 852 and one 876 for a single part item: "One
copy, one 852 field - Item fields do not need a linking subfield as all apply
to the one holdings item. (Holdings are recorded at level 1 or 2 in Leader/17
(Encoding Level).) [See example under subfield $p below]"
(http://www.loc.gov/marc/holdings/hd876878.html).

However, "Multiple copies, one or more 852 fields - Subfield $3 is used to link
item fields to the appropriate copy in 852 field(s). (Holdings are recorded at
level 1 or 2 in Leader/17 (Encoding Level).) [See example under subfield $e
below]" (http://www.loc.gov/marc/holdings/hd876878.html). 

But the $3 subfield isn't a coded field. It's free text, which foils any
consistent automated linking.

It gets even more complicated for "Multiple physical part holdings item": 

"Holdings in 866-868 (Textual Holdings) fields - Subfield $3 is used to link
item fields to the appropriate part specified in fields 866-868. (Holdings are
recorded at level 3 or 4 in Leader/17 (Encoding Level).) [See example under
subfield $h below]

Holdings in 863-865 (Enumeration and Chronology) fields - Subfield $8 is used
to link item fields to the appropriate part specified in fields 863-865. Each
part (volume or volumes) for which item level information is included requires
a separate 863-865 field. (Holdings are recorded at level 3 or 4 with piece
designation in Leader/17 (Encoding Level).) [See example under subfield $l
below]"

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