Page Comparison

Presentation of mock-ups and discussion

_ Slide 4: Title look-up is a new feature, I think (building a modal [pop-up window] for it). Item look-up doesn't exist either yet. Title look-up could function similarly to patron look-up.

_ What if you untick the box afterwards - or is it impossible? Hmmm-- either you couldn't uncheck it  OR  have item level filtered back into the view.  Probably ok before you save to untick; afterwards, you prob. can't switch back to item.

_ New idea= create a request from a new instance. 

_ Keep them seperate? (Instead of having a check box) New request --> Item or title?   
There were converstaions about adding the action in the Action menu... it seems that checkbox seemed like the sleeker option. Also because Action list is getting longer. 

General consensus on the work flow --> Steph can now work on user stories >> estimate effort >> more nitty-gritty of how this will work in the back end.

_ Additional considerations: Default checking of that box? Permission controls on that box? 

_ Will the student understand this jargon? So does the UI help the operator make the right choice? We want the least training possible, and this looks like you need insider knowledge. 
Would hover-over/helper text help? E.g. "This title request could be filled by 10 copies." / is request will be placed on all 6 copies." / "his request will be placed on all available copies."
Though it would be important to have this information in the API - so that the patron has that information when they place a request.

Title Level Requests
Revised mockups for Title level requests

Presentation of mock-ups and discussion

_ Reordering would use exsiting drag&drop functionality (which already exists for item level)

_ How does the system prioritise item vs. title level request? I don't think we've made a decision yet, prob. first in first out. 
When reordering and looking at the item request list, you should also see which was an item request, and which was a title request, e.g. if staff wants a particular item in order to fix it, then the staff should indeed get exactly that item. Are these edge cases?
Could this be a setting, whether item and title requests are equal (i..e priority = first in, first out) OR  title level takes precedence over item level  OR  item level takes precedence over title level (i.e. all title/item level requests must first be fulfilled before going onto item/title level requests). 
Cleanest way to do it would prob be a time stamp...

==> Could someone please work on a work-flow for prioritisation?  Marie / Thomas / Erin

→ Don't hesitate to use Slack to post your thoughts too!