Copy locations table should have a 'deleted' flag
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Evergreen 2.3.7
When a copy location is no longer in use, it is preferable for a library to remove it from their list of locations so users don't see the defunct location and potentially choose it in error. Users with permission are able to delete copy locations in the copy locations editor. When a copy location is deleted successfully, the row is removed from asset.copy_
This presents several problems:
If items are coded with the location, the deletion fails. Even if the items have been deleted, it is not possible to delete the location.
The asset.copy_
If there were a deleted flag in the copy location table that was set to TRUE when the location was deleted, these relationships would be preserved.
The deleted flag in the copy location table should cause the location not to display in the library's list of locations. Checks should be made against undeleted items, before the deleted flag can be set to TRUE. Ideally, checks should also be made against saved copy templates.
Changed in evergreen: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in evergreen: | |
assignee: | nobody → Jason Boyer (jboyer) |
Changed in evergreen: | |
assignee: | Jason Boyer (jboyer) → nobody |
tags: | added: pullrequest |
Changed in evergreen: | |
assignee: | nobody → Michele Morgan (mmorgan) |
Changed in evergreen: | |
assignee: | nobody → Michele Morgan (mmorgan) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
This is related to #979302.
Shelving locations used by only deleted items should be allowed to be deleted, or marked deleted. This is causing lots of confusion and trouble. The deleted items are invisible on the client. Staff can't do anything with them.