Mockups for preregistration user records

Description

User story:

As a LoC registration staff, I want to search for patron's preregistration record in the staging table and create an FOLIO user record based on patron preregistration data, so that the patron can access the library’s services.

Requirements:

  1. New page in the Users App:

    • This new page should be accessible from the Users app, and can be similar to the "Lost items requiring actual cost" page (example link folio/folio).

    • The page should allow staff to search for preregistration records and perform actions on them.

  2. Page content:

    • Search: Ability to search by name and email, similar to the existing Users app search function.

    • Preregistration data table. A table displaying patron preregistration details (view-only), will include the preregistration details:

      • First name

      • Last name

      • Middle name (optional)

      • Preferred first name (optional)

      • Email address

      • Phone number

      • Mobile phone number (optional)

      • Address

      • Email communication preferences (optional)

    • Additional columns (e.g., status, registration date) may be needed, we can add them later without requiring a new mockup.

    • Action menu. Each preregistration record should have an Action menu with the following options:

      • Create user record

      • Delete

  3. On Delete should be displayed confirmation modal.

  4. When the "Create user record" option is selected, can be two possible flows:

    • Successful creation. It can be a toaster notification

    • Duplicate records found. In this case, we need to display a modal with a list of existing records. The modal should allow the user to map the preregistration record to only one of the existing FOLIO user records (And this is the most questionable part from a mockup perspective)

Example:

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

Activity

Show:

Irina PokhyletsOctober 3, 2024 at 10:07 AM

Thank you, !

Kimie KesterOctober 2, 2024 at 3:47 PM

Hi I updated the mocks based on your feedback in Slack today. If you can just update the story description above or explain to Devs and others the changes, that would be great. Thanks!

Irina PokhyletsOctober 1, 2024 at 12:36 PM

I will write column list in the user story later. As we discussed the additional columns for now are status, account type (tier1/tier2), and maybe separate columns for address.

Priyanka TeralaOctober 1, 2024 at 12:24 PM
Edited


4 - Do you have a plan to update the columns of the list on 3-records-found.png? probably with status - active/inactive?

Irina PokhyletsOctober 1, 2024 at 12:17 PM
Edited

Hi

1. Agree

2. Yes

4. Yes, we can add it. I confirmed with Kalibek that we don’t need to filter by Active/Inactive status, but we will display this information in the user record. If the user confirms their email via remote registration, the status will be marked as active; otherwise, it will be inactive.

As we don’t need Delete action, do we need to display the action menu or can it be just the “New user record“ button (8-delete.png)?

Done

Details

Assignee

Reporter

Priority

Development Team

None

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 18, 2024 at 6:20 PM
Updated October 30, 2024 at 10:07 AM
Resolved October 30, 2024 at 10:07 AM
TestRail: Cases
TestRail: Runs