Page contains key initiatives and issues that Firebird team takes/addresses to support and develop the functionalityFOLIO'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 | | |
Redissue | Noticed that two processes to fill instances table of mod OAI PMH module were created |
Perform analysis of the case| Verify if the issue can be recreated or if it was related to the client requesting the harvest | |
Jira| JIRA | | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-403 |
|---|
|
| Closed/ no longer occurs |
| 2 | | |
Redissue | Spike: Throttle Requests To mod-inventory-storage | 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 | |
Jira| JIRA | | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-400 |
|---|
|
|
|
| 3 | | |
Yellowtask | Prevent users from inadvertently triggering multiple full harvests | Limit of max initial concurrent oai-pmh requests for tenant | |
Jira| JIRA | | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-404 |
|---|
|
| Sprint 138 |
| 4 | | | Status |
|---|
| colour | Blue |
|---|
| title | initiative |
|---|
|
| Determine how many |
concurrent edge and mod-oai-pmh | the system can support before it crashes | Review available options, create required stories and prioritize the work | |
Jira| JIRA | | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | PERF-233 |
|---|
|
| PTF team: Sprint 137, Sprint 138 |
| 5 | | |
Redissue | 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 | |
Jira| JIRA | | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-383 |
|---|
|
|
|
| 6 | | | Status |
|---|
| |
|---|
| colour | Blue |
|---|
| title | Initiative |
|---|
|
| Investigate handling invalid XML characters in the library data | Prioritize the work described in MODIPMH-402 | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-396 |
|---|
|
|
|
| 7 | | | Implement handling invalid XML characters in the library data | Prioritize the work | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-402 |
|---|
|
|
|
| 8 | | | Performance testing for each release | Performance testing for the Lotus release | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | PERF-231 |
|---|
|
| PTF team, Sprint 137, Sprint 138 |
| 9 | | | Status |
|---|
| |
|---|
| colour | Blue |
|---|
| title | Initiative |
|---|
|
| Issues still occur. Need to carefully analyze the logs to have data for RCA | Perform analysis on the logs | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-405 |
|---|
|
| Sprint 137 |
| 10 | | |
issue |
|
| | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-407 |
|---|
|
| Sprint 138 |
| 11 | | |
|
| | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-406 |
|---|
|
| Sprint 138 |
| 12 | | | Collect mod-oai-pmh instances statistics |
| | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH-408 |
|---|
|
|
|
| 13 | | | Build API for harvesting statistics |
| |
Jira| JIRA | | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODOAIPMH- |
|---|
|
|
396