Date
...
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
- Bjorn: Pre-set values for patron blocks
- Marked as last missing feature for Leipzig in Users App.
- Proposal on Patron Block Customizable Presets
- Pre-set blocking settings: Slide 3
- Create block from preset: Slide 4
- Proposal: Additional Block Action for user self-management (self-edit patron profile), Slide 5
- Requirement: Block import via API: Slide 6
- Discussion:
- Why wasn’t this done before?
- How do we separate them in the UI?
- Concatenate with automatic vs. separate panes/accordions
- Nothing to show for automated blocks right now.
- Brief look at blocks as they stand
- General consensus on pre-set blocks as a good idea.
- Add self-edit block.
- Freeze user record as alternative? - needs to prioritize, not in MVP: https://folio-org.atlassian.net/browse/UXPROD-242
- Just a custom block that discovery can interpret and block patron action?
- Action: Submit feature to Holly for write-up.
- Fee/fine owner discussion:
- <agenda>
- Discussion: Consensus around fee/fine owner as HPL
- Requests pop-up:
- Actions menu vs. link in pane.
- UX Testing (A/B) opportunity
- Take-away:
- Consensus to put action button in menu
- Push on performance issues with Dev for request counts
- Additional new enumeration included in requests table?
- Consensus: No.
- Additional concern about performance with high-count volume holdings. - Cheryl
- Erin - Captions info: https://www.loc.gov/aba/pcc/conser/conserhold/Captabbr.html
- Include? - Consensus continues to be NOT to include it in the popup table.
**Note from Brooks: Sorry for the lack of names next to most of the discussion items.