[Bug 37600] New: OpacSuppression does not work in Unimarc
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 Bug ID: 37600 Summary: OpacSuppression does not work in Unimarc Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs@lists.koha-community.org Reporter: Igor.A.Sychev@mail.ru QA Contact: testopia@bugs.koha-community.org OpacSuppression does not work in Unimarc. If I understood correctly, need to add <index_subfields tag="955" subfields="n"> <target_index>Suppress:w</target_index> <target_index>Suppress:n</target_index> </index_subfields> in https://git.koha-community.org/Koha-community/Koha/src/branch/main/etc/zebra... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fridolin.somers@biblibre.co | |m, | |julian.maurice@biblibre.com | |, sonia.bouis@univ-lyon3.fr Summary|OpacSuppression does not |OpacSuppression does not |work in Unimarc |work in UNIMARC out of the | |box --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- It's not quite enough, you also need to run a script to translate the readable entry. See here: https://wiki.koha-community.org/wiki/How_to_add_new_zebra_index (Step 5) For MARC21 the index is set up by default and I think it would be nice to have it also for UNIMARC Is 955$n OK to make the default for UNIMARC? (adding some other UNIMARC users/devs in CC) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #2 from Fridolin Somers <fridolin.somers@biblibre.com> --- (In reply to Katrin Fischer from comment #1)
Is 955$n OK to make the default for UNIMARC? (adding some other UNIMARC users/devs in CC)
We largely use 099$o but I can't find a doc about this field. We already use it in Koha for 099 $c and $d. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- If UNIMARC is similar to MARC21 it's maybe a custom field (like the 9xx in MARC). Do we know where the 955$n came from? We could index both maybe? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #4 from Igor A. Sychev <Igor.A.Sychev@mail.ru> --- In UNIMARC: 9-- Local Fields -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #5 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I would love to add an index to make it work out of the box for UNIMARC users, but I am a little worried about picking the wrong field. If the library has other data in the field already and OpacSuppression is activated, all those record would be hidden on update. I'd like to get some more opinions on the use of 9xx maybe, to see how much of a risk that would be. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #6 from Igor A. Sychev <Igor.A.Sychev@mail.ru> --- There are big doubts that someone at Koha is using $955n for other purposes. And when you "move" from another ILS, all 9xxs are converted to the new 9xx. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 Koha Team University Lyon 3 <koha@univ-lyon3.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koha@univ-lyon3.fr --- Comment #7 from Koha Team University Lyon 3 <koha@univ-lyon3.fr> --- (In reply to Igor A. Sychev from comment #6)
There are big doubts that someone at Koha is using $955n for other purposes. And when you "move" from another ILS, all 9xxs are converted to the new 9xx.
Hi, we do use 995$n for other purpose. For my library, this field is mapped with items.onloan. Sonia -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #8 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Koha Team University Lyon 3 from comment #7)
(In reply to Igor A. Sychev from comment #6)
There are big doubts that someone at Koha is using $955n for other purposes. And when you "move" from another ILS, all 9xxs are converted to the new 9xx.
Hi, we do use 995$n for other purpose. For my library, this field is mapped with items.onloan.
Sonia
Hi Sonia, thanks for letting us know. I am not sure how to get out of this situation really without causing pain for anyone :( -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathsabypro@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #9 from Mathieu Saby <mathsabypro@gmail.com> --- Hello If I understand well, in Marc21 this field is defined in 942, at record level. In my opinion the equivalent for Unimarc should be a subfield of 099 Currently in main, these subfields are used : c (date created),d (timestam),s (serial) ,t (record type),x (nb of issues) So why not 099$n ? (By the way the name of 099 field should be changed, it should not be "local dates" but something more generic) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #10 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Can you make a suggestion for the new name? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #11 from Mathieu Saby <mathsabypro@gmail.com> --- For the 099 field? Maybe "Local field (Koha)". Or "Added entry elements (Koha)" like Marc21 942 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 Mathieu Saby <mathsabypro@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #12 from Mathieu Saby <mathsabypro@gmail.com> --- I will submit a patch for fixing this issue -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 Laurence Rault <laurence.rault@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |laurence.rault@biblibre.com --- Comment #13 from Laurence Rault <laurence.rault@biblibre.com> --- Usually we use 099$o for the Suppress field at bibliographic level. It is not a Unimarc field, but a local one. The 'o' was defined by BibLibre years ago ('o' for opac), so I propose we use it for standard configuration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #14 from Mathieu Saby <mathsabypro@gmail.com> --- The choice between 099 and 942 will depend on the resolution of https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38336 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 Mathieu Saby <mathsabypro@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |38336 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38336 [Bug 38336] Confusion between 099 and 942 field in UNIMARC framework -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 --- Comment #15 from Mathieu Saby <mathsabypro@gmail.com> --- In https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38336 we decided to put UNIMARC "Koha" info in 099, but it only deals with information already in the frameworks. So when it is pushed I will provide a patch for managing a "Suppress" flag in a subfield of the 099 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37600 Mathieu Saby <mathsabypro@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |mathsabypro@gmail.com |ity.org | -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org