Inventory
(UXPROD-785)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q4 2018 | Parent: | Inventory |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Charlotte Whitt |
| Resolution: | Done | Votes: | 0 |
| Labels: | inventory, metadatamanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| Epic Link: | Inventory | ||||||||||||||||
| Analysis Estimate: | Medium < 5 days | ||||||||||||||||
| Analysis Estimator: | Charlotte Whitt | ||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||
| Front End Estimator: | Niels Erik Nielsen | ||||||||||||||||
| Front-End Confidence factor: | Medium | ||||||||||||||||
| Back End Estimate: | Large < 10 days | ||||||||||||||||
| Back End Estimator: | Niels Erik Nielsen | ||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||
| Rank: BNCF (MVP Feb 2020): | R1 | ||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||
| Description |
|
Suppress Holdings, title and item records from display. Only catalogers, circulation staff and others with the given permission can view and edit. Q3 2018: Q4 2018: Filter records by Suppress in discovery and Staff suppress has been deprioritize by Chalmers -
Out of scope: Definition of the view and edit permission on Suppressed records in Inventory |
| Comments |
| Comment by Hkaplanian [ 19/Feb/18 ] |
|
Note that this should be a very simple flag in the record as the external patron discovery service will need to parse this and decide to make it available to users in search results. Since FOLIO focuses on the librarian, not much is needed here for v1 |
| Comment by Charlotte Whitt [ 21/Jun/18 ] |
|
In the batch loader group on Wednesday (6/20/2018), they talked about libraries suppressing or inactivating (or maybe deleting) instances/holdings/items for materials that are no longer owned. One thing everyone agreed was that if something is inactive or suppressed, there ought to be some visual indication in the results list, and that should also be a filter option (like FOLIO has for active/inactive users). Gary Branch mentioned that Voyager colors suppressed records a different color in the results set and puts the record ID in parentheses, so that you have visual cues, e.g. greying out the record, or italics, or a different color perhaps. It would also be useful if you had multiple holdings or multiple items associated with an instance, but one item was now lost/inactive. So to sum up:
|
| Comment by Filip Jakobsen [ 21/Jun/18 ] |
|
Charlotte Whitt, I think the best way to support this in line with the rest of the system, would be to allow users who want to see this, to "toggle on" a column that will contain an icon and a label describing if the record is suppressed or not. This is also what happens for active/inactive. As Hkaplanian points out, since the main focus is staff currently, we might want to have it turned off by default, but provide the ability to toggle it on. I don't think we should build anything custom tailored for "supressed"/"not supressed", but rather aim to let users choose what information (any information at all) they want to see in the results list. This will make for a robust system that will work for many types of institutions, job functions and languages. I defer to Hkaplanian and Cate Boerema on the planning, but when we get to this being a priority, I strongly feel that the above approach is the right one, considering the full user experience of the system. Let me know if you have any questions about this. |
| Comment by Cate Boerema (Inactive) [ 05/Dec/18 ] |
|
Removing Q1 2019 fix version due to limited capacity in Q1 2019. |
| Comment by Charlotte Whitt [ 05/Dec/18 ] |
|
Hi @cate, this is implemented in the back end and in the UI for Instance and Holdings. It's an UI-only task for implementing it in the Item record. |
| Comment by Charlotte Whitt [ 03/Jan/19 ] |
|
Hi Cate Boerema, this feature is implemented in the Instance, Holdings and Item records - except for |
| Comment by Erin Nettifee [ 22/Apr/19 ] |
|
Duke would anticipate a need for circulation staff to see item-level withdrawn records, in the case that a withdrawn item reappears (which happens.) It's unclear from these notes if that is accounted for in the permissions discussion - can someone clarify? Thank you. |
| Comment by Charlotte Whitt [ 23/Apr/19 ] |
|
Hi Erin Nettifee - Thanks for your comments. This story is not about permission settings. I have updated the title of this story, while it was misleading. |