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.
Sounds useful for several identifier fields too (like persistent identifiers).
+1 Excellent idea for an enhancement.
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.