Skip to end of metadata
Go to start of metadata




Discussion items

Beginning / agenda.
    1. We should talk about required data for the User Record.
    2. Manually marking a user active/inactive.
    3. Let’s go over the privacy issues Uschi discovered, and that we discussed last week.
    4. Which of these things require JIRA tickets, and we should prioritize them.

Next week - Todd's presentation. Also potentially general / system accounts (Erin)

Required data for the user record

Preferred first name, middle name, honorific and suffix.

Middle name is in the UI already.

What is required for go-live? Sounds like everyone feels all four fields are needed. Important for patron to be able to be communicated with the way they want to.

Where do these data elements need to be used?

These fields need to be tokenized to include in patron notices.

Checkout screen.

Available to APIs, data integrations. Are there considerations for staff user records? Things that might need to be retained for, say, contracts histories.

Uschi - working with Data Migration field - is there a need to accommodate data type controls? E.g., specify the types of suffixes that the system can do?

Question about Filip's email related to custom fields - can we find out how that is going to be prioritized?

JIRA rankings may need to be revised to reflect importance - JIRA 33. UXPROD-33 - Getting issue details... STATUS

(Note - Tania will cycle off of PO role at end of June. We do not know who is cycling onto that role.)

MODUSERS-113 — three IDs question. Tania has reached out to the dev lead to ask about who they can talk to about scoping this need appropriately.

Manually marking a user active/inactive.

Tania wants to prioritize the development on this.

Right now, someone goes automatically inactive when they expire. But at the moment, there is no ability to toggle it back and forth.

Question - if an account is inactive / expiration date passed, and you extend expiration date into future, do they reactivate immediately or overnight? Tania tests, and the answer is yes.

How is inactive / expired split apart? What is the distinction?

Perhaps inactive is used when someone is on a leave of absence. So you could have someone inactive, but you don't necessarily want their account to be purged.

Staff don't want to do backflips to get someone able to do their job / service.

Changing the date field in the UX impacts the active/inactive field.

Tania demoed what this looks like in the Bellis account.

Summarizing - this ability is critical. It can be less critical if the ability to freeze a field as part of the loader is available - but still important

Security Questions from Uschi
Maura will distribute a Google doc to help to assess priority of UX changes and feature needs.

Next Week
Generic accounts; checkback on custom fields; Todd's presentation