Meeting Topic and Action Item Backlog - SysOps
This is a list of outstanding topics for the SysOps group
This is THE list. It replaces Action Items for Development. – Needs to be cross-referenced with Tech Council Request/Backlog Page .
SysOps Item-ID | Topic | Description | Date Added | Date Scheduled | Action | Jira | Status |
|---|---|---|---|---|---|---|---|
| Securing OKAPI, network topologies for deploying FOLIO
|
| 2019-04-12 |
| done |
|
|
| Docker security |
| 2019-04-12 |
|
|
| |
| Documentation on Docker modules | Documentation belongs a) in the README on github b) on dockerhub |
|
|
| There is a Ticket about that (Anton). Marc Stacy and David Crossley work on this. It is being worked on May/24/2019: FOLIO-2003 and FOLIO-2008. |
|
| Upgrading FOLIO: |
| 2019-04-12 |
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Dependency resolution
| CLI / UI for dependency resolution. An Okapi administrative tool. | 2019-04-12 |
|
| Worked on in Kubernetes / Orchestration working group. - Okapi admin tool is not yet being touched on. - Stripes has a CLI now; works for Okapi in part also. |
|
| Need common tools to get FOLIO up and running |
| 2019-04-12 |
|
| https://folio-org.atlassian.net/browse/UXPROD-1083 UXPROD-748 - Operational Maintenance Open
|
|
| Tenant management
|
| 2019-04-12 |
|
|
|
|
| External integrations
|
| 2019-04-12 |
|
| https://folio-org.atlassian.net/browse/UXPROD-347 UXPROD-211 |
|
| Reporting |
|
|
|
|
| |
| Re-write LS-Tools | LS-Tools = A tool set at Cornell which allows technical services do library automation tasks through a common web interface. It is essentially an ETL tool. It comprises cleanup jobs, export and import jobs. There is a specification written for each job that describes who owns it, how it is executed, what is needed, etc. The app also allows for searching of marc data with a highly granular selection capability. The app is a swiss army knife of technical services activities. It has meant a huge increase in productivity for technical services staff. Re-implementing this in Folio will be a challenge. Some combination of the workflow engine and the marc batch loader could replace LS tools. The workflow engine is meant to be a platform to build these kinds of applications on. |
|
|
| Robbie / Greg and Phil will look at it |
|
| UUID-issue | https://discuss.folio.org/t/on-primary-identifiers-in-folio/1826 Functional requirements: We need human readable identifiers. Eye-readable. Can be read on the phone. It has to accept legacy IDs. New records do not have to be compatible with the legacy identifiers. Preferred: Sequential identifiers. Sequential identifiers are related to the legacy identifiers. They leverage existing IDs by sequential numbers. It doesn't make sense to fix it after having gone live. |
|
|
| We have them for the inventory app. Jira UIIN-435 |
|
|
| Standards / Requirements for module instrumentation. Being able to see what is going on in a given module for debugging, performance analysis. |
|
|
|
| |
|
| Bootstrapping tool that
A script. Might be consolidated into a single administrative toolkit. Right now, there is a perl script. Need to be a pushed-button thing. |
|
|
|
|
|
Missing Documentation and Information
Information | Date Added | Action |
|---|---|---|
Okapi documentation is outdated |
|
|
No technical overview of how data flows through FOLIO, closest is the single server documentation |
|
|
|
|
|
|
|
|
|
|
|