Location and item information (Marc 952) from Koha 2.x to 3.14
Hi, I'm in the progress of updating my Koha system here from 2.x to 3.14 (a giant leap, seemingly!) After using the built-in migration scripts and fixing many local inconsistencies, I am left with the Koha-to-Marc mapping of the subfields in the 952 tab (Location and item information). I am keeping Koha 2.x Marc framework as a default, and using Koha 3.14 Marc framework to catalogue all new biblios and items. I plan to edit all old biblios (and items) gradually and individually, change them into the new framework, and fill in the missing fields. However, although this seems to work with biblio records, some inconsistencies seem to remain with existing items. After editing and changing framework for a given biblio, I can only edit existing items through the "barcode" link. The framework structure for tag 952 in Koha 3.14 then appears (with most fields blank, of course), and the itemnumber showing in the 952.u subfield, now reserved for the Uniform Resource Identifier. Other values are also assigned to wrong fields, both in the intranet form for cataloguing and in the Opac. I would expect that filling the (new) fields correctly and saving would result in an updated item, now belonging to and complying with the (new) framework. In particular, I would expect that a further attempt at editing the same item would show the correct values filling the appropriate fields. But this is not the case: even though I can check (via direct access to the mysql database) that any modification has indeed taken place as desired, it seems as if the item is still interpreting those values as corresponding to fields arranged as in the old Marc framework. (The bibliographic framework test returns OK, with all the columns in the items table mapped to the 952 subfields as in the "new" framework.) On the other hand, items belonging to biblio records still in the default (old) framework are displayed correctly. Is the Marc framework only specific to biblio records? Shouldn't it be possible to have items belonging to different frameworks? Can two frameworks with different Koha-to-Marc mappings in the 952 tag, as in my case, coexist? Any comment and hopefully help would be greatly appreciated! Many thanks, Giuseppe.
On 17 February 2014 05:59, Giuseppe Angilella <Giuseppe.Angilella@ct.infn.it> wrote:
Hi,
I'm in the progress of updating my Koha system here from 2.x to 3.14 (a giant leap, seemingly!)
Well yeah, the last 2.2.x release was 7 years ago .....
After using the built-in migration scripts and fixing many local inconsistencies, I am left with the Koha-to-Marc mapping of the subfields in the 952 tab (Location and item information).
I am keeping Koha 2.x Marc framework as a default, and using Koha 3.14 Marc framework to catalogue all new biblios and items. I plan to edit all old biblios (and items) gradually and individually, change them into the new framework, and fill in the missing fields.
However, although this seems to work with biblio records, some inconsistencies seem to remain with existing items. After editing and changing framework for a given biblio, I can only edit existing items through the "barcode" link. The framework structure for tag 952 in Koha 3.14 then appears (with most fields blank, of course), and the itemnumber showing in the 952.u subfield, now reserved for the Uniform Resource Identifier. Other values are also assigned to wrong fields, both in the intranet form for cataloguing and in the Opac.
I would expect that filling the (new) fields correctly and saving would result in an updated item, now belonging to and complying with the (new) framework. In particular, I would expect that a further attempt at editing the same item would show the correct values filling the appropriate fields. But this is not the case: even though I can check (via direct access to the mysql database) that any modification has indeed taken place as desired, it seems as if the item is still interpreting those values as corresponding to fields arranged as in the old Marc framework.
(The bibliographic framework test returns OK, with all the columns in the items table mapped to the 952 subfields as in the "new" framework.)
On the other hand, items belonging to biblio records still in the default (old) framework are displayed correctly.
Is the Marc framework only specific to biblio records? Shouldn't it be possible to have items belonging to different frameworks?
Can two frameworks with different Koha-to-Marc mappings in the 952 tag, as in my case, coexist?
Item data in 3.4.x and above is no longer stored in the MARC but in the items table, did you run the script to tidy that up? from the INSTALL file Koha 3.4.x or later no longer stores items in biblio records. If you are upgrading from an older version ou will need to do the following two steps, they can take a long time (several hours) to complete for large databases misc/maintenance/remove_items_from_biblioitems.pl --run misc/migration_tools/rebuild_zebra.pl -b -r I would back up the db, and try this Chris
Dear Chris, thanks for replying. On Mon, 17 Feb 2014, Chris Cormack wrote:
Item data in 3.4.x and above is no longer stored in the MARC but in the items table, did you run the script to tidy that up?
I cannot be sure: I've performed an installation from packages, and several migration scripts were run automatically.
misc/maintenance/remove_items_from_biblioitems.pl --run
The documentation says it would "remove the 9XX fields in the bib records that store a (now) duplicate copy of the item record information". I assume these only include subfields within the 952 tag (say, 999c and 999d would not be removed, as they specify the biblionumber).
Item data in 3.4.x and above is no longer stored in the MARC but in
True: Other users with my same problem will find more details here: http://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx) However, the Marc framework coming with 3.x (3.14 here) does include mappings from subfields under the 952 tag to specific columns in the items table. And I can see these fields in the Marc records entered using the new framework. Is that intentional, say for backward compatibility? (which, in fact, is producing here some in-compatibility!) Many thanks! Giuseppe.
On 17 February 2014 08:15, Giuseppe Angilella <Giuseppe.Angilella@ct.infn.it> wrote:
Dear Chris,
thanks for replying.
On Mon, 17 Feb 2014, Chris Cormack wrote:
Item data in 3.4.x and above is no longer stored in the MARC but in the items table, did you run the script to tidy that up?
I cannot be sure: I've performed an installation from packages, and several migration scripts were run automatically.
However the move items one is explicitly not, as it can take a long time. You need to run koha-upgrade-to-3.4 <instancename>
misc/maintenance/remove_items_from_biblioitems.pl --run
The documentation says it would "remove the 9XX fields in the bib records that store a (now) duplicate copy of the item record information". I assume these only include subfields within the 952 tag (say, 999c and 999d would not be removed, as they specify the biblionumber).
Item data in 3.4.x and above is no longer stored in the MARC but in
True: Other users with my same problem will find more details here:
http://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx)
However, the Marc framework coming with 3.x (3.14 here) does include mappings from subfields under the 952 tag to specific columns in the items table. And I can see these fields in the Marc records entered using the new framework. Is that intentional, say for backward compatibility? (which, in fact, is producing here some in-compatibility!)
It looks like they are in the MARC, we display it that way, they are stored entirely in the items table though, not in the biblioitems.marcxml blob. That is why new items are fine. Chris
Many thanks!
Giuseppe.
Dear Chris,
misc/maintenance/remove_items_from_biblioitems.pl --run
I launched the script above (with an added parameter --where="biblioitemnumber=2388", to restrict its action to one single item, to begin with), and it stripped indeed all the 952 subfields for the (single) item specified from its marcxml column. (A single item is associated with that record.) I've rebuilt the zebra index with koha-rebuild-zebra -v -f , with no errors. Then I changed the framework associated with that record (and edited the record), so to make sure that it now belonged to the "new" framework. However, if I try and edit the item, the cataloguing form (cataloguing/additem.pl?op=edititem) have subfields filled with values belonging to wrong columns in the "items" mysql table (e.g., items.itemnumber fills in the blank for 942 u - Uniform Resource Identifier). Do I have to modify the Koha-to-Marc mapping associated with the "old" framework? But in this case I would lose some functionality with records in the "old" framework, at least until I'll upgrade them all to the "new" framework (hopefully). Many thanks and best regards, Giuseppe.
Dear Chris, briefly: it works! many thanks for your kind advice! :-) Now, a more extensive summary for the possible benefit of other future passers-by (and for my own reference). My problem was I could not properly edit existing items (or edit newly added items) for biblio records belonging to either of two co-existing Koha frameworks. "Old" framework complies with Koha 2.x (and has been inherited by a problematic backup, not properly upgraded for various reasons, some of which disastrous), while "new" framework complies with Koha 3.14 (my present installation). Old framework is my current default here (as most of my records still belong to that framework). Chris pointed out that frameworks prior to 3.x collected item specifications in some subfields of the MARC 952 tag, already in the MARC record (both binary and xml), while more recent frameworks deal with (a lot of more) item information only within the "items" mysql table of the Koha database. However, individual columns of such table are mapped onto specific 952.x subfields. This is indeed described in detail here: http://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx) Chris suggested that I should first remove/strip all items information from the MARC record of each biblio record, which can be done (with some care) through the migration script misc/maintenance/remove_items_from_biblioitems.pl --run (reminder: prepend sudo and the appropriate environment variables, such as PERL5LIB=/usr/share/koha/lib KOHA_CONF=/etc/koha/sites/<your Koha instance>/Koha-conf.xml ) (individual records can be modified by adding the a command parameter such as --where="biblioitemnumber=2388" ; this follows a MySQç syntax) Rebuild the zebra index with sudo koha-rebuild-zebra -v -f Then, I had to modify existing Koha-to-MARC mappings in the old framework for nearly all 952.x subfields, and add all the ones which existed in the new framework but were absent in the old framework, so that all subfields under the 952 tag looked identical in both the old and the new framework. (New framework supersedes the old.) The zebra index must be rebuilt again (I did it several times, as I kept adding/editing subfields, in order to see whether things were working properly). I can now edit/add existing/new items in the new+old/new framework, and see them in the Opac at the correct position (no date showing in the place of replacement cost or itemnumber instead of a URI ... ). Many thanks once more! Giuseppe.
participants (3)
-
Chris Cormack -
Giuseppe Angilella -
Giuseppe Angilella