http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4888 Marjorie Barry-Vila <marjorie.barry-vila@ccsr.qc.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marjorie.barry-vila@ccsr.qc | |.ca --- Comment #29 from Marjorie Barry-Vila <marjorie.barry-vila@ccsr.qc.ca> --- (In reply to Mirko Tietgen from comment #27)
Created attachment 14837 [details] [review] Bug 4888 - pre-set of field indicators value
Preload on database of the set of field indicators value as defined by http://www.loc.gov/marc/bibliographic/ecbdhome.html. New sql files in marc21/mandatory to create and populate the indicators tables with the sets of values for the Default framework/authtype. Each framework/authtype will be able to have its own copy to allow individual modification of indicators value. When editing the framework/authtype exists the possibility of cloning the indicators set from an existing framework/authtype populated with indicators.
Modification of the intranet administration-Marc Frameworks/Authority MARC Framework to clone on creation from another framework and to delete set of indicators from a framework. Management (add/modify/delete) for indicators of the fields in the Framework Structure.
Modification of the intranet cataloguing addbiblio / authorities authorities to enable a plugin to see the defined indicators value for a specific framework, and to check validity of indicators value.
Two new system preferences: CheckValueIndicators for checking the value of the indicators when cataloguing a biblio record; DisplayPluginValueIndicators: to enable the plugin at addbiblio to see indicators value and to check too.
Rebased to master 01/2013
Bug 4888 - rebase follow-up
Fixing errors I made during rebase
Bug 4888 follow-up: rebase errors 2
Another rebase error fixed
Bug 4888 follow-up: fix authorities.tt
Fixed an error in authorities.tt
Bug 4888 follow-up
fixed auth_tag_structure.tt
Hi, Do you always work on this patch? Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.