Inventory
(UXPROD-785)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q2 2020 | Parent: | Inventory |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Charlotte Whitt | Assignee: | Charlotte Whitt |
| Resolution: | Done | Votes: | 0 |
| Labels: | cap-mvp, chalmers, chalmers_debut_followup, inventory, metadatamanagement, po-mvp, q4-2019-at-risk, split | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Inventory | ||||||||||||||||||||||||||||||||||||||||
| Analysis Estimate: | Very Small (VS) < 1day | ||||||||||||||||||||||||||||||||||||||||
| Analysis Estimator: | Charlotte Whitt | ||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Niels Erik Nielsen | ||||||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | Medium | ||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Jakub Skoczen | ||||||||||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Outstanding questions:
* Implemented as a search index or as a persisted field containing the normalized version of the ISBN number? |
||||||||||||||||||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 110 | ||||||||||||||||||||||||||||||||||||||||
| PO Ranking Note: | CW: Aligned PO rank with Calculated Total rank | ||||||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
Goal/Purpose: Library staff need to search Inventory by ISBN both with or without dashes and/or spaces and retrieve ISBN entered either with or without dashes/spaces. Use cases: Staff member scans UPC code on back cover to enter ISBN (contains dashes) – this should retrieve the record whether the string is entered with or without dashes. Staff member enters digits only to search--this should retrieve the record whether the string is entered with or without dashes. FOLIO displays the ISBN number in the Instance record. The ISBN number is one of the main elements when ordering a resource, match of incoming records and more. The ISBN element is in Inventory defined as a resource identifier number set by a resource identifier type labelled ISBN/Invalid ISBN in a reference table in the Settings > Inventory > Instance. Documentation: Out of scope for MVP: ISBN utility code library: https://github.com/folio-org/folio-isbn-util
Some examples Charlotte Whitt This is feedback from Chalmers. This is high priority for them. Please review and determine next step (finalize into a story, mark as will not implement, need more info, delete, etc.). The label chalmers_debut_followup helps us keep these issues all findable as a group. |
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 17/Jul/19 ] |
|
HI Charlotte Whitt I noticed this doesn't have a Q3 label. Do you think it will get handled in Q3 2019? Not sure how it ranks against the many other Inventory features. We're also working on it from the Orders side. Relevant UIOR story is linked. |
| Comment by Charlotte Whitt [ 17/Jul/19 ] |
|
Hi Ann-Marie Breaux - that would be a question for Cate Boerema? This is such an everyday (general) search, and something almost all staff are doing on a daily basis. So it definitely needs to be in if not before, then for Q4 2019. |
| Comment by Cate Boerema (Inactive) [ 17/Jul/19 ] |
|
Well, Charlotte Whitt, you had previously put UXPROD-1420 at the top of your Q3 priorities, but I think once we break that down, we'll see it's not all really needed for mvp. We should then take a look at what other Inventory features might be able to be pulled in. The calculated rank on this is relatively low, but that's clearly because not all institutions have ranked it (all who have put it at go-live). Charlotte this might be one you bump up with your PO rankings and tag with po-mvp (if you think that's appropriate) |
| Comment by Ann-Marie Breaux (Inactive) [ 17/Jul/19 ] |
|
Charlotte Whitt Cate Boerema FWIW - this is definitely a Chalmers pain point. They want to be able to scan a UPC on a book and use the ISBN of the UPC to execute a search in Orders and/or Inventory. There's a separate story for Orders (
|
| Comment by Charlotte Whitt [ 17/Jul/19 ] |
|
I have already assigned `PO-mvp` |
| Comment by Marie Widigson [ 16/Sep/19 ] |
|
Still very high priority for us at Chalmers! |
| Comment by Cate Boerema (Inactive) [ 19/Sep/19 ] |
|
Charlotte Whitt and Ann-Marie Breaux this is cap-mvp, thus Q4 work for Core Functional. Will it be dev-ready soon? |
| Comment by Ann-Marie Breaux (Inactive) [ 19/Sep/19 ] |
|
Cate Boerema we're getting all our ducks in a row this week over in Orders, and then I think we will be able to copy that work for Inventory, so yes, I think this can be dev ready next week cc: Charlotte Whitt |
| Comment by Ann-Marie Breaux (Inactive) [ 30/Sep/19 ] |
|
Charlotte Whitt and Cate Boerema Here's the current ISBN situation in Inventory, and what we're doing in Orders to make this work. If it woudl be helpful to talk through any of this or look at it together in FOLIO, please let me know. Inventory situation:
Order situation
So that's how we're handling it in Orders, and we'll probably implement similar handling in other acq apps that have ISBN searches. It'll likely be easier since most of the other apps' data flows from the POL, so all of the work we've done to clean up the ISBNs in the POL will help with the downstream searches. cc: ing Craig McNally and Dennis Bridges in case they have anything to add. |
| Comment by Marc Johnson [ 07/Oct/19 ] |
Where is this constraint enforced, in the reference UI, mod-orders and/or mod-orders-storage?
Does this mean that it is only possible to search for an entire ISBN-13 in acquisitions? How does the orders UI know that what has been entered into the POL/Product ID/ISBN search is intended to be a ISBN number and not a product ID? |
| Comment by Marc Johnson [ 07/Oct/19 ] |
Should the reference inventory UI or mod-inventory only allow valid ISBN's to be provided for an identifier with the type ISBN (rather than Invalid ISBN)?
Does inventory have a separate field for the qualification information? If not, how are we intending for the qualifier to be ignored? (I find the qualifier examples a little odd, as I think of ebooks and hardcover books etc as being separate instances) |
| Comment by Theodor Tolstoy (One-Group.se) [ 08/Oct/19 ] |
|
[Comment removed] |
| Comment by Charlotte Whitt [ 14/Oct/19 ] |
|
Notes from meeting with Ann-Marie Breaux Craig McNally lew235 Marc Johnson Charlotte Whitt - 10/14/2019
|
| Comment by Ann-Marie Breaux (Inactive) [ 14/Oct/19 ] |
|
Hi Charlotte Whitt One small correction on this line:
13 digit ISBNs will never have an X check digit. When the ISBN expansion happened, they also revised the check algorithm, so that X would no longer be assigned, only digits. The only place you'll see an X is on the end of a 10-digit ISBN. Also, in case it's useful, here's a tool from Bowker (the US ISBN agency) that allows for quick translation back and forth between 10s and 13s: https://www.isbn.org/ISBN_converter |
| Comment by Ann-Marie Breaux (Inactive) [ 15/Oct/19 ] |
|
Theodor Tolstoy (One-Group.se)'s comments from last week, which I asked him to remove until after we got over some of the other fires: IMHO, In order for FOLIO to work long-term, you need to be able to trust Inventory identifiers to be exactly that and not strings formatted in a way that is imposed by MARC21. A valid ISBN should be an ISBN that other modules can trust right out of the box (the box being inventory). Otherwise, every single module that wants to interact with Inventory needs to setup a similar logic and validation for their identifiers as mod-orders. And what if the source of the data has another logic when populating Inventory ? Will not having MARC-import formatted identifiers break the contract? Perhaps another importer puts the qualifier in front of the ISBN instead? Then every module need to be rewritten to accommodate that. If the ISBN does not validate, it could be put in as an Invalid ISBN and search would not be broken. Perhaps, what we really should do is to introduce the GTIN Identifier type? The GTIN should always be the 13 digit version of the ISBN, validated and trustworthy. If there is a strong drive for having the qualifiers together with the identifiers, perhaps they could be a added as a separate note field so the identifier? Not the best place of opening this discussion. But i feel this Jira touches on a lot of things that should be a bit more clear. |
| Comment by Ann-Marie Breaux (Inactive) [ 15/Oct/19 ] |
|
Here's a link to examples of many product identifiers, including various configurations of ISBNs: https://drive.google.com/open?id=13KA5SXmev5qApIofCUyKvDRt4reAqNFI |
| Comment by Charlotte Whitt [ 22/Oct/19 ] |
|
Based on the feed back we have gotten from RA, MM, and RM SIG last week - https://docs.google.com/presentation/d/1zsgykxOAKSdjikm8Lg56lamAv9u6o7ms1dTIHx1SDnI/edit#slide=id.p - we'll split this feature into two tracks: |
| Comment by Charlotte Whitt [ 12/Dec/19 ] |
|
Hi Jakub Skoczen - will you confirm/update the estimates of the remaining work on making search on normalized ISBN numbers possible. Thanks much |
| Comment by Jakub Skoczen [ 12/Dec/19 ] |
|
Charlotte Whitt I've updated the estimate to represent remaining work –
|
| Comment by Charlotte Whitt [ 12/Dec/19 ] |
|
Awesome, thank you Jakub Skoczen |