ACDHIJKLMNOPQRSTUVWXYZAA
1
Idea/InitiativeRevised ThemeTopic/ThemeNotesPriority level
4
Logging/Audit History - affects all appsAudit functionalityarchitecture
5
Consortia SupportConsortiaconsortia
6
Define cross-tenant architecture to be used by FOLIOConsortiaconsortia
7
Support cross-tenant architecture and functionality that enables consortia using multiple tenantsConsortiaconsortia
9
User preferences to make FOLIO more individual - saving personal templates, internationalization, accessibility, Inventory view (circulation vs. metadata management)Customization customization
10
Custom item statusesCustomization workflows
11
Data Import - Finish, reconfigure? Architectual problems? Data importdata import
21
Copying but not syncing of records - need source of truth, single-source record, data integrity - need system to keep consistency of dataData integrityarchitecture
25
Record LockingData integrityarchitectureData integrity?
26
Provide sufficient documentation for implementers to set up and configure functional appsDocumentationdocumentationData integrity?
27
Improvements to documentationDocumentationdocumentation
29
Develop and maintain API documentationDocumentationTW: Need to be more specific.
30
Clearly document library requirements for performance - e.g. 2 second response time for page loads, batch upload of 10,000 MARC records in 3 minutes, etc. and secure realizationDocumentationperformance/stability
32
Clearly document the library requirements for stability (Mean Time Between Failures [MTBF], Mean Time To Repair [MTTR]) and secure realizationDocumentationperformance/stabilityTW: If I'm reading this correctly, the first step is documenting what is needed.
34
App store - plug-ins - for sharing low-barrier community developed optionsExtensibility
extensibility (app store/sharing)
TW: If I'm reading this correctly, the first step is documenting what is needed.
37
Internationalization - timezones, multiple currencies per tenant, etc...InternationalizationI18n
38
Develop support for non-MARC record-based data models (for instance: Dublin Core, VRAcore, PBCore, FGDC), linked open data, etc.MetadatametadataTW: What is the current status of this?
45
User management of permissions Permissionspermissions management
48
DashboardsWorkflowspersonalization/workflowTW: Needs fleshing out.
55
Privacy and features for anonymizing user dataPrivacyprivacy
56
Make sure features fit the "definition of done." E.g., records need to allow for CRUD (like tags should be deleted)QAQA
57
Support and sustain continuing development of reporting features in the service of libraries, e.g. the inclusion of institutional data and other data setsReportingreporting
58
Promote and illustrate the capability for an institution to move between hosting environments (including to/from self-hosting) and change support providersSoftware packagingarchitecturePackaging?
59
Best Practices - developing semi-annual review of technology and migrations to new technologyTechnology planbest practicesTechnology plan
61
Release scheduling - new features, clean-up (Bug fixes, update to new architecture, etc...)Technology planbest practicesTechnology plan
62
Common practices across modules - lists, user experience, bringing in new technology is being done by individual development teamsUI consistencybest practices
70
Workflow app/appsWorkflowsworkflows
71
Notifications - external to users - messaging to library user, vendor, etc...Workflowsworkflows/communication
72
Notifications - internal - "here is something you need to do in FOLIO"Workflowsworkflows/dashboard
73
Template for a FOLIO module - serves as example of best practices - fits with contributed code requirements, definition of donebest practices/onboardingTW: I don't think I understand this.
74
75
76
77
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156