Khalilah's team is working on an accessibility issue to make the required fields labeled as required (with more than just a black asterisk). They added html to indicate required...shows up as a red *. The group agreed that the required fields in the users module should also get this change so the required fields properly indicate to screen readers which fields are required.
Discussed system users vs actual FOLIO users. (system user example - SIP2). Suggestion - an indicator the spells out the 'type' of user. This indicator could be driver of which fields are required. (e.g. system user doesn't really have a first name/last name). Existing ticket.
It should be documented, that if a system user is created via the API without including the fields the UX requires, any changes to that user will have to be made using the API because the UX requires a specific set of fields. Maura will add this to the tips and tricks section of the wiki.
List of user fields document. → attempt to gather together, evolution of the user record and make some decisions about what improvements need to be made for initial adopters.
Preferred name and department are fields being added to the user record (in development right now).
Statistical codes → if we adopt stat. code as they exist in inventory, would they be merged with the inventory stat. codes...so all codes would show up in both modules? No ...the thought was users would have it's OWN statistical codes.
We can wrap up this discussion next week. We can discuss a user story next week for statistical codes.