2020-02-20 Resource Access Meeting Notes

Date

17 Feb 2020

Attendees

Discussion Items

Time	Item	Who	Description	Goals
5min	Housekeeping	Anya		Notetaker - (OLD ACCOUNT) Erin Nettifee
	o Permissions for Circ set up o Patron Groups o Locations o Loan Types * o Material types * o Overdue Fine Policies o Lost Item fee Policies o Request Policies o Request cancellation reasons o Patron notice policies o Patron notice templates o Fixed due date schedules o Staff slips o Loan policies	Brooks Travis and Brian Arrigo	Discussion of dependencies and order of operations for creating circulation rules	Walk through these areas - will end at noon and pick up again next week. Goal is to go through these steps and then proceed to circulation rules editor.

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials	Comments
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue

Notes

Welcome to our new meeting format.
A list of pre-requisites:
- Permissions for Circ set up
- Patron Groups
- Locations
- Loan Types *
- Material types *
- Overdue Fine Policies
- Lost Item fee Policies
- Request Policies
- Request cancellation reasons
- Patron notice policies
- Patron notice templates
- Fixed due date schedules
- Staff slips
- Loan policies
Existing documentation in Settings - Circulation - Circulation Rules Editor
Brooks - Missouri State test instance (Edelweiss)
- Begin with permissions sets.
- They have a set of general role-based permission sets. Currently they are only allowing people with "folio_admin" permission set to modify circulation rules.
- Anya - how did you decide which permissions were assigned to that circ staff permissions set?
- Brooks - this is a pretty permissive set, made as a starting point as they begin using workflows.
- Discussion about how granular permissions are - depends on app development - for example, Check In only has one big permissions set.
- Brian - suggestion is to start at beginning with all the permissions, and then become more granular.
  - Incognito mode is your friend when testing permissions - https://support.google.com/chrome/answer/95464?co=GENIE.Platform%3DDesktop&hl=en - Firefox and Safari have similar features. Allows you to be logged in as admin and test permissions in incognito window.
- Patron groups - 12 groups at Missouri State.
- Brian - at Simmons, they essentially moved their old system groups over. They have some agreements for borrowing at other institutions and groups were made to accommodate those, even if those people never or almost never show up.
- Five Colleges - they have made a point of condensing groups down - eg, undergrads, grads are all Students. Means that those students get the same policy, but they were already heading down that road anyway prior to their FOLIO implementation beginning.
  - Five Colleges have separated out summer programs because their students have short terms and condensed semesters.
- Important that these decisions have political considerations, not just technology
- Brooks - the current bulk patron loader will accept the string name of the patron group and map it assuming the group exists, but other places will want the groups UUID, which is not possible to get easily through the UI
- Erin - I see you have an ILL user. Why do that instead of loan type?
  - Mark - iterative process. This is how we do it now.
  - Erin - rather than loaning it in FOLIO, you could simply change a loan type and have a circ rule that says you can't do anything with this item.
  - Allison - oh, so it would be like an item status. Interesting.
  - Andrea - right now, people have to have single users for consortial members - so maybe this wouldn't work at Duke.
- Anya - note that sometimes there are UX issues with ten items in a list, so just be aware.