Resource Access View of Inventory Data
(UXPROD-1877)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Resource Access View of Inventory Data |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Ann-Marie Breaux (Inactive) | Assignee: | Charlotte Whitt |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | chalmers, chalmers_debut_followup, inventory, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| Potential Workaround: | Cate Boerema: I know it's painful, but the workaround is to use Inventory as-is. We may be able to make some easy changes to the Inventory layout to make this easier for RA folks. | ||||||||||||||||
| Epic Link: | Resource Access View of Inventory Data | ||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||
| PO Rank: | 48 | ||||||||||||||||
| PO Ranking Note: | 2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
Leaving PO rank as equal to calculated total rank. Workaround is to use Inventory. |
||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R2 | ||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||||||
| Description |
|
Resource access staff need to work with inventory data, but their use cases differ from that of catalogers, as their work revolves around circulation of items (copies), while catalogers' work centers on describing instances (bibliographic records). Circulation staff want to do things like:
The focus of this feature is the development of a view of inventory data designed for RA use. This may take the form of a view within the Inventory app or, perhaps, another app entirely. A separate app may actually be preferable in that it would support clean permissions for circ staff and does not extend Inventory (which is already a very large app). This feature to be discussed with the RA-SIG.
NOTES from Chalmers Notes from Ann-Marie based (5/23/2019) on conversations with Chalmers: Purpose is to provide a view of the Inventory records to better support non-catalogers use As a staff person |
| Comments |
| Comment by Charlotte Whitt [ 23/May/19 ] |
|
Hi Ann-Marie Breaux - This issue is already addressed in the GAPS analysis 2019 by Duke, and will need further discussion. This probably needs to be solved as a UI customization issue, while it will be difficult to make a consistent view of all record types in Inventory (Instance, Holidings, Item, Container) which both suit the purpose of catalogers and non-catalogers. I therefore don't think this is a UIIN story, but rather a new UI Customization feature. |
| Comment by Lisa Sjögren [ 24/May/19 ] |
|
This is a high priority for us, but we are willing to wait a few months for a good and well thought through solution. |
| Comment by Khalilah Gambrell [ 24/May/19 ] |
|
Hey all, I am unsure UI customization will fully address the reported issues. There are some UI design issues (e.g. title name appears 3 times on the record) that must be addressed. Hierarchial layout design may help too. Also, I think it would be helpful to have folks do a quick card sorting exercise to see field and accordion display priority. We may see agreement across catalogers and non-catalogers. Also is there a way to use permissions to address some of these issues? |
| Comment by Charlotte Whitt [ 27/May/19 ] |
|
Hey @khalilah - The resource title, is only mentioned one time: Let me illustrated: |
| Comment by Kristin Martin [ 09/Jul/19 ] |
|
From Chicago: This should not be implemented as a fixed change to the display. The display needs to be customizable so that they users with different needs have the information that they need at the top of the screen. |
| Comment by Kristin Martin [ 11/Jul/19 ] |
|
This appears to be the same thing as
|
| Comment by Cate Boerema (Inactive) [ 12/Jul/19 ] |
|
Thanks Kristin Martin, I think this is essentially the same as
To solve the problem for getting RA a view that's more useful to them, a "fixed" view/app will be easier than creating customizable FOLIO forms. I think we should consider customizable forms a separate feature or features and we already have several items in the backlog along those lines:
|
| Comment by Cate Boerema (Inactive) [ 17/Jul/19 ] |
|
Copying a comment from Felix Hemme on
A lot of information is visible at a glance, without having to scroll. Hope this is helpful. If needed, we can update the screenshots from german to english. |
| Comment by Erin Nettifee [ 17/Jul/19 ] |
|
Duke would mark 1742 as a go-live. |
| Comment by Erin Nettifee [ 29/Jul/19 ] |
|
I note the workaround here - is this feature being considered MVP, or are the Inventory redesign Jiras being pursued as MVP? |
| Comment by Ann-Marie Breaux (Inactive) [ 29/Jul/19 ] |
|
Hi Erin Nettifee This feature not currently labeled as po-mvp, so not considered MVP at the moment. I'm not sure about the other Inventory redesign features. |
| Comment by Jacquie Samples [ 23/Sep/20 ] |
|
One point about the feature list is that it is needed far beyond RA functions: Everyone using FOLIO need to be able to "Quickly access items by barcode to view/edit details." Using the results of a search by barcode should result in a display of item data. Or, a message indicating that the barcode searched for is not extant in FOLIO. |
| Comment by Lisa Sjögren [ 24/Sep/20 ] |
|
Some of the points brought up by Chalmers mention in this issue, such as displaying item and holdings at the top of the instance are already implemented (and much appreciated). Maybe the description needs to be updated to better reflect what has been done/remains. As I see it, in most cases when you search for a barcode you'd want to see the instance-with--all-holdings-and-items view in the third pane, but with the matching item clearly highlighted. From that perspective, I think the https://ux.folio.org/docs/prototypes/use-apps/inventory/ redesign looks extremely promising, so am very curious about what the plans/time frame for implementing that is. |
| Comment by Charlotte Whitt [ 24/Sep/20 ] |
|
Hi Lisa Sjögren - thanks for adding your comments on this feature Please notice that I have story in for clearly highlight of the matching item record: Cate Boerema the Stripes Force team has done the ground work for implementation of the highlight functionality; see:
|
| Comment by Cate Boerema (Inactive) [ 24/Sep/20 ] |
|
Nice, Charlotte Whitt. Let's groom it tomorrow. |
| Comment by Charlotte Whitt [ 01/Feb/22 ] |
|
This work is substituted by the new work on Hierarchical Display of the Inventory Result list -
Barcode is implemented as a drop-down menu. |