Bug 20843 - For fixed fields requiring computer generated data, default value or plugin?
Summary: For fixed fields requiring computer generated data, default value or plugin?
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 17.05
Hardware: PC Windows
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-30 22:57 UTC by emjhet
Modified: 2020-11-30 21:45 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description emjhet 2018-05-30 22:57:52 UTC
As of 2018, the Koha Frameworks that were on our system (set up in late 2011) were designed for different types of records but the MARC fixed fields 000, 007, and 008 did not accurately code for those materials. I am making unique Frameworks that I hope will accurately code for specific materials. I have put a default value in the 000 (despite the need for a computer generated record length in the 00-04 character position) and the 007, and as of now have left the 008 blank.

I can not use a default value in the 008 because position 00-05 requires the date entered on file. I would, however, like to change the data currently in the 008 plugin. I simply do not find it helpful to have the default of position 06 be "b" (no dates given, B.C. date involved.) It is absolutely ridiculous for video recordings, yet not all my co-workers understand to edit this field. Is there a way to edit the plugin? Support told me that there can be only one plugin per field, but I was not sure based upon Bug 3013, Bug 14815, and Bug 19473.

Thank you.
Comment 1 Katrin Fischer 2020-04-05 01:56:31 UTC
I believe this would be better on the mailing list as it's more of a question than a bug report. For 008 and the year, see bug 24134.