Welcome to the FOLIO Wiki
Spaces
Apps
Templates
Create
Folio Development Teams
All content
Space settings
Shortcuts
How-to articles
How-to articles
This trigger is hidden
Retrospectives
Retrospectives
This trigger is hidden
Meeting notes (2)
Meeting notes (2)
This trigger is hidden
Product requirements
Product requirements
This trigger is hidden
File lists
File lists
This trigger is hidden
Content
Results will update as you type.
Meet the teams:
Aggies
aleph2folio team
Benevolence
Bienenvolk (former: ERM Team)
Citation Team
Core Platform team
Eureka Team
Eureka Development Team Processes
Support Documentation
Eureka - Spikes / Investigations
MODUSERSKC-4 Document process of user creation
MODSIDECAR-13: Options for handling modules which call OKAPI
Bridging the gap between Users in the system and Users of the system
Verify that Module Descriptor changes are backwards compatible
MODROLESKC-62: Spike - Should Keycloak resources be cleaned up when disabling applications w/ purge=true
Permissions naming convention
How to handle CapabilitySets which include Capabilities which may not be deflined yet.
EUREKA-89 Spike - Design solution for scheduled system calls
Spike - Investigate support for i18n in the capabilities grid
[DRAFT] Resources synchronization between modules and Keycloak during the application revoke
Spike - Investigate options for mod-scheduler handling changes in the system
APPDESCRIP-27 Spike - How to handle multiple implementations of the same interface
Authentication Logging
Spike - Revisit platform descriptors
MODROLESKC-215 Spike - Ability to rename capabilities
EUREKA-374 Spike - Identify problems preventing us from updating existing applications for Ramsons
Spike - Identify opportunities to split mega applications into smaller pieces
EUREKA-72: Investigate options consortia UI bundles
EUREKA-602 - Investigate improved capability management in various scenarios
MODSIDECAR-85 - Investigation into the sidecar's interaction with the AWS Parameter Store.
EUREKA-623 - Investigate cross-tenant query requests for modules that are not entitled across all tenants in the consortium.
EUREKA-631: Cross-tenant query requests for modules that are not entitled across all tenants in the consortium
Application Composition Plan
Eureka Sunflower Plans and Expectations
UI Dev/QA Environments, Config file
Architectural PoC Preview Feedback
Eureka Testing by QA
How to: Finding and using capabilities/sets for permissions for QA
Local deployment and development
Eureka - How to ...
Components
Eureka Early Adopter Program