Progress review agenda 8 March 22
Hi @lathrops1 @Kireev @latternm @ErinS @deniskar
(cc @John.kopanas @danjela @ChristinaTromp @sidorelauku @bela @vignesh03 @andynicholson @Shanthi_B)
The main topic for today's meeting is reporting and resolving FTP submission error.
- I provided an update the main issue #438 yesterday. There I outline the entire process and provide a list of specific errors to handle. I've also increased the dev time estimate based on this updated scope.
- We discussed moving up FTP submission errors in the timeline because of some issues the NCBI team have reported in their testing.
- #804 -- Inconsistent behavior in permitting ingest of tagged XML from PDF. Please see the update to this issue and keep in mind that, with the approach outline there, it's not dependent on FTP submission error handing being developed.
- #542 -- Chapter Components should only be allowed one Bookshelf Display PDF. This is one use case that would be resolved by implementing #438
- Then we have two other features that should be considered in conjunction with the proposal in #438
- #571: integration: submitting XML source files to collections -- updated today
-
#569 (closed): XML workflow use case: Publishing a PDF-only version prior to XML -- commented today. This is needs review to assess where a check by
DOIfits in (this minimal case was propose as a workaround until the entire use case can be met)
Other than validating the approach to handing FTP submission errors, I think it's important for us to evaluate whether implementing this now is the right decision, considering the time it would add and the increased risk of delaying the first deployment. Of course we welcome any suggestions you may have to simplify or scale down the proposal.