2020-11-19 Resource Access Meeting Notes

Date

Attendees

Sharon Wiles-Young

(OLD ACCOUNT) Erin Nettifee

Cynthia Lange

Monica Arnold

Andrea Loigman

Laurence Mini

Holly Mistlebauer

Emma Boettcher

Brooks Travis

Erin Weller

Rameka Barnes

Cheryl Malmborg

Kimie Kester 

David Bottorff

Martina Tumulla

Schwill, Carsten

Cornelia Davis

Anya

Darcy Branchini

mey

Jana Freytag



Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia
45Review the governance and vision & strategyPlease take a look at the PC vision and strategy document and the governance model provide feedback if needed
15Proxy borrowing interaction with patron block on borrowingCurrently if the patron standing in front of you has a patron blocked in effect, they are blocked from checking items out for their sponsors as well (unless you do an override). Let's discuss how we need this to work.

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue




























Notes

Erin is taking notes today.

Emma Boettcher - moving to a new job at Ohio State. We'll miss you Emma! No update on who may be taking over her product owner role.

Agenda: reviewing Product Council vision & strategy and governance model to provide feedback.

  • At Product Council today there was a very nice report on Bugfest for Honeysuckle - things are looking really good. Looks much better than the bugfest for Goldenrod.
  • They are also talking about moving away from trying to have hotfixes... working on processes with coming back to SIGs on feature development... is a hotfix a bug? a feature? 
  • They are also adding a "smoke test" phase to bugtesting - happening next week to try to catch the last minute bugs that were problematic for Goldenrod.

Does RA want to do a group response, or individual responses?

  • One major concern - and comments in place already address - is the idea of paying money to be affiliates. Smaller companies, and smaller libraries, don't have that in their budgets. Antithetical to open source idea. Want people who are not paying to be in leadership roles. 
  • Proposal is for the number of "open seats" on the councils to grow from 2021 - 2023
  • Andrea - would "open" organizations be doing in-kind work? Without an investment in dollars, whether you would end up with people on the council that aren't putting an investment in in time?
    • Mike G. and Kelly D. have put an idea forward of an "expertise" affiliate that could potentially cover this use case. Group feels that this kind of "in-kind" work is necessary for members to be able to get a seat on a governing council.
  • Members on a community council will have to be elected, so that provides another kind of vetting for people (Carsten). And phased approach provides opportunity for adjustment.
  • if Registration on Jira controls voting, the larger the organization is the more votes they have, and that may not address the issues that the model is trying to address (in terms of different types of orgs being recognized)
  • May not be true that the votes are monolithic by institution - orgs may choose their nominees, but individual who vote for the positions can choose for themselves.
  • Andrea - at least one seat on each of the councils should go to an organization that is in production. Cynthia agreed. Brooks - this will probably sort itself out over the next twelve months. The number of libraries coming online in the next year will help this figure it out as it goes forward.
  • Brooks - not sure about balance of 2021 - 2023 - should there be more open seats initially.
  • Erin - has there been discussion about what would happen if the product council and the community council disagree with each other?
    • The community council decides is what is policy, if they are the highest council. (see powerpoint slide)
    • Brooks - the product council and technical council have disagreements now. 
    • Erin - the community council has "project policies and processes" - very ambiguous. 
    • Brooks - the people in charge are recommending this model now, so #shrug
    • Sharon - the Product Council can lose track of things. 
  • Darcy - we all know open source is a challenge, and it fails frequently, or relies on a too small group of core users. Has anyone talked to Open Source orgs or looked at their governance models to borrow their models that have worked well?
    • Sharon - they did talk to Koha, and another group (Sharon can't remember name, but it was a pretty well-known open source community.)
    • Anya - groups don't cross pollinate much so it helps to talk to many different groups to get info.
  • Does group have any other feedback? Important to speak now. Feedback is due tomorrow.
  • Reviewing FOLIO Strategic Objectives document
    • Andrea - we should include an objective that we always follow standards and work to incorporate existing standards. Sharon - will you add that as a comment? Andrea - yes. Standards! Standards! Standards! Standards! It's a concern for new libraries that are exploring the community, that we are articulating it as working with standards instead of inventing our own special way of work.


Holly topic - patron blocks when patron has a proxy.

  • If patron with a block is acting for another person who doesn't have a block, it works. So it seems like it's doing what we want it to do.
  • Acting for themselves = block. Acting for proxy = cleared? Not sure - looks like someone may be messing with these users in Honeysuckle environment.
  • Consensus - in these scenarios, if person is blocked but you are acting for someone else who doesn't have a block, then they should be able to act as a proxy. If proxy is blocked, you shouldn't be able to act for that person.