Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
Medium < 5 days
-
Medium < 5 days
-
-
Prokopovych
-
-
R1
-
R4
-
R2
-
R2
Description
Tags will be useful on Requests for many reasons. For example, to support the pick list workflow using the Requests csv.
Scenario
- Print csv for items to be picked up off the shelves (Request status = Open - Not yet filled and Item status = Available)
- Find all but 2 of the items
- Mark those two requests/items as not found so they can be filtered out of the next pick list report which may be generated again in an hour or so
When discussing how best to handle this scenario, we looked at the missing item feature (UXPROD-965) to see if this might be a way to handle it, but Missing changes the Item status which displays to the patrons and would be confusing. Also, most of the time these items are soon found within a day or so.
Ultimately, we decided that Tags would be a good way to handle this scenario. Ideally you could filter by this tag. But, as long as the tag is displayed in the csv, that should be sufficient for go-live. Aren't Tags handy?
Please note, there is a feature in the backlog for a "real" pick list report: UXPROD-923