Bug 26071 - Allow to configure fields not to be copied when using "Edit as new (duplicate)" in cataloging
Summary: Allow to configure fields not to be copied when using "Edit as new (duplicate...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-27 13:19 UTC by Katrin Fischer
Modified: 2024-01-15 06:55 UTC (History)
4 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 Katrin Fischer 2020-07-27 13:19:28 UTC
When duplicating a record for example for cataloging a newer edition an exact duplicate of the record is created. In some cases it would be nice if you could define fields that should be emptied out when duplicating, similar to what we can do when duplicating subscriptions (SubscriptionDuplicateDroppedInput). 

The use case here would be to drop 001 when copying, so no duplicate IDs are added to the catalog. The field is marked mandatory so then the cataloger will be reminded to fill it in.
Comment 1 Marcel de Rooy 2020-07-27 13:29:57 UTC
Sounds useful for several identifier fields too (like persistent identifiers).
Comment 2 George Williams (NEKLS) 2020-07-27 18:06:29 UTC
+1

Excellent idea for an enhancement.
Comment 3 Katrin Fischer 2020-07-27 19:25:41 UTC
Glad to see there is some interest in this! I think there would be multiple use cases, as Marcel points out, I just wanted to give an example that has come up at one of our libraries.