[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: |
|
||||||||
| 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
Out of scope Use case(s)
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
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. |