| Issue Number | 719 |
|---|---|
| Summary | Use fresh XML from NLM for the EBMS migration |
| Created | 2023-01-31 08:23:55 |
| Issue Type | Improvement |
| Submitted By | Kline, Bob (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2023-02-04 14:47:55 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.337581 |
The current migration code maintains a set of XML for the articles which mirrors what is in production. However, now that we realize how far out of date our article XML has fallen (due to bugs in the NLM APIs; see OCEEBMS-687), we need to perform the migration using up-to-date XML, in order to prevent the first scheduled refresh job from being overwhelmed. So I will replace the code which keeps our mirror set of XML in sync with production with code which uses the latest XML from PubMed. Of course, for those articles which NLM has "disappeared" we will fall back on using the XML we already have in production (as we always have).
This is basically the same approach we used when we first migrated the CIteMS system to the new EBMS ten years ago (by the way, the 10-year anniversary—March 18—is approaching quickly 😉).
The software which collects and updates the set of article XML to be used for the migration has been modified to work around the bugs in the NLM APIs.
Elapsed: 0:00:00.000823