[Bug 34198] New: Interface to define relational rules for MARC fields that use authorised values
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Bug ID: 34198 Summary: Interface to define relational rules for MARC fields that use authorised values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs@lists.koha-community.org Reporter: aleisha@catalyst.net.nz QA Contact: testopia@bugs.koha-community.org CC: m.de.rooy@rijksmuseum.nl We have a case where a set of MARC tags use authorised values i.e. 902$a, 902$b, 902$c, 902$d. Each of these subfields will use different authorised values. We'd like the authorised values displayed for 902$b to change depending on how 902$a is set. For example, if 902$a is set to a specific value, then the irrelevant options for 902$b should be hidden so they can't be selected. This might go on i.e. the values for 902$c are then dependent on the setting of 902$b. These rules would need to be editable by the library. -- 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=34198 Aleisha Amohia <aleisha@catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |aleisha@catalyst.net.nz |ity.org | Status|NEW |ASSIGNED -- 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=34198 Phil Ringnalda <phil@chetcolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |phil@chetcolibrary.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Aleisha Amohia <aleisha@catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|aleisha@catalyst.net.nz |koha-bugs@lists.koha-commun | |ity.org Status|ASSIGNED |NEW -- 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=34198 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |julian.maurice@biblibre.com |ity.org | CC| |julian.maurice@biblibre.com -- 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=34198 --- Comment #1 from Julian Maurice <julian.maurice@biblibre.com> --- Created attachment 189006 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189006&action=edit Bug 34198: Add parent-child relationship to authorised values The goal is to have some kind of hierarchy between different authorised value categories so that, when cataloging, selecting an authorised value in a parent authorised value category allow only a subset of values for child authorised value categories. This patch allows authorised value categories to have a parent category. When an authorised value category have a parent, its authorised values can have a parent authorised value in the parent category. An authorised value that have a parent can only be selected if: - its parent authorised value have been selected, or - no authorised value have been selected in the parent category An authorised value that have no parent can always be selected. This only works within the context of a MARC field. Selecting a value for a subfield will only alter subfields of the same field. A child category can also be a parent category. There is no limit to the depth of this hierarchy. Test plan: 1. Create an authorised value category TYPE with the following values: - Type 1 - Type 2 - Type 3 2. Create an authorised value category SUBTYPE (parent: TYPE) with the following values: - Subtype 1.1 (parent: Type 1) - Subtype 1.2 (parent: Type 1) - Subtype 2.1 (parent: Type 2) - Subtype 2.2 (parent: Type 2) - Subtype X.1 (no parent) - Subtype X.2 (no parent) 3. Create an authorised value category SUBSUBTYPE (parent: SUBTYPE) with the following values: - Subsubtype 1.1.1 (parent Subtype 1.1) - Subsubtype 2.2.1 (parent Subtype 2.2) - Subsubtype Y (no parent) 4. In the default MARC framework, create a 900 field. Within this field, - create a subfield 'a' linked to AV category TYPE, - create a subfield 'b' linked to AV category SUBTYPE, - create a subfield 'c' linked to AV category SUBSUBTYPE. 5. In the default MARC framework, in the item MARC field (952 or 995), edit or create 3 subfields to link them to these AV categories. Do the same for ACQ framework. 6. Do the same thing again for an authority type 7. Edit or create a bibliographic record. Go to field 900 and select a value for $a then open $b dropdown list to verify that values are disabled correctly. For instance, if $a = 'Type 1', 'Subtype 2.1' and 'Subtype 2.2' should be disabled. Select a value for $b and open $c dropdown list to verify that values are disabled correctly. Clone a field and verify that this works in the cloned field too. 8. Repeat step 7 for the item editor 9. Repeat step 7 for the item editor in acquisitions 10. Repeat step 7 for the authority editor -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 --- Comment #2 from Julian Maurice <julian.maurice@biblibre.com> --- Created attachment 189007 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189007&action=edit Bug 34198: [DO NOT PUSH] Update DBIC schema Patch from commit 09874bd -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 --- Comment #3 from Julian Maurice <julian.maurice@biblibre.com> --- Created attachment 189068 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189068&action=edit Bug 34198: Add parent-child relationship to authorised values The goal is to have some kind of hierarchy between different authorised value categories so that, when cataloging, selecting an authorised value in a parent authorised value category allow only a subset of values for child authorised value categories. This patch allows authorised value categories to have a parent category. When an authorised value category have a parent, its authorised values can have a parent authorised value in the parent category. An authorised value that have a parent can only be selected if: - its parent authorised value have been selected, or - no authorised value have been selected in the parent category An authorised value that have no parent can always be selected. This only works within the context of a MARC field. Selecting a value for a subfield will only alter subfields of the same field. A child category can also be a parent category. There is no limit to the depth of this hierarchy. Test plan: 1. Create an authorised value category TYPE with the following values: - Type 1 - Type 2 - Type 3 2. Create an authorised value category SUBTYPE (parent: TYPE) with the following values: - Subtype 1.1 (parent: Type 1) - Subtype 1.2 (parent: Type 1) - Subtype 2.1 (parent: Type 2) - Subtype 2.2 (parent: Type 2) - Subtype X.1 (no parent) - Subtype X.2 (no parent) 3. Create an authorised value category SUBSUBTYPE (parent: SUBTYPE) with the following values: - Subsubtype 1.1.1 (parent Subtype 1.1) - Subsubtype 2.2.1 (parent Subtype 2.2) - Subsubtype Y (no parent) 4. In the default MARC framework, create a 900 field. Within this field, - create a subfield 'a' linked to AV category TYPE, - create a subfield 'b' linked to AV category SUBTYPE, - create a subfield 'c' linked to AV category SUBSUBTYPE. 5. In the default MARC framework, in the item MARC field (952 or 995), edit or create 3 subfields to link them to these AV categories. Do the same for ACQ framework. 6. Do the same thing again for an authority type 7. Edit or create a bibliographic record. Go to field 900 and select a value for $a then open $b dropdown list to verify that values are disabled correctly. For instance, if $a = 'Type 1', 'Subtype 2.1' and 'Subtype 2.2' should be disabled. Select a value for $b and open $c dropdown list to verify that values are disabled correctly. Clone a field and verify that this works in the cloned field too. 8. Repeat step 7 for the item editor 9. Repeat step 7 for the item editor in acquisitions 10. Repeat step 7 for the authority editor -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 --- Comment #4 from Julian Maurice <julian.maurice@biblibre.com> --- Created attachment 189069 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189069&action=edit Bug 34198: [DO NOT PUSH] Update DBIC schema Patch from commit 0d0e207 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #189006|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #189007|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@openfifth.c | |o.uk, | |pedro.amorim@openfifth.co.u | |k -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 --- Comment #5 from Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> --- This looks interesting, noting for later. We should add support for this in the Vue framework components so it can be easily applied there generically too. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 --- Comment #6 from Julian Maurice <julian.maurice@biblibre.com> --- Created attachment 189182 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189182&action=edit Bug 34198: Use Koha::I18N as workaround to a bug in template translator When the template translator find a string to replace in an attribute (in this case, title) it rewrites the whole tag. And when the tag contain TT syntax, the result is really bad, for instance: <option $raw="$raw" %]="%]" [%="[%" attributes="attributes" disabled="disabled" title="Les pertes [...]" value="[%- aval | html -%]" |="|" >[%- mv.labels.$aval | html -%]</option> By having the attribute value translated by Koha::I18N we avoid that problem. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Angela Berrett <angela.berrett@familysearch.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |angela.berrett@familysearch | |.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #189068|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #189069|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #189182|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 --- Comment #7 from Julian Maurice <julian.maurice@biblibre.com> --- Created attachment 196360 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196360&action=edit Bug 34198: Add parent-child relationship to authorised values The goal is to have some kind of hierarchy between different authorised value categories so that, when cataloging, selecting an authorised value in a parent authorised value category allow only a subset of values for child authorised value categories. This patch allows authorised value categories to have a parent category. When an authorised value category have a parent, its authorised values can have a parent authorised value in the parent category. An authorised value that have a parent can only be selected if: - its parent authorised value have been selected, or - no authorised value have been selected in the parent category An authorised value that have no parent can always be selected. This only works within the context of a MARC field. Selecting a value for a subfield will only alter subfields of the same field. A child category can also be a parent category. There is no limit to the depth of this hierarchy. Test plan: 1. Create an authorised value category TYPE with the following values: - Type 1 - Type 2 - Type 3 2. Create an authorised value category SUBTYPE (parent: TYPE) with the following values: - Subtype 1.1 (parent: Type 1) - Subtype 1.2 (parent: Type 1) - Subtype 2.1 (parent: Type 2) - Subtype 2.2 (parent: Type 2) - Subtype X.1 (no parent) - Subtype X.2 (no parent) 3. Create an authorised value category SUBSUBTYPE (parent: SUBTYPE) with the following values: - Subsubtype 1.1.1 (parent Subtype 1.1) - Subsubtype 2.2.1 (parent Subtype 2.2) - Subsubtype Y (no parent) 4. In the default MARC framework, create a 900 field. Within this field, - create a subfield 'a' linked to AV category TYPE, - create a subfield 'b' linked to AV category SUBTYPE, - create a subfield 'c' linked to AV category SUBSUBTYPE. 5. In the default MARC framework, in the item MARC field (952 or 995), edit or create 3 subfields to link them to these AV categories. Do the same for ACQ framework. 6. Do the same thing again for an authority type 7. Edit or create a bibliographic record. Go to field 900 and select a value for $a then open $b dropdown list to verify that values are disabled correctly. For instance, if $a = 'Type 1', 'Subtype 2.1' and 'Subtype 2.2' should be disabled. Select a value for $b and open $c dropdown list to verify that values are disabled correctly. Clone a field and verify that this works in the cloned field too. 8. Repeat step 7 for the item editor 9. Repeat step 7 for the item editor in acquisitions 10. Repeat step 7 for the authority editor -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 --- Comment #8 from Julian Maurice <julian.maurice@biblibre.com> --- Created attachment 196361 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196361&action=edit Bug 34198: [DO NOT PUSH] Update DBIC schema Patch from commit 9a94ae3 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 --- Comment #9 from Julian Maurice <julian.maurice@biblibre.com> --- Created attachment 196362 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196362&action=edit Bug 34198: Use Koha::I18N as workaround to a bug in template translator When the template translator find a string to replace in an attribute (in this case, title) it rewrites the whole tag. And when the tag contain TT syntax, the result is really bad, for instance: <option $raw="$raw" %]="%]" [%="[%" attributes="attributes" disabled="disabled" title="Les pertes [...]" value="[%- aval | html -%]" |="|" >[%- mv.labels.$aval | html -%]</option> By having the attribute value translated by Koha::I18N we avoid that problem. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Julian Maurice <julian.maurice@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34198 Chris Mathevet <chris.mathevet@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Patch doesn't apply CC| |chris.mathevet@inLibro.com -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org