Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeItemWhoNotes

Announcements/Quick topicsCorrieNone today

WOLFCon sessionsDennis

Submitted a proposal to gather multiple POs on ECS-related functionality

If anyone here has particular interests on what is discussed, please let Dennis know.


Survey (next time)Corrie, Noah

From last meeting: 

(Noah) We should do a survey about perceived gaps, 3rd party integrations needed. Corrie and Noah will do a draft for discussion. Ask about timing folks are considering for moving/implementations. Will be posted on folio-general channel, send it "anywhere and everywhere."

Draft list of questions

2024 goals the listProject updatesEveryone

Draft list of questions

  • Add a multi-choice to open-ended questions where applicable
    • Use in ‘Gaps’ section for barriers, 3rd party integrations 
    • Too many open-ended questions could require responders to take longer to fill out the survey and decrease the number of participants
  • Add follow-up to the ILS question inquiring which ILS(s) 
  • Gaps could be hard to identify if a library isn’t already on FOLIO
  • Add skip logic to differentiate those who have implemented FOLIO from those considering FOLIO
    • Implement based on the category of a responders : considering migration, migration, implemented
    • Questions to ask based on their category :
      • What does FOLIO offer that is of interest to them?
      • Why are they migrating?
      • What are the pain points from their current system?
  • ‘Would you choose single tenant or multi-tenant (ECS)?’ question might be too hard to answer, even for those familiar with FOLIO
    • Transform into a question that gets at what people think is important when considering a single vs. multi-tenant environment
    • Examples : shared collections, ERM, resource sharing, management of workflows, shared patrons, etc.
  • Question : What is critical for your implementation/migration to be successful?
  • What about responders who are members of multiple consortia?  
  • Do we need to differentiate between buying consortia & library network consortia?
    • Ask as part of the demographic section / introduction
    • Add a multiple choice option with a write-in option for an answer not listed
  • SIG section :
    • What would motivate someone to come to the SIG meeting? 
    • Or how do people want to engage with the SIG? 
    • What is the role of the SIG? 
    • Want to gather the perceptions and expectations of the responder of the SIG
    • ‘How can the Consortia SIG better meet or represent your needs?’ implies they know the work we are currently doing ; maybe broaden the question to gather feedback on how/what the SIG does as part of the FOLIO community
  • Is there a way to gather feedback on potential collaboration with other SIGs? 
    • What other collaborations should the SIG be exploring?  (with Reporting, RA, etc.)
  • # of libraries in a consortium – leave open, free-text so people can respond on multiple consortia if applicable
    • Use a different word than ‘libraries’? – institutions, agencies, or members instead
    • Whatever wording is selected, we need to define it
  • After we revise the survey with this feedback, we will need to consider the overall length 
    • If the survey is too long, it could deter partcipants
  • Survey should be anonymous
    • How do we write the survey so it IS anonymous, not just says it is?
    • Don't want responders to feel they can be easily identified based on responses
  • Type up parameters of the survey to communicate ahead of distribution
    • Intended audience
    • Anonymous 
    • How will responses/results be shared?  Aggregated responses only?  
      • How responses will be shared can impact a response
    • How do we distribute results?  Slack channel, emails, etc.  
  • Post from Zorian in Slack : 
    • “I had a thought for a question on the consortial survey: Would it make sense to ask a question along the lines of "Does your consortia participate in shared collection management or acquisitions, particularly of e-resources?" This would indicate interest/need in consortial functionality for acq and ERM”
    • Incorporate this feedback into the type of consortium question and Gaps section 

Next steps : Corrie and Noah will take this feedback and rework the survey for another round of review


ECS DevelopmentDennis

ECS Development – Dashboard in Jira listing tickets related to ECS functionality

Would like to come to a future SIG Meeting and discuss the plans for Ramsons, if the SIG is interested

  • Members are definitely interested

Next steps : Corrie will work with Dennis to schedule a date


Action items