2026-04-15 Meeting notes

5 min

Note taker

@Steve Strohl

• Who will take notes today?

User templates

@Amelia Sutton

• Discussion focused on the “Creation of Templates to Associate with User Records” in FOLIO.

  • This would allow for values to be assigned as part of a default series of values for the templates a library decides to create, helping to eliminate repetitive data entry. Some fields would be able to be hidden as needed.

  • The concept is based in large part on what we see in creating the Order record templates for Purchase Orders.

• UXPROD-4038 was referenced for the group’s review.

• For Circulation it seems to be the consensus of the group that templates would be a welcome addition to the workflow.

• Templates would be optional in Circulation, like they are in Orders (Acquisitions).

• The group went through various fields options that could be optionally “hidden” from view as opposed to other fields that would always be present.

  • All non-required fields will be should be hideable

  • Request preferences being hidden should hide the Fulfillment preference and Default delivery address fields

• One comment focused on have type over text inside a field if the staff wanted to focus Circulation staff on alternative ways to use a field. For example, LAST NAME, FIRST NAME fields could have type over text that would allow them to be used also as DEPARTMENT and HISTORY for the designation of faculty and/or emeritus faculty.

• The group went over the upcoming change to the display of information with a fourth window pain in FOLIO rather than defaulting to a full screen mode in advance of the edit option.

• An overreaching concern as it pertains to templates would be, ideally, having them granular enough so certain staff members at the Circulation desk would only be able to search and have display the fields that more senior staff would designate for them. One example would be, student workers only getting specific fields to search on and display that would protect other students, faculty, and staff member’s privacy.

  • Restrictions on searchable fields will be implemented separately

  • There is also interest in having capabilities that would allow a Student worker to create user records with sensitive data (addresses, contact info, etc) but not view that information afterwards when viewing or editing the record.