Bug 24843 - Allow change of framework via batch record modification
Summary: Allow change of framework via batch record modification
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-10 21:02 UTC by Andrew Fuerste-Henry
Modified: 2024-09-09 17:34 UTC (History)
7 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2020-03-10 21:02:47 UTC 
Koha should give users some method to change the framework of multiple records at once. Batch record modification cannot currently do this.
Comment 1 Holly 2023-02-24 10:38:09 UTC 

*** This bug has been marked as a duplicate of bug 15869 ***
Comment 2 Andrew Fuerste-Henry 2023-02-24 13:17:08 UTC 
This is not a duplicate of bug 15869. That bug is about changing frameworks on batch import. My intent here is for a way to change the frameworks via batch record modification, for changes that don't have anything to do with importing new records. The feature introduced in 15869 would allow one to batch edit frameworks by exporting a batch and then reimporting, matching, and overlaying without changing anything except the framework. It seems worthwhile to have a simpler option.
Comment 3 Miranda Nero 2023-10-24 21:49:14 UTC 
We are using an API to overlay records and cannot update the framework in this process as if we were staging the records. The majority of our records are overlaid using the API, so being able to update the framework on our own with batch modification would be a huge time saver.
Comment 4 Mykle 2024-09-09 17:34:03 UTC 
Agreed. This might be manageable by mapping an unused MARC 9xx field to the framework codes field-- but I imagine some others might know better whether this could actually work that way.

If that doesn't work-- there may need a coding update to make such a feature possible.