Reporting SIG Development Priorities

This page captures current FOLIO Jira issues and Metadb Project Issues that that the Reporting SIG has stated are priorities for software development to support FOLIO reporting. Github issues and Jira tickets related to reporting development can be curated and prioritized here. See the related Product Council’s Community Priorities Dashboard.

Notes

-for each issue, what is the priority?

-any issues or tickets missing?

-Should an issue be added for GDPR in Metadb? (Lauren developing scenarios)

keep history unanonymized
keep private data out of Metadb altogether (never synchronized into the Metadb tables); this was possible in LDP
keep data in metadb, but anonymized in both current and history when triggered in FOLIO

Priority	Topic	Issue	Notes

Priority	Topic	Issue	Notes
1	Data Anonymization: Support configurable data anonymization in Metadb software	https://github.com/metadb-project/metadb/issues/21 https://github.com/metadb-project/metadb/issues/89
1	Data Anonymization: Anonymization of Requests	UXPROD-1041 UXPROD-4302	FOLIO development of this feature likely to impact Metadb data
1	Data Anonymization: Address fees/fine issues related to various loan anonymization options	UXPROD-3659	FOLIO development of this feature likely to impact Metadb data
4	Reporting App Permissions	https://folio-org.atlassian.net/browse/UILDP-178 https://folio-org.atlassian.net/browse/UILDP-184	There are additional permissions coming with the Trillium release of FOLIO for the Reporting app.
4	Reporting App Permission Based on GitHub Repository Directory Access	[new Jira coming]	In the Reporting app Settings, adding the ability to restrict individual users to access Reporting App reports pointing to github/gitlab directories for different reporting functional areas (e.g., acquisitions)
2	In the marc _ _ t table, each instance ID should have a unique srs ID. The marc _ _ t table should include only records where the state field is 'ACTUAL,' but it is including records where the state field is 'OLD.' This results in multiple srs ID rows for one instance ID.	https://github.com/metadb-project/metadb/issues/92
2	Add primary keys to the tables without them (such as the instance_subject_source and instance_subject_type tables) in the Inventory App	https://folio-org.atlassian.net/browse/MODDATAIMP-1230	TAMU indicates this is not just triggered by Data Import App, they are seeing it triggerd elsewhere, too
3	Derived Table Updates, Maintenance, and Management