Product Council Topic Calendar 2024
Topic
Proposed by
Description
Date added
to list
on PC agenda
Topic | Proposed by | Description | Date added | Date placed | How to ensure SIGs feel they have a good sense of purpose | As Folio becomes more mature, and particularly in areas where functionality is not under active development, it is important that SIGs adjust and are healthy and useful groups for the community. The PC could discuss how to help SIGs feel they are doing useful work, gathering examples of how different SIGs operate and share best practices | Scope of FOLIO in relation to reporting topic | Reporting / lack of reporting / lack of clarity about reporting options is a topic that is raised regularly, and following a review of the 2023 “things that could be improved about Folio” survey outcomes, the PC felt there would be benefit in some PC discussion of how the options could be better communicated and the situation as regards “reporting” (which can be an ambiguous term with the grey areas of what is ‘in app’ reporting) could be better described for greater shared understanding across the community | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Linked data app - formal review for approval in Ransoms | Initial overview of linked data work was shared with the PC on 2024-04-04 Meeting notes. The team (Doug Lyons and Gloria Gonzales) intend to come back share alpha version of development work completed that should be included in Ransoms closer to the date (deadline for review currently Sept. 13. At this time we should also have more details on the roll out. |
| early July? | Review of work: Mark for deletion (Set for Deletion) instances and underlying MARC | New functionality for deleting instances and underlying MARC coming quickly: https://folio-org.atlassian.net/issues/UXPROD-4303?jql=text%20~%20%22mark%20for%20delete*%22. Some concerns around app interactions and dependencies (spreadsheet). Recommend MM SIG and App Interaction have conversations first, and bring to PC in case of need. A diagram showing dependencies would be helpful. |
| BugFest testing review | How can we keep people motivated and engaged to participate in BugFest? What roles for the community could we have to make BugFest successful? Discuss this after Quesnalia BugFest is finished Updated 6/18/2024: There is a survey on Bugfest currently out there. Would like to discuss results within PC. |
| Follow up on prioritization pilot process in Acq SIG | First presented at 2/22 and 2/29/24 meetings. Acq SIG will evaluate after Quesnalia release and report back to the PC in May. |
| Name label changing impact and info dissemination | Label/name/data model changes (see below) in FOLIO have an impact on external systems. This information needs to be shared more widely. Discuss ways to do this. Reporting SIG raised concerns about changes made to the FOLIO data model are not being well communicated and documented. Impacts of New FOLIO Fields and Features on Reporting Once the PC has some recommendations, share with Tod/TC for their input |
|
Privacy SIG roadmap | The Privacy SIG roadmap. The SIG currently has no convener and the previous convener believes the SIG model is not well suited to the multi-dimensional challenges of building privacy into the design of FOLIO. This presents two questions: (1) what to do about the Privacy SIG (2) how to make progress on a privacy roadmap for FOLIO. |
| This will go to the Tri-Council | Onboarding with Implementers | The now defunct Onboarding group asked the Implementers SIG at WOLFCon 2023 to take over some of what they started. Catch up with them on how it's going and the plan moving forward. |
| For Tri-Council meeting, retrospective on Poppy release | The delay(s) in the Poppy release and a variety of other issues have been a challenge. |
| Ongoing need for Product Owners and representation distribution | Jesse Koennecke Kristin Martin Charlotte Whitt Jennifer Eustis Alexis Manheim | FOLIO regularly needs POs. How can we help? What is the distribution of POs from vendors, libraries, etc.? |
| What should be core vs. extended in re-architechted FOLIO? | The PC will be responsible for determining which apps are considered core vs. extended when the overall FOLIO architecture changes? |
|
Snapshot data refresh | Current data in FOLIO Snapshot is not as useful as it could be. Is there a way to get a small, lightweight, and clean dataset into Snapshot that includes examples of data use cases that have been problematic in the past? What are the other parameters for this data? Can we task the SIGs with creating/providing this data? DevOps team is responsible for maintaining the Snapshot. |
| sometime in May | |||||||||||
Retrospective report on new CSP process | Oleksii Petrenko says this will happen in Nov or Dec after the Poppy release. | 29 Sep Proliferation of new apps | As FOLIO develops more new apps will be added to the product. What are the implications for the UI, etc.? Is
|
| ||||||||||
Recommend a process for vendor requests to integrate with FOLIO | Guidance is needed for library vendors that want to create integrations with FOLIO on how to approach and work with the larger FOLIO community on this development. |
| ||||||||||||
How to ensure SIGs feel they have a good sense of purpose | As Folio becomes more mature, and particularly in areas where functionality is not under active development, it is important that SIGs adjust and are healthy and useful groups for the community. The PC could discuss how to help SIGs feel they are doing useful work, gathering examples of how different SIGs operate and share best practices | |||||||||||||
Scope of FOLIO in relation to reporting topic | Reporting / lack of reporting / lack of clarity about reporting options is a topic that is raised regularly, and following a review of the 2023 “things that could be improved about Folio” survey outcomes, the PC felt there would be benefit in some PC discussion of how the options could be better communicated and the situation as regards “reporting” (which can be an ambiguous term with the grey areas of what is ‘in app’ reporting) could be better described for greater shared understanding across the community. Jennifer Eustis will be taking conversation to Reporting SIG for further discussion and next steps. | |||||||||||||
Linked data app - formal review for approval in Ransoms | Initial overview of linked data work was shared with the PC on 2024-04-04 Meeting notes. The team (Doug Lyons and Gloria Gonzales) intend to come back share alpha version of development work completed that should be included in Ransoms closer to the date (deadline for review currently Sept. 13. At this time we should also have more details on the roll out. |
| early July? | |||||||||||
Review of work: Mark for deletion (Set for Deletion) instances and underlying MARC | New functionality for deleting instances and underlying MARC coming quickly: https://folio-org.atlassian.net/issues/UXPROD-4303?jql=text%20~%20%22mark%20for%20delete*%22. Some concerns around app interactions and dependencies (spreadsheet). Recommend MM SIG and App Interaction have conversations first, and bring to PC in case of need. A diagram showing dependencies would be helpful. |
| ||||||||||||
BugFest testing review | How can we keep people motivated and engaged to participate in BugFest? What roles for the community could we have to make BugFest successful? Discuss this after Quesnalia BugFest is finished Updated 6/18/2024: There is a survey on Bugfest currently out there. Would like to discuss results within PC. |
| ||||||||||||
Follow up on prioritization pilot process in Acq SIG | First presented at 2/22 and 2/29/24 meetings. Acq SIG will evaluate after Quesnalia release and report back to the PC in May. |
| | |||||||||||
Name label changing impact and info dissemination | Label/name/data model changes (see below) in FOLIO have an impact on external systems. This information needs to be shared more widely. Discuss ways to do this. Reporting SIG raised concerns about changes made to the FOLIO data model are not being well communicated and documented. Impacts of New FOLIO Fields and Features on Reporting Once the PC has some recommendations, share with Tod/TC for their input |
| ||||||||||||
Privacy SIG roadmap | The Privacy SIG roadmap. The SIG currently has no convener and the previous convener believes the SIG model is not well suited to the multi-dimensional challenges of building privacy into the design of FOLIO. This presents two questions: (1) what to do about the Privacy SIG (2) how to make progress on a privacy roadmap for FOLIO. |
| This will go to the Tri-Council | |||||||||||
Onboarding with Implementers | The now defunct Onboarding group asked the Implementers SIG at WOLFCon 2023 to take over some of what they started. Catch up with them on how it's going and the plan moving forward. |
| ||||||||||||
For Tri-Council meeting, retrospective on Poppy release | The delay(s) in the Poppy release and a variety of other issues have been a challenge. |
| ||||||||||||
Ongoing need for Product Owners and representation distribution | Jesse Koennecke Kristin Martin Charlotte Whitt Jennifer Eustis Alexis Manheim | FOLIO regularly needs POs. How can we help? What is the distribution of POs from vendors, libraries, etc.? |
| |||||||||||
What should be core vs. extended in re-architechted FOLIO? | The PC will be responsible for determining which apps are considered core vs. extended when the overall FOLIO architecture changes? |
| ||||||||||||
Keep a list of existing apps and their state of maintenance, their status of integration (tight or just loosely), developer team, responsibility, connected MoU's about maintenance | The Product Owners have created a Team vs module responsibility matrix. Harry is developing a simplified version on a single slide as well as a list of orphaned apps and modules. Having a list of orphaned areas is useful for when an organization joins FOLIO and wants to work on something. It is possible to have orphaned modules that don't in turn orphan an app (the single sign-on module is an example). There is another category of apps for which a team performs periodic maintenance but there is no active development (updating dependencies, for instance). An additional acceptance criteria for contributing code could be a memorandum-of-understanding to support the code for an explicit period of time. What is the maintenance commitment for code contributed by established partners? |
| ||||||||||||
Release planning | From Martina Schildt | What is the release management planning/process. Talk to release manager regarding release process and where could improvements come in. This could be combined with report on BugFest. Invitation to Anton and Oleksii Petrenko. |
| |||||||||||
Need full support for GDPR | from Martina Schildt | Have Privacy SIG report on GDPR needs and how that work can be slotted into FOLIO development - discussion postponed - check again on |
| |||||||||||
Managing upgrades so that implemented libraries to take advantage of new functionality | from Kristin Martin |
|
| |||||||||||
FOLIO Technical Pain Points | from Tod Olson | Part of the TC Goals & Objectives process has been to identify technical pain points within FOLIO that impede development and operations. We plan to look at underlying causes, come to agreement on some remedies, and use this to inform our priorities. Like any form of technical debt, these will require resources to address, but will pay dividends if addressed well. See: FOLIO Technical Pain Points - DRAFT (in progress) |
| UI Customization rather than Permissions | Start plan for when to do all of the planned Features for the customization of FOLIO. There are a bunch of things that we want to bring to FOLIO put together in a plan as a theme in the Roadmap. |
|
Completed Topics
See: FOLIO Technical Pain Points - DRAFT (in progress) |
| |||
UI Customization rather than Permissions | Start plan for when to do all of the planned Features for the customization of FOLIO. There are a bunch of things that we want to bring to FOLIO put together in a plan as a theme in the Roadmap. |
|
Completed Topics
Topic | Proposed by | Description | Date added | Date placed | ||||
|---|---|---|---|---|---|---|---|---|
Retrospective report on new CSP process | Oleksii Petrenko says this will happen in Nov or Dec after the Poppy release. |
|
| |||||
Snapshot data refresh | Current data in FOLIO Snapshot is not as useful as it could be. Is there a way to get a small, lightweight, and clean dataset into Snapshot that includes examples of data use cases that have been problematic in the past? What are the other parameters for this data? Can we task the SIGs with creating/providing this data? DevOps team is responsible for maintaining the Snapshot. |
|
| |||||
PC on-boarding of Dev Advocate | The new FOLIO Developer Advocate started this week. How should the PC engage with the position? |
|
| |||||
FOLIO Story paper | Mike Gorrell wants to come to discuss FOLIO Story and get any final feedback. | 13 May 2024 |
| |||||
API knowledge sharing/refresher | List is here: https://dev.folio.org/reference/api/ |
|
| |||||
Challenges of integration of Folio with Discovery services | Add to PC agenda in January and initiate discussion with Khaliliah and Uwe Reh |
|
| |||||
Mid year check in on priorities/goals | Review how things are going with the goals and priorities we set at WOLFCon 2023 |
|
| |||||
Review of Evaluation Process for New FOLIO Functionality | The Evaluation Process for New FOLIO Functionality six month pilot period just ended and it's time for review. Need feedback from POs. Draft version shared:
|
|
| |||||
Roadmap and Prioritization Working Group update | Plans for a prioritization process based in the SIGs, etc. |
|
| |||||
Time Zone Inclusiveness | 2023-09-20 Meeting notes Meeting Hygiene and Efficiency Subgroup | Follow up from WOLFCon what can the PC do this year discussions. 2023-12-20 PC Meeting Hygiene and Efficiency Agenda and Meeting Notes |
| and/or We will discuss this at the quarterly SIG Conveners meeting, but perhaps also at the 12/7 meeting when the Hygiene group gives their report? | ||||
(Direct Consortia Borrowing) DCB functionality in Quesnalia | Team Volaris is initiating the process of submitting three new modules for TC review. As part of this process, seeking a PC approval. We have already created the three TCR tickets. These are TCR-35, TCR-36, and TCR-37.A good starting point to learn more about the purpose of the three modules is the DCB Integration wiki page. |
| ||||||
Update from and feedback on PC Meeting hygiene subgroup | The PC Meeting Hygiene and Efficiency subgroup will report on what they've done and get feedback on changes. |
| ||||||
Entities Management followup. Will reach out to the MM-SIG | Feedback from MM SIG conveners regarding final report from the Entity Management Working Group | Should the MM SIG take over Entity Management work (or at least be the lead), should it be a new SIG, under another group, etc.? Then it was pointed out how much MM SIG already has responsibility for and that there are other groups like Acquisitions and ERM that would have a big stake in this as well. | but PC notified and had an initial discussion on | SIG Reports subgroup is addressing this issue Does the Entity Management group fall under MM SIG or is it a SIG on its own? | ||||
State of QA for new releases | resulting from discussion at 2023-09-28 Product Council Agenda and Meeting Notes | After a discussion about release management and timing, CSPs, etc, Khalilah Gambrell suggested that we have members of the EPAM team at an upcoming PC meeting to talk about the state of QA. |
| |||||
Flower release schedule - release dates and/or decreasing the number of annual releases, and how this fit in with the re-architectural decisions. | Follow up from later than expected Quesnalia release date, feedback currently being gathered | |||||||
Platform & Application Formalization Questions from the Technical Council | follow up from WOLFCon 2023 |
| is this for re-architecting subgroup or PC in general? will start in subgroup. See Re-Architecting Impact on the Product Council | |||||
Support SIG Community Developer | from Anya | Need to recruit new developer |
|
Edit by Charlotte Whitt (10/2/2023) | ||||
Need for additional Product Owners | from Jesse Koennecke | Jesse is discussing needs with Khalilah |
| |||||
Translation of documentation | from Martina Schildt |
|
| Edit by Martina Schildt (10/04/2023) | ||||
Review the status of the calendar app. | Cheryl will work more on the specifications of the problem, bringing in others from the RA SIG and FOLIO implementers as well as possibly developers from the Vega team. This will likely then come back to product council. Calendar App development taken on by Bama team. See: 2022-03-24 Product Council Meeting Notes. Did not have further discussion with PC. |
| ||||||
Establish criteria for newly developed apps and code contributions | In coordination with Technical Council and Community Council, what is PC's criteria for accepting contributed code. What alternatives exist if a contribution is not accepted; what does it mean if something is not accepted. In the context of the LDP inclusion discussion, the PC identified the need for its own criteria for accepting apps into the reference environments. For instance, does an app meet the style guidelines? And later in the meeting, is there a support commitment from the developers? FOLIO Scope Criteria Group formed, meeting starting in December 2021. Update in June. |
|
Edit by Charlotte Whitt (10/2/2023) | |||||
Review FOLIO Vision, Strategic Objectives and Initiatives for PC items | Carry-over 2021-09-16 Product Council Meeting Notes | CC also identified items from the vision document that they thought was the responsibility of PC and TC. Review the CC document in the context of the strategic objectives document. See the objectives with roles assigned: FOLIO Vision, Strategic Objectives and Initiatives Conversation begun at 2021-10-07 Product Council Meeting notes Sharon/Anya working on SWOT analysis with implementers' libraries |
|
| ||||
Privacy SIG New Charter | from Peter Murray | For an upcoming Product Council meeting, the Privacy SIG has revised its charter and is seeking endorsement: About the Privacy SIG |
|
| ||||
Update on WOLFCon development | From Mike Gorrell | 15 minute slot at that meeting to present FOLIO WOLFcon Planning and ask them to contribute their ideas and needs for WOLFcon sessions. |
|
| ||||
Identifying priorities for development for FOLIO | Anya, Martina Schildt, Tod Olson and Jana Freytag volunteered to work on a group to look at the issue of feature ranking. |
|
| |||||
Update on Data Sync Working Group | From Brooks Travis | Ways to synchronize data across FOLIO apps. Group work started in August under App Interaction. Originally wanted to present November 18, moving back to December 2, then to December 9 Will provide discuss on Feb. 10 SIG Conveners |
|
| ||||
...