Date
...
Time | Item | Who | Description | Goals/Info |
---|---|---|---|---|
2min | Administrivia | Andrea Loigman |
| |
15min | Search | Cate Boerema (Deactivated) | Query search on Users and Requests | There was a highly ranked "Boolean search" UXPROD which has been broken down into two separate features: 1. Boolean/Query Search for Requests - https://issues.folio.org/browse/UXPROD-2458 2. Boolean/Query Search for Users -https://issues.folio.org/browse/UXPROD-1015 Let's discuss this solution, review the wireframes etc. Does this seem important? What types of searches might you conduct using this capability? |
40min | Circ Log | Emma Boettcher | Loans actions in circulation log | Decide what info to record in search log for all loans-related actions. (Can easily be split over multiple meetings) |
...
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Reasoning | Link to supporting materials | Comments |
---|---|---|---|---|---|---|
e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision |
| e.g. mock-up, JIRA issue | |
Notes
Pleas Please feel free to grammar check and correct the content, thank you
...
- How important are the two issues?
- For Users App the UXPROD-1015 and also this issue: UXPROD-2092
- add drop downs for last name, barcode,
- For Duke and Chicago the external id would be important UIU-1363
- composed boolean search for the often occurring names: last name, first name (is supported already)
- a solution could be a combined index
- from the Users SIG: truncation with *
- For the request app UXPROD-2458
- For Users App the UXPROD-1015 and also this issue: UXPROD-2092
- Fielded vs boolean Search?
- fielded Search is preferred (easier to train)
- consistency throughout the circ apps would be good
...