Owning lib of asset.copy_location not visible in Item Attributes Editor UI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.6 |
Fix Released
|
Undecided
|
Unassigned | ||
2.7 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The owning library of the copy location of an item is not visible in the Item Attributes Editor. This leads to misassignment of copy locations with no way of knowing that a cataloger is doing so. This occurs in library systems that apply a consistent copy location naming scheme across all member units (e.g., all CHRL libraries use the name "ADULT" for a copy location in each of their libraries) and where items are cataloged centrally. A cataloger will set up an Item Attributes Editor template which applies an "ADULT" copy location for one of the system's branches, then re-use that template for other branches' items, not realizing that the "ADULT" location she/he is using belongs to a specific branch.
Workarounds would be to have catalogers manage a large set of templates that factor in copy location owning lib (which is actually quite unwieldy, workflow-wise) or to run a periodic SQL-level cleanup that tags asset.copy objects with the correct location.
What would be most desirable is if the system would know to set the correct copy location by name (which would allow catalogers to retain existing templates - recreating templates would be a very burdensome task). Basically, Evergreen should "know" that catalogers want the asset.copy.circ_lib to be the same as asset.copy_
Thanks,
Chris
Changed in evergreen: | |
status: | Incomplete → New |
Changed in evergreen: | |
assignee: | Jason Stephenson (jstephenson) → Thomas Berezansky (tsbere) |
Changed in evergreen: | |
milestone: | none → 2.next |
importance: | Undecided → Medium |
Changed in evergreen: | |
assignee: | Thomas Berezansky (tsbere) → nobody |
tags: | added: signedoff |
Changed in evergreen: | |
status: | In Progress → Confirmed |
Changed in evergreen: | |
milestone: | 2.7.2 → 2.next |
Please supply at minimum, what version of Evergreen you are on.