Skip FOLIO Project Navigation

🗄 Items, UX iteration 2

ux-iteration
english
uxi-items
uxi-2-items

#1

Please note: This video presents our optimal vision for this feature in FOLIO; What you see in this prototype is what we are working towards in the long run, and might not all be present in the first, developed version. Please help us improve it — share your questions, constructive feedback and ideas in the comments below.


:file_cabinet: Inventory, UX iteration 1, English
#2

This is clearly designed for cataloging/acquisitions, but circulation uses item records in pretty specific ways, so lots of questions . . .

  • How can we see an items current availability / status? and how can we manually alter that if required (e.g. mark something missing or damaged)?
  • How do we see current outstanding requests? and how/where do we manipulate the requests (e.g. reorder them or move them to an alternate copy)?
  • How can we see the item’s circ history (e.g. last check out, return) and where that happened and who the operator was?
  • History of item changes (location changes, manual status changes, etc.)? and where these changes happened and which operator performed them?
  • Identify other copies of the same item and their availability and status of requests.
    – In an ideal world, how do we find related copies (other editions or formats)?

and again - where is the fielded search?


#3

@andrealoigman Thank you for your comments and questions!

- How can we see an items current availability / status? and how can we manually alter that if required (e.g. mark something missing or damaged)?
The status discussion is hugely influential on this app, but also affects a lot of other apps. So it is not something that can be solved simply by changing this layout. However I feel it would be beneficial to the discussion if we could showcase it in this app’s UX prototype, so we will try to incorporate that in the next UX iteration. Thanks for bringing it up!

- How do we see current outstanding requests? and how/where do we manipulate the requests (e.g. reorder them or move them to an alternate copy)?
Good question! How do you think it would make sense to see them?

- How can we see the item’s circ history (e.g. last check out, return) and where that happened and who the operator was?
Good question! How do you think it would make sense to see them?

- History of item changes (location changes, manual status changes, etc.)? and where these changes happened and which operator performed them?
We have been conceptually talking about doing a “change tracker” that could be pulled up in any context to show any and all changes to a record as a whole or a specific field. Would that cover what you ask about here, or are you thinking of something more specific or different?

- Identify other copies of the same item and their availability and status of requests.
One could open the related Bib record and from there see all related items. Would you want to see all related items from the item record itself?

– In an ideal world, how do we find related copies (other editions or formats)?
Click on the relevant item under “Related bib” and from there discover “related items”

and again - where is the fielded search?
It is not evident in this prototype yet. It will exist in the search+filter side bar, with the ability to go to an “advanced” mode to do a boolean/fielded/advanced search. We will try to include this in the next UX iteration of this prototype. Thanks!


#4

We’d need to see them on the item record of course, but it’s a bit more complicated than that. Sometimes the reason that we’re manipulating requests is because multiple requests have been attached to a single item when we have multiple copies. In those cases we’re trying to spread the requests more evenly across the all of the copies in the system. So we’d also need to be able to find a way to see that.
In addition, some libraries will purchase additional copies if they see x number of concurrent requests for a single item/title. So there needs to be a way to see requests attached to a bib in addition to just those attached to an item.
This will need to be resolved to permit title level requests anyway. I know title level requests aren’t set for the first iteration, but it is something most other systems offer, so we will need to provide it.

How are you envisioning the ‘change tracker’ working? Could this be resolved with a circ specific variation of that?

Ideally, yes. We would want to see, or at least easily get to, other copies from the item record. If we couldn’t see it in the item record itself it would be good to at least have an indication that there are other copies.


#5

Having the notes function and the ability to tag colleagues is useful as records may have to change hands while being processed or updated. Where is the function for notes that display to the public? Example: “To access full functionality, the user must create an account with their xxx@xxxx.edu address.”


#6