2021-02-09 Meeting Notes

Date

Attendees

Paula Sullenger

Kelly Drake

Dwayne Swigert

Jean Pajerek

Monica Arnold

Brooks Travis

Karen Newbery

Tod Olson

Debra Howell

Ian Walls

Tracy L Patton

Martina Schildt

Jesse Koennecke

Peter Murray

Andrew Clark

Darsi Rueda

egerman

Christie Thomas

Ann-Marie Breaux (Deactivated)

Jacquie Samples

Jenn Colt

Martina Tumulla

morganm@gvsu.edu

Robert Scheier

Theodor Tolstoy (One-Group.se)

Tom Wilson

patty.wanninger

Marie Widigson

Kirstin Kemner-Heek

@nbecwar


Goals

Discussion items

TimeItemWhoNotes

Optimistic Locking update

Checked in with Jakub who said "If we expect that more modules should implement OL we need to get tickets created in Jira with a specific request".

Paula will get more clarification from Jakub on getting tickets written






New roadmap planning processKelly Drake

Short-term task force, hope to get done in a month, to develop a project roadmap for FOLIO, dealing with development needs and addressing develpment outside the purview of the Capacity Planning team.

Questions from TF:

What would your group look for in a roadmap?

KN- to know how tech debt will be addressed; to know when certain features will be developed

Ian- who is the responsible person for a certain thing?  Say someone is making a module that is an outside special project, how do we know what is being worked on so that someone else doesn't start a duplicate effort

Jacquie: who will maintain the roadmap document over time?  AMB- especially as things age and need to be updated

Tod- what are the boundaries of the roadmap process and are we straying outside of them? (if things outside of roadmap come up, we want to still hear them and take them back.)

Jesse- is there a willingness to be roadmap driven?  For ex, implemented libraries wants new things that aren't in the current roadmap.

Jacquie - what about a place to record the things we know we can't work on now, don't want to lose track of them - thinking about the Epics/Stories that are not on the map, so organize the page by Epic, details of situation associated beneath.  This type of information might help individual institutions to plan areas of local development.  And helps the communication of those development areas to the wider FOLIO community.

AMB- Epic is too big, feature level makes more sense for this need

Kelly- Strategic Planning document has a lot of things that aren't being requested by libraries now, they're about expanding appeal to the wider library community.  Where does the balance come in?  Are institutions willing to give up short-term goals for the greater vision

Ian- as a host is beholden to their customer needs

TF question: what about the feature ranking process?  Should there be a limit on R1s per institution?

Patty- ranking does not give consensus. Ex- deletes are high priority for some, irrelevant for others

AMB - same with MARC Holdings, of critical importance to a few

Jacquie: I am thinking more and more that if an institution has no intention of using a feature, that their ranking isn't included in the math, so that those R5s don't outweigh the few that really do need it.  Is there a way to figure out if an institution has had a chance to review the features that are important to it.

Christie- some are saying that R5 should mean we don't think community resources to this but she doesn't think it's the right approach

Ian- Trying to reach a consensus on limited pool of resources, institutions need to pool their resources to get those unique features developed

AMB- We're seeing some of that - this is important to me, so we'll apply (or pay for) some resources - e.g. OCLC single record import, and some of the stuff that Cornell is working on

Tod- Individual inst rankings are trying to capture one slice of data, institutional-level priorities.

we need to to keep this, it's useful. How do we pull together or give input into project-level  priorities?

Update from Capacity Planning Team to PC on the process: 

TF- why do people feel their priorities aren't being heard?  Who is missing from the process? and why?

Christie- anything that isn't in JIRA doesn't exist, sometimes we're just waiting on someone to write things up so the same things keep coming up

Ian- data migration group feels that it's not being heard, have JIRAs but still not being worked on, seems to not be a priority because it's used only once per institution

Tom- we have to realistically work with the resources we have. 

Brooks- We need a mechanism to formally indicate strategic development needs for the project. Provide some mechanism to “escalate” features for the community to prioritize outside the existing ranking system.

Tod- balancing immediate needs against strategic investments

Ran out of time, will take up more TF questions next week.








Implementation issues



Many of the SIGS have implemented various process for dealing with their specific implementation issues.  Here's a quick list:

Resource Management implementers - https://folio-org.atlassian.net/wiki/display/RM/Resource+Management+implementers

Inventory Implementers - https://folio-org.atlassian.net/wiki/display/MM/Inventory+Implementers

ERM Implementers - https://folio-org.atlassian.net/wiki/display/RM/ERM+implementers

RA SIG - Thursday Implementer Discussions.FOLIO Implementation Group - https://folio-org.atlassian.net/wiki/display/COHORT2019/FOLIO+Implementation+Group






Collecting individual institution documentation and training -




Community Contributed Resources 

Kristen Martin has folder in Google Drive for Resource Management documentation.






Future topics

Receiving workflow demos deferred until Honeysuckle - Bywater libraries using Honeysuckle starting tomorrow, a couple others going in February, Cornell and Duke using ERM Honeysuckle







Of Note:
Last 20 minutes of Data Import meetings have morphed into "Labs" where they're working with libraries on workflows. Also, Data Export meetings have become sharing labs for the entire hour. Data Import meetings are Wednesday 1:00 p.m Eastern. Data Export Thursday 3:00 p.m. Eastern.



March 2- Capacity Planning team Juniper update

Action items

  •