upgrading to 2.5+ can break copy templates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
The introduction of floating groups in Evergreen 2.5 changed the type of the asset.copy.floating column from a Boolean to an integer. However, holdings maintenance copy templates (i.e., the staff_client.
The effect that if one attempts to save an item record in holdings maintenance after applying such a copy template, the save will fail.
There are various ways to fix this:
[1] Add special logic to holdings editor to detect this and either ignore it or give the user a chance to update the copy template.
[2] During upgrade, munge existing copy templates. One possibility: if the template sets floating to false, remove that field; if it sets it to true, change it to set it to "1", matching the default floating group that gets creating during upgrade.
Evergreen 2.5 and later
Changed in evergreen: | |
status: | New → Won't Fix |
Another possible solution would be to move the floating group functionality out to a new field or table, turn asset.copy.floating back into a bool, and have the checkin code look at the new field. FWIW, this would be my preferred solution, as it would address other potential issues such as reports that expect a.c.floating to be a bool.