[Koha-devel] MARC Holdings, Koha, and Migration

[Thomas D]

MARC 21 TO KOHA HOLDINGS MAPPINGS

draft 0.02

Corrected generally, and with reference to information about Koha tables
that Chris Cormack and Paul Poulain gave me over IRC.  Thank you Chris and Paul.

Yes this is missing mapping for other tables that might be part of the
migration process.  Mapping to the Koha items table for MARC 21 holdings is
the only issue treated here.

Mapping existing standard data to a MARC 21 local use field is necessary
when migrating holdings to Koha.  If using the default local use field 952,
the following may be a common mapping.  Be sure to construct unique 952
fields populated from the corresponding $t, if present.  Mappings with
multiple subfields listed should have all listed subfields mapped to the
corresponding local use 952 subfield where the last populated subfield value
would overwrite any previous populated value for that local use 952 subfield.

Map 852 $t, 876 $t, 877 $t, and 878 $t to 952 $t for a nonexistent
items.copynumber column.  (If you have been using $3, you should find some
way of combining $t with $3 to form a unique whole number.)  Do not link
items.itemnumber to a MARC subfield, not even 952 $t in the MARC to Koha
links to avoid possible loss of data.  Koha will assign a unique itemnumber
to your items with no help from your old records.  If you need to maintain
your existing copy numbers in a Koha table, create a new column in Koha for
representing that information, such as items.copynumber, and program a
solution.  You could append copy numbers to an appropriate subfield
accompanied by a text label 'copy ' within an existing value such as call
number, given below, and suppress appending in cases where only one copy exists.

Map 852 $p, 876 $p, 877 $p, and 878 $p to 952 $p for items.barcode.

Map 541 $d; or 876 $d, 877 $d, and 878 $d to 952 $d for items.dateaccessioned.

Map 850 $a, 852 $a, or 852 $b to 952 $b for items.homebranch.  Be sure to
convert to the 4 character all caps code as defined for Koha branches.

Map 541 $h; or 876 $c, 877 $c, and 878 $c to 952 $o for items.price.

Map 365 $b; or 876 $c, 877 $c, and 878 $c to 952 $u for items.replacementprice.

Map 365 $f to 952 $r for items.replacementpricedate.

Map 852 $b to 952 $d for items.holdingbranch.  Be sure to convert to the 4
character all caps code as defined for Koha branches.

Map 506 $a, 876 $h, 877 $h, and 878 $h to 952 $y for items.notforloan.  Be
sure to convert to an integer where NULL or 0 is for loan and 1 is for loan.

Map 876 $j, 877 $j, and 878 $j to 952 $1 for items.itemlost.  Be sure to
convert to an integer where NULL or 0 is not lost, 1 is lost and paid for by
the party responsible for losing the item, and 2 is lost with no payment yet.

Map 876 $j, 877 $j, and 878 $j to 952 $w for items.withdrawn.  Be sure to
convert to an integer where NULL or 0 is not withdrawn and 1 is restricted.

Map 852 $k, 852 $h, 852 $i, and 852 $m concatenated together sequentially to
952 $h for items.itemcallnumber.

Map 506 $a, 876 $j, 877 $j, and 878 $j to 952 $4 for items.restricted.  Be
sure to convert to an integer value where NULL or 0 is not restricted and 1
is restricted.

Map 852 $c, 856 $u, 876 $l. 877 $l, and 878 $l to 952 $c for items.location.


Thomas D


---------------------------------------------
Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com