Hardening of OAI-PMH
- Denis
- Magda Zacharska
| Stakeholders |
|---|
PO - Magda Zacharska SA - Mikhail Fokanov |
FOLIO's implementation of OAI-PMH was developed with a requirement that the full inventory harvest is a rare event, done once or twice a year. The full harvest should be supported by incremental harvests that can be scheduled on a daily basis to make sure all the inventory changes are included in the library's catalogs. However, in production we see that the full harvests are triggered multiple times during a day, sometimes concurrently, sometimes inadvertently. The purpose of this page is to list the proposed initiatives and stories that will allow to harden OAI-PMH implementation and make it more robust.
Table
| # | Date | Type | Details | Plan / Action items | Jira | Status/Timeline |
|---|---|---|---|---|---|---|
| 1 |
| STORY | Noticed that two processes to fill instances table of mod OAI PMH module were created | Verify if the issue can be recreated or if it was related to the client requesting the harvest | MODOAIPMH-403 - Getting issue details... STATUS | Closed/ no longer occurs |
| 2 |
| INITIATIVE | Investigate possible ways to limit impact of the full harvest on inventory and SRS storage | Review available options, create required stories and prioritize the work | MODOAIPMH-400 - Getting issue details... STATUS | |
| 3 |
| STORY | Prevent users from inadvertently triggering multiple full harvests | Limit of max initial concurrent oai-pmh requests for tenant | MODOAIPMH-404 - Getting issue details... STATUS | Sprint 138 |
| 4 |
| INITIATIVE | Determine how many full harvests the system can support before it crashes | Review available options, create required stories and prioritize the work | PERF-233 - Getting issue details... STATUS | PTF team: Sprint 137, Sprint 138 |
| 5 |
| INITIATIVE | Perform analysis for the case when handling client waits while oai-pmh searching for instances with underlying records | Review available options, create required stories and prioritize the work | MODOAIPMH-383 - Getting issue details... STATUS | |
| 6 |
| INITIATIVE | Investigate handling invalid XML characters in the library data | Prioritize the work described in MODIPMH-402 | MODOAIPMH-396 - Getting issue details... STATUS | |
| 7 |
| STORY | Implement handling invalid XML characters in the library data | Prioritize the work | MODOAIPMH-402 - Getting issue details... STATUS | |
| 8 | STORY | Performance testing for each release | Performance testing for the Lotus release | PERF-231 - Getting issue details... STATUS | PTF team, Sprint 137, Sprint 138 | |
| 9 |
| INITIATIVE | Issues still occur. Need to carefully analyze the logs to have data for RCA | Perform analysis on the logs | MODOAIPMH-405 - Getting issue details... STATUS | Sprint 137 |
| 10 |
| BUG | MODOAIPMH-407 - Getting issue details... STATUS | Sprint 138 | ||
| 11 |
| BUG | MODOAIPMH-406 - Getting issue details... STATUS | Sprint 138 | ||
| 12 |
| STORY | Collect mod-oai-pmh instances statistics | MODOAIPMH-408 - Getting issue details... STATUS | ||
| 13 |
| STORY | Build API for harvesting statistics | MODOAIPMH-412 - Getting issue details... STATUS | Sprint 138 |