Because we have ran out of MARC subfield codes, we cannot add more Item-columns from the DB to the search indexable MARC Record. This patch enables support for "Koha to MARC mapping" to work on other Fields as well. This patch enables editing Items' columns mapped to non-standard MARC Items Fields. No further issues regarding using non-standard Item fields identified yet.
Created attachment 35896 [details] [review] Bug 13708 - MARC Mapping Item columns to several MARC Fields Because we have ran out of MARC subfield codes, we cannot add more Item-columns from the DB to the search indexable MARC Record. This patch enables support for "Koha to MARC mapping" to work on other Fields as well. This patch enables editing Items' columns mapped to non-standard MARC Items Fields. No further issues regarding using non-standard Item fields identified yet.
We have used Uppercase letters successfully for some things.
Thanks for the comment! What do you mean with "some" things?
Also I have a feeling that MARC standard has only lowercase subfield codes? I don't know for sure.
Storing additional item related information - Koha seems to deal with it well, although you might be right about the standard :) I know we have uppercase subfield codes in some of the data we receive as well.
Katrin, thanks for the tip. I'l ltry your suggestion. The additems.pl is such an ridiculous mess any modifications I would make would make it even worse. The remnants of MARC:ified Items need bo be better encapsulated instead of thrown around in every conceivable file.
Hm, from the comments on IRC maybe I misunderstood what you are trying to do? What we do is use upper case letters with no explicit mapping to a field in the items table in the configuration - this way the data ends up in items.more_subfields_xml. If you found a problem with this approach it would be good to know!