Page Comparison

...

• Hotfix release experiences
• 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
• 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. 

Discussion items

...