The Q1-2020 Fameflower Hotfix release was released May 1st. Anton announced it.
Let's discuss our experiences with it so far.
Chris Creswell did a post in #sys-ops today:
The hotfix application worked smoothly in his development environment, then not so smoothly on his shared local test instance.
A few modules reported errors when enabling, but his script to enable modules actually tries twice for each module, and the second time it worked for each.
Okapi reports the expected module versions enabled for jis tenant, and everything seems to work as he clicks around in the UI.
But he does wonder if the second attempt at enabling the modules did any of the database schema updates or not.
He is going to use a check_postgres script that he found to compare the schemas between his development environment and their test instance to see if anything is different.
Jason reports some failures of the schema update scripts on the TAMU tenants.
His first run at the migration from Q4 to Q1 Hotfix seems to have been successful for the Diku tenant where he has reference and sample data loaded.
Updating the TAMU tenant failed.
Historical circulation migration data is getting difficult. Across FOLIO versions, migrations have not worked. Getting history from Voyager is getting more difficult. Important to current and existing libraries.
A problem for historical open and closed loans data. Some libraries may decide to not transfer closed loans.
Difficult for migration and offline circulation!
Needed for reporting as well. Might be stored in a separate file.
No stories written for this.
How and when to suppress notices for migrated data? Saving tenant configuration util after migration seems to help. Or set to an invalid server.
ToDo: Discuss with PO team
25
SAML integration
Tod
SAML integration at Chicago
Mod-login SMAL is not federation aware. No way to get automatic updates. No self registering.
How can configurations be preserved between instances.
Federation support is really needed.
Want to release SAML attributes for actions in FOLIO.
A particular identity can be automatically authorized to login.
mod-SAML isn't actively maintained. Will be very important over the coming year and more.
It would be an advantage to FOLIO to have active dev in this area.
Apache has modules for being a provider. NGINX has a 3rd party tool for this as well. Could FOLIO rely on these tools for SAML authentication and attribute release. Would eliminate the need to maintain the FOLIO SAML code.
FOLIO would need to be able to consume the data from both modules.
ToDo: Need several tickets for this in JIRA. Tod will create the ticket.
Need a PO for this.
Should also look at who owns the patron user loader.
Need to do a better job of circling back on architecture changes such as searching, data stores, etc.