Community Priorities Dashboard

The Community Priorities Dashboard (CPD) is managed by the FOLIO Product Council (PC) and populated by FOLIO Special Interest Groups (SIGs.) The purpose of the CPD is to draw attention to the highest priority needs as defined by FOLIO subject matter experts (SMEs), help the PC identify product level gaps or trends, and foster collaboration among Community members with shared needs.

PC issues call for updated priorities Updated priorities due PC publishes priorities dashboard

Community Priorities Dashboard

2025 Community Priorities (from Jira)

2025 Community Priorities (original)

Group	Priority #1	Priority #2	Priority #3	Priority #4	Priority #5

Group	Priority #1	Priority #2	Priority #3	Priority #4	Priority #5
Acquisitions	https://folio-org.atlassian.net/browse/UXPROD-4589	https://folio-org.atlassian.net/browse/UXPROD-4243	https://folio-org.atlassian.net/browse/UIREC-273	https://folio-org.atlassian.net/browse/UIOR-1190	https://folio-org.atlassian.net/browse/UIF-480
Cross App	https://folio-org.atlassian.net/browse/UXPROD-4547	https://folio-org.atlassian.net/browse/UXPROD-4546	https://folio-org.atlassian.net/browse/UXPROD-4545	https://folio-org.atlassian.net/browse/STCOM-1160	https://folio-org.atlassian.net/browse/UXPROD-1647
ERM	https://folio-org.atlassian.net/browse/UXPROD-5330	https://folio-org.atlassian.net/browse/UXPROD-5334	https://folio-org.atlassian.net/browse/UIEUS-429 https://folio-org.atlassian.net/browse/UXPROD-5578	https://folio-org.atlassian.net/browse/UXPROD-5189	https://folio-org.atlassian.net/browse/UXPROD-5348
Discovery	https://folio-org.atlassian.net/browse/UXPROD-4805	Tell the Discovery system what item is holdable. https://folio-org.atlassian.net/browse/UXPROD-2422	Tell the Discovery system what item is renewable https://folio-org.atlassian.net/browse/UXPROD-2758	Ability to Sort Items in FOLIO so that the Discovery system does not have to sort 10,000+ items on the fly https://folio-org.atlassian.net/browse/UXPROD-5257 , https://folio-org.atlassian.net/browse/UXPROD-1625
Reporting	Support for data anonymization in Metadb software version 1.5. See Metadb Issue #21 and see related: UXPROD-1041 UXPROD-4302 UXPROD-3659 Metadb Issue #89	Fix software bugs impacting Metadb data: Metadb Issue #92 https://folio-org.atlassian.net/browse/MODDATAIMP-1230	Metadb Derived Table Updates, Maintenance, and Management	Reporting App Permissions Development https://folio-org.atlassian.net/browse/UILDP-178 https://folio-org.atlassian.net/browse/UILDP-184 Reporting App Permission Based on GitHub Repository Directory Access (new Jira coming)
Public Library	https://folio-org.atlassian.net/browse/UXPROD-4776	https://folio-org.atlassian.net/browse/UXPROD-5094	https://folio-org.atlassian.net/browse/UXPROD-5117	https://folio-org.atlassian.net/browse/UXPROD-3567
Data Export	https://folio-org.atlassian.net/browse/UXPROD-2708	Ability to edit a profile after it has been used (UXPROD-2708) https://folio-org.atlassian.net/issues/UXPROD-2708?jql=ORDER%20BY%20created%20DESC	Ability to combine Instance data and SRS records (UXPROD-3254) https://folio-org.atlassian.net/issues/UXPROD-3254?jql=ORDER%20BY%20created%20DESC	Ability to cancel a job (UXPROD-2328) https://folio-org.atlassian.net/issues/UXPROD-2328?jql=ORDER%20BY%20created%20DESC	https://folio-org.atlassian.net/browse/ROAD-65
Linked Open Data	https://folio-org.atlassian.net/browse/UXPROD-5668	https://folio-org.atlassian.net/browse/UXPROD-5665	https://folio-org.atlassian.net/browse/UXPROD-5227	https://folio-org.atlassian.net/browse/UXPROD-5228	https://folio-org.atlassian.net/browse/UXPROD-4600
Implementers	https://folio-org.atlassian.net/browse/UXPROD-4776	https://folio-org.atlassian.net/browse/UXPROD-3822
Bulk Edit	UXPROD-4990 - Trillium - bulk edit performance improvements	UXPROD-4025 - Creating and Managing Bulk Edit Profiles for Scheduling Jobs	UXPROD-5277 - Token support in bulk edit profiles	UXPROD-4952 - Bulk edit - Scheduling bulk edit jobs
Data Import	Update Instance Administrative Data Only (https://folio-org.atlassian.net/browse/UIDATIMP-1724)	Allow update of the Instance and the SRS record in a single data import job (https://folio-org.atlassian.net/browse/MODDATAIMP-1199)	Allow for MARC field protection at the import profile level (https://folio-org.atlassian.net/browse/UXPROD-2934 )	Reporting: Have the ability to download a list of errors from an import (https://folio-org.atlassian.net/browse/UIDATIMP-914 )	Jobs run immediately after canceled jobs take excess time (https://folio-org.atlassian.net/browse/MODSOURMAN-970)
List App	Expanded data coverage (covered in a variety of features)	UXPROD-5178 Lists: Build queries with "OR" and "NOT" Boolean operators	UXPROD-5470 Lists: Create a list based on an uploaded file of records	UXPROD-5120 User defined entities with joins, created via Lists app UI	UXPROD-5157 Lists: Support building queries based on relative dates
Metadata Management	Reorder of Holdings and Items (https://folio-org.atlassian.net/browse/UXPROD-3178 ; https://folio-org.atlassian.net/browse/UXPROD-1635 ; https://folio-org.atlassian.net/browse/MODINVSTOR-1142 ; https://folio-org.atlassian.net/browse/UIIN-2688)	Inventory Hierarchical Navigation Structure (UI/UX refactor) (https://folio-org.atlassian.net/browse/UXPROD-491)	Search MARC fields in UI (https://folio-org.atlassian.net/browse/UXPROD-5218)	Inventory: Strip leading, trailing, and double spaces out of data in some elements (instance, holdings, item) (https://folio-org.atlassian.net/browse/UXPROD-3473)	Make 336 (instance resource type) repeatable on Instance records (https://folio-org.atlassian.net/browse/UXPROD-3973)
Resource Access	https://folio-org.atlassian.net/browse/UXPROD-3651	https://folio-org.atlassian.net/browse/UXPROD-4876	https://folio-org.atlassian.net/browse/UXPROD-4462	https://folio-org.atlassian.net/browse/UXPROD-2188	https://folio-org.atlassian.net/browse/UXPROD-5175
Course Reserves	https://folio-org.atlassian.net/browse/UXPROD-4869	https://folio-org.atlassian.net/browse/UXPROD-2775	https://folio-org.atlassian.net/browse/UXPROD-2594	https://folio-org.atlassian.net/browse/UXPROD-4870	https://folio-org.atlassian.net/browse/UICR-60
Consortia	https://folio-org.atlassian.net/browse/UXPROD-4998	https://folio-org.atlassian.net/browse/UXPROD-4839	https://folio-org.atlassian.net/browse/UXPROD-4713	https://folio-org.atlassian.net/browse/UXPROD-4798	https://folio-org.atlassian.net/browse/UXPROD-4825

Development Plan

Gather all SIG priorities
Review top 5s together on PC Slack and in PC meeting on 4/24
Draft prototype community priorities dashboard Jira, review as a group, and determine how to come up with a single rank PC list (5/8)
Refine further, prepare for wider distribution (target 5/29)
Share for feedback at June SIG Conveners meeting, POs, PC, and TC.<< We are here
Publicize and get feedback at WOLFCon, determine plan for maintenance & distribution

Review Notes

Proposed process: SIGs or liaisons will visit PC to discuss priorities PC Members rate each prioritized feature 1-5 on each factor in DRAFT Prioritization Rubric Should rating be hybrid - PC members rate asynchronously then discuss in meeting before we finalize ranking PC needs a way to add features to the list that might not have been raised by SIGs - engage POs here? Repeat 2 times a year to align with release schedule - what’s the milestone we need to look at here? How do we capture functionality not represented in the SIG priorities

Two tier Single rank list of vetted, shovel ready UXPRODs ranked by PC Broad list of priorities submitted by community Can PC include priorities that reflect technical debt? How would we get UXPRODs? maybe these would be gaps against a baseline Jira Dashboard All priorities must have UXPRODs Is it ok to create placeholder UXPRODs? Only complete, dev ready UXPRODs can be included on PC list. Flag UXPRODs in submitted by community that are high priorities for PC but need more work. PC add priorities for gaps against established baseline To accomplish this we need: validated baseline a process for getting these reflected in UXPROD - who is product owner? Do we ask SIGs to add them? etc How to best reflect technical debt? Proposed Distribution Plan Long Term Goal - update and distribute this page quarterly in April, July, October, and January. Beginning of the month - put out call to SIG liaisons mid month - compile and review with PC end of month - distribute to the community via Slack add recurring agenda item for tri-council meetings and community updates

Observations This was a big ask - we will need to give ample lead time and be patient as they ramp up this process Not everyone submitted 5 - maybe top 3 would be more focused / lighter lift Implementers and some subgroups wished to include their top 5 Review Questions Content How useful are these priorities? How can we make them more useful? How does this track with our assumptions about FOLIO development priorities? Is there an additional PC perspective that needs to be reflected here? Include scheduled work, unscheduled work, or break out both? Are there other slices of priority information that would be interesting to have here? Scope Do we want to include priorities from subgroups as well as SIGs? What is the correct level of granularity? How do we ensure “orphaned” groups are accounted for? How do we capture different perspectives? Format Is it better to manage this in Jira or Confluence? If Jira, should we be tracking these priorities in PC Jira? Would it be better to do top 3? What is the best way to collate priorities - by SIG, by app, or something else?

Sources

Acquisitions

Metadata Management

Metadata Management Road Map → For a list of the top 5 anticipated features by votes, see the gadget Open and not Planned Metadata Management Features.

https://folio-org.atlassian.net/wiki/spaces/MM/pages/716243025

App Interaction | Cross App

https://folio-org.atlassian.net/wiki/spaces/AppInt/pages/712245249

https://folio-org.atlassian.net/jira/dashboards/10270 (Did not work for me - may need to be rebuilt or need permission tweak)

ERM

ERM SIG topics | Jira ranking: https://folio-org.atlassian.net/jira/dashboards/11004
ERM Roadmap | Jira: https://folio-org.atlassian.net/jira/dashboards/10323
ERM SIG implementers' topics | Confluence: https://folio-org.atlassian.net/wiki/spaces/ERMSIG/pages/5374024
ERM Bienenvolk Trillium Dashboard | Jira: https://folio-org.atlassian.net/jira/dashboards/10503

Bulk Edit

high level roadmap

Lists App

High level roadmap

Reporting

See Metadb Project Issues Log

Data Export

https://folio-org.atlassian.net/browse/ROAD-65

SIGs Not Yet Reflected Here

SIG NAME	SIG Convenor(s)	PC Liaison

SIG NAME	SIG Convenor(s)	PC Liaison
Consortia SIG	Lucy Harrison & Vivian Gould	Lucy Harrison
Documentation Working Group	Ludwig Liebl	Martina Tumulla
Open Access SIG	Martin Bauschmann	Alexis Manheim
System Operations and Management SIG	Ingolf Kuss	Ingolf Kuss
Support SIG	Anya & Debra Howell	Charlotte Whitt
User Management	Maura Byrne	Maura Byrne
Workflow SIG

Pilot Community Priorities Dashboard (2025-6)