Progress review 5 Oct
Hi @lathrops1 @Kireev @deniskar @ErinS
cc @John.kopanas @yannis @adam
Agenda
- Current cycle
- Next release for NCBI testing
- Items on hold
- Key issues to resolve
- Upcoming cycle
Current cycle
The following development items have been completed and tested by the Coko team within this cycle.
Issue ID | URL | Title | State | Milestone | Epic ID | Epic Title |
---|---|---|---|---|---|---|
703 | #703 (closed) | Part modal versus part page and navigating through books with parts | Closed | Sept 02 | &33 | TOCS parts |
373 | #373 (closed) | Collections created as PDF or XML supplied ones appear on dashboard incorrectly with Word icon | Closed | Sept 02 | &44 (closed) | Create collection |
712 | #712 (closed) | Show collection status | Closed | Sept 02 | &44 (closed) | Create collection |
713 | #713 (closed) | Add source icon for collection based on collection members | Closed | Sept 02 | &44 (closed) | Create collection |
598 | #598 (closed) | Different versions of a file aren't sorted together in "show history" | Closed | Sept 02 | &42 (closed) | FM Tracking |
715 | #715 (closed) | updated folder names in dowloaded packaged to match folders in Apex/PDF conversion | Closed | Sept 02 | &41 (closed) | FM Download |
714 | #714 (closed) | Files from converted package (PDF conversion) are duplicated in UI | Closed | Sept 02 | &32 (closed) | PDF (book and chapter) integration |
539 | #539 (closed) | Preview tab lacks notice to check errors after Load to PMC | Closed | Sept 02 | &26 (closed) | Errors management |
716 | #716 (closed) | BCMS status indicates "New Upload" although NCBI Word2XML conversion passed and a load to PMC session completed with Preview displaying in BCMS | Closed | Sept 02 | ||
717 | #717 (closed) | BCMS component status and latest source file status are inaccurate | Closed | Sept 02 | ||
718 | #718 (closed) | Converted files not ingested to BCMS and sent to Load to PMC | Closed | Sept 02 |
These additional dev items, which all relate to the Settings Templates, have been completed on a separate branch and deployed for my review.
The process required before this development can be released for NCBI's testing involves:
- My review of each dev item
- We may choose to do demos to NCBI team to resolve small queries
- My feedback to our team with potential fixes to be made
- Code review and substantial testing before this branch can be merged
Issue ID | URL | Title | State | Milestone | Epic ID | Epic Title |
---|---|---|---|---|---|---|
114 | #114 (closed) | Lock sensitive settings after book is created | Open | Sept 02 | &34 (closed) | Setting: Org templates |
390 | #390 (closed) | Create, update, apply an Organization settings template | Open | Sept 02 | &34 (closed) | Setting: Org templates |
428 | #428 (closed) | book settings changes | Open | Sept 02 | &34 (closed) | Setting: Org templates |
651 | #651 (closed) | Unable to fix settings errors | Open | Sept 02 | &34 (closed) | Setting: Org templates |
693 | #693 (closed) | Amendments to new book step 1 | Open | Sept 02 | &21 | Set up: Create Org, Collection, and Book |
726 | #726 (closed) | TOC Order Chapter By Setting Should be Required | Open | Sept 02 | &2 | Chapter-processed TOC management |
Next release for NCBI testing
- As requested we'll complete these issues related to chapter TOCs so that your team can continue with this testing: #702 (closed), #727 (closed), and #728 (closed).
- @lathrops1 also need a response to this in-progress issue: #631 (closed).
Items on hold
As discussed in mattermost, the issues related to large file submissions (#610 (closed), #716 (closed), #725 (closed)) are on hold until we have the sample packages to test with and answers to:
- What is the usual size of packages submitted by FTP and what is the MAX package size we should expect?
- Are file size validations needed for file types besides Supplementary and Review files to be up to 1 GBs?
Key issues to resolve
As discussed in the DDWG meeting yesterday, these are the key issues to finalise so that they can be scheduled for development:
- The creation of collection xml as raised by @latternm on #706 (comment 68755). For this our team needs a new issue that outlines the technical requirements of the collection xml and the expected integration for sending the collection xml. We're happy to propose a solution for this keeping in mind the current development and expected deadline, but it's important for us to understand NCBI's requirements first.
- The granthub integration in #433 (closed) -- this is close to being finalised, I will provide an updated design once we have an answer to #433 (comment 68500)
- The metadata spec in #678 (closed) -- this is with me to review and breakdown into smaller development tasks once we have a agreed on the general approach for this initial release.
Upcoming cycle
We will focus on these issues related to collections:
- #695 (closed) - Group books by custom group titles in the collection manager UI (currently in testing)
- #690 (closed) - Check collection Agreements when collection member is published (in-progress)
- #705 (closed) - Order book by metadata value in the collection manager UI (not started)
Until we have clarity on the key items above, it's difficult to confirm which other features can be completed in this cycle. I will update this list by COB Friday.
(Going forward I'll also do my best to provide this update on the Friday before our Progress review meetings)