Bug 2901

Summary: Unable to hide RLIN subfields in a framework
Product: Koha Reporter: Doug Dearden <dearden>
Component: CatalogingAssignee: Galen Charlton <gmcharlt>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: dcook, katrin.fischer
Version: rel_3_0   
Hardware: PC   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Chris Cormack 2010-05-21 00:57:45 UTC


---- Reported by dearden@sarsf.org 2009-01-07 13:53:24 ----

When editing a subfield in the staff client at: Home › Administration › MARC Frameworks › (name)Framework Structure › Tag 100 Subfield Structure , setting tag 9 to -6 does not hide the tag when creating a new biblio or when editing one using the particular framework.  To reproduce the problem, in any framework edit the Tag 100 subfield 9, change the "hidden" attribute under additional constraints to -6 .  Catalog a new biblio using the framework you changed, and the Tag 100 subfield 9 will still display.  This is also true for tags 110, 111, 130, 440, 600, 610, 611, 630, 650, 651, 690, 691, 696, 697, 698, 699, 700, 710, 711, 730, 796, 797, 798, 799, 800, 810, 811, 830, 896, 897, 898, 899 - subfield 9.  All of these have RLIN in the description.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:57 UTC  ---

This bug was previously known as _bug_ 2901 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2901

Unknown operating system Linux - Debian. Setting to default OS "All".
Actual time not defined. Setting to 0.0

Comment 1 David Cook 2014-06-25 03:32:01 UTC
I noticed this recently as well...still seems to be an issue. 

You can collapse it...but it's impossible to hide it in the editor...
Comment 2 Katrin Fischer 2016-09-08 05:49:03 UTC
I think this is probably a security measure: it will hide properly when you remove the thesaurus from the $a of those fields. If you could hide $9 and tried to link an authority, the authnumber wouldn't get saved anywhere = broken linking. So as long as the link is there, the $9 won't go away to keep this from happening.

WONTFIX?