[UXPROD-4038] Create templates to apply to user records Created: 06/Feb/23  Updated: 13/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Molly Driscoll Assignee: patty.wanninger
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-4596 Duplicate/clone to user records Draft
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem: When creating new users in FOLIO, staff do not have a way to pre-populate data in fields or hide fields that are not/should not be used by their institution. The creation of user templates would save time on data entry for specified user types and allow customization/streamlining of the user registration form within the Users app.

In scope

  • Ability to create custom fields with prefilled helper text 
  • Ability to have these fields display only on user records assigned to certain patron groups 
  • Ability to have fields required based on the patron group of the user record 

Out of scope

Use case(s)

  • For records for minors (people under 18), the library needs to collect information for a parent/guardian. They use a custom field for this and would like it required/visible only on relevant records as denoted by a specific patron group.
  • For adjunct faculty, the library captures department and title information. They use a custom field for this and would like it required/visible only on relevant records as denoted by a specific patron group.
  • For community users, the library collects driver's license details. They use a custom field for this and would like it required/visible only on relevant records as denoted by a specific patron group.
  • The library does not track birth date information for specific patron groups and would like to be able to hide this field to prevent accidental input.

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Thomas Trutt [ 08/Feb/23 ]

Templates in general seem to be of interest to a lot of areas within FOLIO as well as user settings. Maybe these ticket should be grouped together or a sub group started to look over a possible solution for the majority of these request?

Comment by Erin Nettifee [ 08/Feb/23 ]

There's a definite difference between a template feature where values are simply preset, and a template feature that asks for fields to be hidden or required based on the value set in a particular field. (Though I think Orders has implemented something for hidden / viewable fields on a template, but it's the template as a whole, not based on a field value - I think the original feature for that work is UXPROD-1665 Closed .)

Which is to say, I would probably try to scope this down a bit because it's unlikely to get worked on in any capacity without being staged a little bit better.

At Duke, we would not prioritize this highly, as we have very few fields that are A) not loaded by our patron loader and B) fields that we would want to have static text pre-populated in.

Generated at Fri Feb 09 00:36:46 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.