[FOLIO-466] Discuss what is needed for circulation from the inventory modules Created: 07/Feb/17 Updated: 12/Nov/18 Resolved: 16/Feb/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Marc Johnson | Assignee: | Marc Johnson |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint8 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | |||||||||||||||||||||
| Description |
|
Discuss what else is needed to support initial circulation of physical items. Might include discussion of circulation activities / modules. |
| Comments |
| Comment by Marc Johnson [ 09/Feb/17 ] |
|
I’ve taken a look at the current design prototypes (based upon the link in
LIBAPP-20 Based upon that, I believe the inventory modules need to support: Getting the details of an item (
Is there anything else that the inventory modules need to be able to do? And some follow up questions which I need help with: LIBAPP-26 and LIBAPP-77 mentions brief details of the item, what fields are expected for that? Does it go beyond title, barcode, material type, location and status? The UI prototype (https://share.proto.io/D7XIAW/) has what looks like an author, below the title in the top right corner. Do we need to model authors/creators/contributors? The discuss post refers to the idea of customising the metadata that can be viewed on the scan page using the “More Options…” button, is this out of scope for the current work? At the moment, all item states are all lower case in the text field, does this need changing to capitalisation? Hugs, Marc |
| Comment by Cate Boerema (Inactive) [ 09/Feb/17 ] |
|
Hi Marc. We don't yet have details on what item data should display in Check-out. I think we should just use the item data we have and refine later when we have the details. So, to start out with, let's do: Title, Barcode, Material Type and Location. Status would also be nice so you could see when you "scan" the barcode (type it in for now) whether the item is currently checked in or out. In terms of capitalization, Filip would like everything (labels, menu values etc) to be in title case. Thanks for asking! |
| Comment by Marc Johnson [ 09/Feb/17 ] |
|
Thanks Cate, All of those fields are available, so that is cool. I will change the capitalisation of the examples I have. As the fields are purely text at the moment, the modules won't validate the casing. Is there anything that I've missed? Hugs, Marc |
| Comment by Mike Taylor [ 09/Feb/17 ] |
|
I added D, Wayne and Charles, as they have the most library experience, I think, and I want their thoughts on what I am about to say ... Which is ...
I am no librarian, but it seems bizarre to me that anyone would accept an inventory-related application that doesn't show at least author and probably date. Otherwise, how are you going to tell which of the five books titled The Last Man Who Knew Everything you're dealing with? Library folks, what's your take? |
| Comment by D Ellen Bonner [ 09/Feb/17 ] |
|
I'm not sure what you mean by "inventory modules". To me that smacks of reporting... is that not the intention? (Guess I need to read more of these issues) If it's reporting, yeah--you need almost all bib details. If it's really just circ, meh, people at the desk won't look beyond the title for verification--if that. Title display assumes the barcode has already brought up the display. Edit: Display of status isn't even required. Humans won't be acting on that. The system should present an error message upon bcode scanning if the status is a "non-circulating" value (lost, in house use only, etc.). |
| Comment by Cate Boerema (Inactive) [ 09/Feb/17 ] |
|
Hi D. Inventory is the internal name we are currently using for what Filip calls "Catalog" in the prototype. It is not reporting. At this point, we are just trying to "rough in" the check out functionality. We don't have detailed designs or specifications for what data elements should display on the screen so we just want to use what we have. We will update these screens later when the detailed designs become available. See LIBAPP-103 for the work item I have in for Filip. |
| Comment by Marc Johnson [ 09/Feb/17 ] |
|
As a quick aside on the history of the name inventory. We had a number of discussions late last year and catalog was seen (in those) as an name that carried too many other considerations, mostly around discovery, OPACs and the act of cataloging. And we wanted to emphasise that this only represented physical items at the moment and not a unified view between physical and electronic resources. Hugs, Marc |
| Comment by D Ellen Bonner [ 09/Feb/17 ] |
|
Thanks Marc and Cate. All very sensible. I've much catch-up to do still. |
| Comment by Marc Johnson [ 16/Feb/17 ] |
|
Cate Boerema and Jakub Skoczen Do you think we can close this? Hugs, Marc |
| Comment by Cate Boerema (Inactive) [ 16/Feb/17 ] |
|
From a requirements perspective, I think we know what we need to support our very first pass at this (
|
| Comment by Marc Johnson [ 16/Feb/17 ] |
|
Thanks Cate Boerema I'll close this assuming you believe the extraction of inventory module requirements that I did above covers
Hugs, Marc |