Summary: | Editing MARC Authority Subfield Structure - Librarian Text is Mandatory | ||
---|---|---|---|
Product: | Koha | Reporter: | Colin Campbell <colin.campbell> |
Component: | MARC Authority data support | Assignee: | Galen Charlton <gmcharlt> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P5 - low | CC: | chris, katrin.fischer |
Version: | Main | ||
Hardware: | All | ||
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 01:13:23 UTC
http://lists.koha-community.org/pipermail/koha-patches/2009-September/010249.html Patch no longer applies. Is this still an issue? Still an issue. Open to question whether we should rework the patch or make it obvious to the user that the field is mandatory which as originally pointed out is not documented anywhere other than in the code. Needs new patch or reworked patch Resetting to ASSIGNED since a new patch is required. Setting this to "New" since a new patch doesn't seem to be forthcoming. The problem still exists with both authority subfield structure and biblio subfield structure -- If you submit a new subfield without including librarian text the process fails silently. There's a good reason: The "New" form fields are part of a big form which includes all the form fields for existing data. It needs to be possible to submit empty fields and thereby ignore the "New" part of the form. It (apparently) needs to also be possible to create a new subfield *without* a subfield code, so librarian text ends up being the field which is consulted to determine whether data in the "New" form is added. Still valid. Can we not just mark the field as required the usual way? (In reply to Katrin Fischer from comment #6) > Still valid. Can we not just mark the field as required the usual way? There is a catch here. We want the subfield code and the staff interface description to be required, but the form for a new subfield is always loaded. We only want it to trigger when something has been entered indicating a new field is to be added. I didn't manage to do that. |