2020-05-15 - System Operations and Management SIG Agenda & Notes
Date
Attendees
- Christopher Creswell
- Johannes Drexl
- Former user (Deleted)
- spampell
- jroot
- Chris Rutledge
- Wayne Schneider
- Catherine Smith
- zeno.tajoli
- Brandon Tharp
Goals
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
5 | Welcome | Ingolf |
|
Code of Conduct | Ingolf | The FOLIO Code of Conduct has been endorsed by the Product Council . There will be CSVs - Community Service Volunteers - to enforce the regulations of the Conduct. | |
Upgrading module-supplied reference data | Wayne, group |
Blog post: https://app.slack.com/client/T1EPYQDAQ/C9BBWRCNB Current situation (Wayne):
Let's not discuss the failures. Question is What behavior do we want ?Zeno: Italy doesn't use "loadReferences" when they update (Ingolf)
Jason: At A&M, we do "loadReference" = false. Then there is the risk that some (new) reference data are missing and that some functionalities are not working, because of this. But this risk is small. It is an easily correctible risk. All: We need to define a harder boundary betweem reference data and sample data. The location should be sample data. We need to safeguard reference data against changes. Reference data = a default set of data which I can overlay. Wayne: We could work in stages. Put together (reference data in stages). But this will make migration tough. Tod: We can not solve the whole question in this meeting. Wayne will open a Discuss Post on migrating reference data. | |
Small topics | Ingolf |
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
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.
| |
diverse | 15,600 modules are being loaded (if one does a module pull with Okapi), 15 to 16 MB of data . There is a ticket for adding filtering capacities to /proxy/pull/modules : OKAPI-728 | ||
Topics for future meetings: | |||
Report from Support SIG Report about TC Architectural Blueprint / Strategic Changes | Phil Mike | Not before June. |