| | |
|---|
Note Taker | | Note taker for today: @Martina Schildt
Note taker for next meeting: @Johanna Radding |
New Member Introduction: Qulto | János Pancza & Zoltán Erdős | János introduces Qulto Mongoose, mongoose is the company, Qulto is the product. 25 years of history with libraries and museums, based on flagship product, which is Qulto. Zoltán CEO and former folio developer senior full-stack developer: Adam > will be the main developer for now, has got at least 10 years of coding experience questions: Shawn: specific app or set of applications will they focus on? János: would like to develop and integrate a mobile app with folio; but are open minded Community Priorities Dashboard - Product Council - FOLIO Wiki can be consulted to see needs in FOLIO; it’s a not yet ranked list Release management group can be contacted as well; group meets every other week; Monday mornings Eastern, 9 a.m. Eastern time.
There's a release management stakeholders Slack channel that
is where a lot of the business is conducted. Tom: will you also be hosting? János: yes, we will also be hosting |
Membership | | CC evaluation and ranking exercise for each of the 14 Propositions:
From the Tri-Council-Discussion (WOLFCon 2025):
Membership and Value PropositionDevelopment priority influence (7): Greater say in determining development priorities (though there were concerns about weighting votes based on contribution level Technical expertise access (6): One-on-one access to community experts for specific technical questions Specialized troubleshooting support (4): Access to guidance for diagnosing and resolving system issues Training materials and resources (4) Reserved governance seats (3): Designated seats on councils for different types of institutions (small libraries, consortia, regional representation Reporting tools expertise (2): Access to community knowledge about effective use of reporting tools Discounted rates for WOLFcon attendance (2): Rather than offering one or more registrations, offer a tiered percentage discount on all registrations from a member organization. API and technical training (1): Specialized training on using APIs and advanced technical features Institution recognition (1): Having member institution names scrolling on the FOLIO homepage or login screen as recognition.
No votes for: Access to QA environments and tested releases: Non-members could receive releases later Access to reference environments: For current and upcoming releases Documentation access: Similar to ArchivesSpace's model Slack access: Requiring membership for an institution's domain to access the FOLIO Slack instance. Community letter and outreach benefits: Inclusion in community communications and promotions
Worth following up on: Development priority influence (7): Greater say in determining development priorities (though there were concerns about weighting votes based on contribution level need to be careful with this; Community does not contribute a lot of development resources in parallel there is the community-driven development effort but it's something that we could, with the right structure, offer as a benefit to members
Technical expertise access (6): One-on-one access to community experts for specific technical questions some type of commitment to contributing time and expertise that could be around subject matter expertise, functional expertise, or technical expertise. there's not tremendous capital that's required, and it does tap into one of the greatest strengths of the folio community, is so many institutions that have got knowledge and goodwill and a willingness to share Rachael: are they also members, or could they be anyone Shawn: how does this fits into the SIG environment, and what their evolving role is in the community. In chat: Better together: The Data Curation Network - Data Curation Network Kristin: How could this work? Right now, if somebody has a question, let's say, they can bring it up at the SIG, they might bring it up on the Slack channel; could be some substantial work on the part of the person providing the information; could be part of someone’s position; time needs to be set aside Simeon: agress to Kristin. Data Curation Network model is really interesting Rachael: what is the selling point if people are already working with their hosts and vendors? Maccabee: users' expertise is very valuable in this concept, that is different from theoretical knowledge; could be value in having a conversation, not only getting an answer on a question in a Slack channel Petra: How would it work? What are the memebers' benefits? I can have a one-to-one, one-on-one talk with someone from IT to set up my system. Who will tell new members what they experienced, is that always the same people? Tom: Tere's the ArchivesSpace community and they have both a member's channel as well as a non-members channel (which is somewhat less vibrant). A working group will be formed.
Training materials and resources (4) Maccabee: simply recorded those one-on-one consultations and put them in a member directory. Rachael agrees with Maccabee Tom: there’s a regular fixture at WOLFcon: How FOLIO works, How the FOLIO community works Mike: maybe develop a buddy system? Peter in chat: Overall, I'm still stuck on how member-only support would differ from what the community does now. (Member-buddy is a good organizing concept) Paul and Petra are already working on what training material is already available. After reviewing the results, we can think of next steps.
There are no other benefits that people would like to surface in this meeting. |
Open items for Councils from WOLFcon | Discussion | Action Items from Tri-Council Meeting at WOLFcon for follow up: Work on visibility of development requests / DIP proposal (PC) Create updated list of FOLIO modules with maintenance status (including orphaned apps) (PC).
Needs to be checked with PC chairs. Develop dashboard for tracking Jira points and cost metrics. (TC)
Maccabee as TC liaison will pass on the question to TC today. “Counting things” follow up from DC Summit (spring 2025) - (Jenn, Shawn, Tom C)
Jenn is reconving this group. And we have a rough set of things to count, and are developing a methodology for trying to count those in a repeatable fashion.
We're anticipating that that will be surfaced in January at the next Tricouncil meeting. Investigate Koha Model for community-driven development and maintenance (Lisa, Jenn, Tom T., Harry)
No updates today. Examine and better define Membership Value to inform a membership drive (CC)
Just discussed, please see agenda item above. Convene AWS working group to draft cost sharing design and investigate feasibility of distributed hosting (in kind contributions of hosting env.) (Stephen, Peter, Wayne, Shawn, Mark V. and/or Yogesh) It was asked how the group is sharing goals with the AWS-investigation group. This group is more on the issue of searching a new paradigma for alterative providers and needs; separate from the AWS-cost-investigation group we've met twice. We have a working spreadsheet that we're using to identify the various stages of the software development lifecycle and associate the infrastructure that we are currently running for each. That will allow us to kind of associate, or find the intersections of where we believe the truly shared items are, which parts of the software development lifecycle are collaborative, and which ones are more individual.
we hope to have something for the Tri-Council meeting in January.
All to report progress at next tri-council meeting (Dec/Jan) To Do: schedule a meeting (ask other Councils about possible slots)
Line Item Contributions – engage with EBSCO (Paul, Tom) there was a line items contributions proposal, which was finished at WolfCon. Thank you to the group, Steven carried it across the finish line, but it was a larger subgroup that worked on that.
Paul and I have been in discussions with EBSCO to see if they will officially endorse this.
|
Next Tri-Council Meeting | @Paul Kloppenborg @Tom Cramer | Best dates for next Tri-Council? Probably in the second or third week of January makes the most sense. Tom and Paul will coordinate with the PC and TC chairs. |