August 2017 - Koha-bugs - lists.koha-community.org

[Bug 10306] Allow multiple Koha to Marc mappings ( say publication info in MARC21 260 or RDA 264)
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10306 --- Comment #21 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Created attachment 65540 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65540&action=ed… Bug 10306: Allow controlfields in TransformKohaToMarc Since the interface allows you to connect a kohafield to a MARC controlfield, this routine should be able to handle that. Unfortunately it did not. Test plan: Change will be tested in Biblio/TransformKohaToMarc.t in the next patch. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10306] Allow multiple Koha to Marc mappings ( say publication info in MARC21 260 or RDA 264)
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10306 --- Comment #20 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Created attachment 65539 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=65539&action=ed… Bug 10306: Biblio module changes In order to allow multiple Koha to MARC mappings (for one kohafield), we need to adjust a few key routines in C4/Biblio.pm. This results in a few changes in dependent modules too. Note: Multiple mappings also include 'alternating' mappings. Such as the case of MARC21 260 and 264: only one of both fields will be used. Sub TransformMarcToKoha will handle that just fine; the opposite transformation is harder, since we do no longer know which field was the source. In that case TransformKohaToMarc will fill both fields. We only use that operation in Koha for items (in Acquisition and Cataloging). Sub GetMarcSubfieldStructure This sub used a selectall_hashref, which is fine as long as we have only one mapping for each kohafield. But as DBI states it: If a row has the same key as an earlier row then it replaces the earlier row. In other words, we lose the first mapping if we have two. This patch uses selectall_arrayref with Slice and rearranges the output so that the returned hash returns an arrayref of hashrefs for each kohafield. In order to improve consistency, we add an order clause to the SQL statement used too. Sub GetMarcFromKohaField This sub just returned one tag and subfield, but in case of multiple mappings we should return them all now. Note: Many calls still expect just one result and will work just fine: my ($tag, $sub) = GetMarcFromKohaField(...) A possible second mapping would be silently ignored. Often the sub is called for biblionumber or itemnumber. I would not recommend the use of multiple mappings for such fields btw. In case the sub is called in scalar context, it will return only the first tag (instead of the number of tags and subfields). Sub GetMarcSubfieldStructureFromKohaField This sub previously returned the hash for one kohafield. In scalar context it will behave like before: it returns the first hashref in the arrayref that comes from GetMarcSubfieldStructure. In list context, it returns an array of all hashrefs (incl. multiple mappings). The sub is not used in C4::Ris. Removed the use statement. Sub TransformKohaToMarc This sub got a second parameter: frameworkcode. Historically, Koha more or less assumes kohafields to be defined across all frameworks (see Koha to MARC mappings). Therefore it falls back to Default when it is not passed. When going thru all mappings in building a MARC record, it also supports multiple mappings. Note that Koha uses this routine in Acquisition and in Cataloging for items. Normally the MARC record is leading however and the Koha fields are derivatives for optimization and reporting. The added third parameter allows for passing a new option no_split => 1. We use this option in C4::Items::Item2Marc; if two item fields are mapped to one kohafield but would have different values (which would be very unusual), these values are glued together. When transforming to MARC again, we do not want to duplicate the item subfields, but we keep the glued value in both subfields. This operation only affects items, since we are not doing this reverse operation for biblio and biblioitem fields. Sub _get_inverted_marc_field_map This sub is a helper routine of TransformMarcToKoha, the opposite transformation. When saving a MARC record, all kohafields are extracted including multiple mappings. Suppose that you had both 260c and 264c in your record (which you won't), than both values get saved initially into copyrightdate like A | B. The additional code for copyrightdate will extract the first year from this string. A small fix in TransformMarcToKoha makes that it only saves a value in a kohafield if it is defined and not empty. (Same for concatenation.) Sub TransformMarcToKohaOneField This sub now just calls TransformMarcToKoha and extracts the requested field. Note that since we are caching the structure, this does not result in additional database access and is therefore performance-wise insignificant. We simplify code and maintenance. Instead of modifying the passed hashref, it simply returns a value. A call in C4::Breeding is adjusted accordingly. The routine getKohaField in Koha::MetadataRecord is redirected to TransformMarcToKohaOneField. NOTE: The fourth patch restructures/optimizes TransformMarcToKoha[OneField]. Sub get_koha_field_from_marc This sub can be removed. A call is replaced by TransformMarcToKohaOneField in C4::XISBN. Note: The commented lines for sub ModZebrafiles are removed (directly under TransformMarcToKohaOneField). Test plan: For unit tests and interface tests, please see follow-ups. Run qa tools in order to verify that the modules still compile well. Read the code changes and verify that they make sense. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12566] Duplicate checks for Self Registered borrowers
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12566 --- Comment #3 from Emma Perks <emma.perks(a)heartofengland.nhs.uk> --- Primary email check is a great start thank you, but we need a more robust way of checking, several fields if possible. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 6725] patron duplicate matching
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6725 Emma Perks <emma.perks(a)heartofengland.nhs.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emma.perks(a)heartofengland.n | |hs.uk --- Comment #1 from Emma Perks <emma.perks(a)heartofengland.nhs.uk> --- Valid - needed -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 12412] Add ability for plugins to convert arbitrary files to MARC from record staging tool
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12412 --- Comment #17 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Bug 10407 made this rather invisible feature disappear again. Bug 19049 should recover that. It would have been better (looking back) to put some more pointers in the code about this arbitrary format. You should not pass excel files in a variable called $marcrecords.. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12412] Add ability for plugins to convert arbitrary files to MARC from record staging tool
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12412 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=19049 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10407] Allow MARCXML records to be imported with Tools/ Stage MARC records for import
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10407 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=12412 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12412] Add ability for plugins to convert arbitrary files to MARC from record staging tool
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12412 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=10407 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10407] Allow MARCXML records to be imported with Tools/ Stage MARC records for import
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10407 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |19049 --- Comment #56 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #55) > Hm, I don't agree with saying that plugins are not part of the codebase and > people are 'lucky' if they work. Hmm, this is definitely not what I said! Specific plugins are simply not part of the codebase. Just a fact. I was not aware of the statement in the 3.20 release notes btw. Without that statement you were lucky if you got excel files into Koha. Do not take these words out of their context please. > We highlighted creating plugins to convert arbitrary files as a new feature > in the release notes of 3.20: > > https://koha-community.org/koha-3-20-0-released/ > Add ability for plugins to convert arbitrary files to MARC from record > staging tool (bug 12412) The conversion from arbitrary files should have been incorporated much more clearly in the interface and the code imo. The format option of the interface does not show Arbitrary only MARC or MARCXML. It is not mentioned in the online Help too. The code passes variable $marcrecords to BatchStageMarcRecords. Inside BatchStageMarcRecords the to_marc plugin is called. Again the same variable name $marcrecords is used. No mention of any arbitrary file type! No comment whatsoever, etc. So I can imagine that when Olli wrote the initial patches, he was not aware of this. Neither was I when I rescued these patches and got them further. At this point, we can only open a new report to add e.g. Arbitrary to the formats when we have a plugin, or some other description from the plugin. And call to_marc on these lines before passing them to BatchStageMarcRecords. See bug 19049. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19049 [Bug 19049] Recover the Arbitrary file type on stage-marc-import with plugin to_marc -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12691] Use Koha.Preference for calls to SCOUserJS, SCOUserCSS, OPACUserCSS, opacuserjs, etc in Self-Checkout
by bugzilla-daemon＠bugs.koha-community.org 07 Aug '17

07 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12691 --- Comment #15 from Marc Véron <veron(a)veron.ch> --- Can not test ATM because of Bug 19048 -- You are receiving this mail because: You are watching all bug changes.

1 0