Date
...
| Time | Item | Who | Description | Goals/Info |
|---|---|---|---|---|
| 2min | Administrivia | Andrea Loigman |
| |
| 30min | Users | User fields and RA needs | Updated user fields list | |
| 30min | Circulation log | Emma Boettcher | to be con't Thursday if not completed. | Solicit feedback on circulation log wireframe, highest priority aspects
|
Meeting Outcomes
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
Follow-up to discussion from 2020-6-11 meeting w / Maura Byrne & patty.wanninger from User Management
...
There is no limit on the number of custom fields that can be added – the limit of 15 custom fields is not (and never was?) true any longer. Given that there is no limit on the number of custom fields, there was agreement that custom fields can be an adequate substitute for statistical codes. Erin showed how custom fields could be implemented with controlled vocabulary and selected from a drop-down list. There was agreement that there needs to be a way to import custom field values from a file or application, as manually putting in the data is impractical. Thought also needs to be put in to ensuring that the data in custom codes fields is retained after anonymization. The JIRA for statistical codes is UXPROD1400.
...