Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

TimeItemWhoNotes
5WelcomeIngolf

Code of ConductIngolfThe FOLIO Code of Conduct has been endorsed by the Product Council .

Upgrading module-supplied reference dataWayne, group
  • upgrading a FOLIO system with loadReference=true as a tenantParameter
  • currently causes conflicts
  • solution might be to perform upgrades without loadReference=true

Small topicsIngolf
  • Harry signifies that someone from the Sys Ops SIG could join PO meetings and and discuss with the group the impact of certain decisions or lack of decisions  that impact the people that must support FOLIO in the library. There is no need to attend each PO meeting. - Volunteers ?
  • E-Mail support / SMTP support - does this work, has this been tested ?

Yes, this has been implemented in Italy (National Library of Florence), at IndexData and at TAMU.

It uses a standard SMTP setup. Needs an SMTP server. Better with SSL support. Italy uses Postman.

At IndexData, they are using Amazon SES, an SMTP Service.

At TAMU, there is a Campus SMTP. One needs to post JSON-Documents to it. Here's documentation about TAMU's E-Mail configuration: https://github.com/folio-org/folio-install/blob/kube-rancher/alternative-install/kubernetes-rancher/TAMU/deploy-jobs/create-email/create-email-config.sh

https://github.com/folio-org/folio-install/blob/kube-rancher/alternative-install/kubernetes-rancher/TAMU/deploy-jobs/create-email/Readme.md

  • Delete or edit (e.g. translate) pre-defined settings - for some settings that does not work. E.g. Settings - Inventory - Resource Types (not editable). But Settings - Inventory - ILL Policy: can edit and delete.

These settings are firm, not changeable. The source is RDA. This is by design.

If you want to translate, that's part of Internationalizaton. Knowledgeware has been working on this and gave a presentation in the Product Council just recently, on April 16th. Here is the link to the agenda & meeting notes of that day: https://docs.google.com/document/d/1puq9ySnP1RG583TOLDCh9hPZTBxSp4cJtZu_y-7W5hU/edit

And these are the messages in the chat of that day: https://docs.google.com/document/d/1Q3UQsXFjPhezViQ6UmJaHCihB8ZSf3QF8IpcPWayEeI/edit  

There should also be a recording of that meeting available.

Generally, questions like this are to be addressed to MM SIG, not to SysOps.

  • Upgrade path - is there a documentation ?

Topics for future meetings:


Report from Support SIG

Report about TC Architectural Blueprint / Strategic  Changes

Phil

Mike


Not before June.

...