Progress review agenda 28 June 2022
Hi @lathrops1 @Kireev @latternm @ErinS @deniskar @douglassue @jordandc @jeffbeckncbi
(cc @John.kopanas @danjela @DioneMentis @sidorelauku @bela @vignesh03 @Shanthi_B @pokhi @shubtiwari)
Here is the agenda for the progress review meeting today. NCBI team please free to comment here if you want to discuss anything else today.
Book versions
Status update
Book versions work is going well, and we need to finalise the team specifications to keep it on track.
Teams and permissions
Can we proceed as proposed in last week's agenda, as is on the permissions sheet? i.e. The team for each new version functions like a new book team.
Release this week
We have been working on converted file validations and need confirmation of any new requirements before we do a release, since our work in progress on file validations has been paused and if released to you in it's current state, could cause blockers in NCBI's testing.
The following issues are staged for release, 5 of which were targeted in the MVP deployment priorities, and the rest of which have been finalised while prioritisation was still under way:
URL | Title |
---|---|
#842 (closed) | Unable to move an existing book to a collection it belongs |
#976 (closed) | Books part of a group in a collection, if moved to another collection creates duplicate |
#1176 (closed) | Unable to upload xml file to converted xml folder because extension is not allowed |
#1183 (closed) | "Agreements Check 1: An Error occurred failed" when reloading TOC in NCBI-managed migration dev site |
#1217 (closed) | Collection source type is not saved correctly |
#1228 (closed) | editor is unable to upload new chapters in ch based book |
#1231 (closed) | publication date allows unusual syntax |
#1234 (closed) | Collection with books inside custom groups have blank page |
#1235 (closed) | "Agreements Check 1: An Error occurred failed" when publishing collection TOC in NCBI-managed migration dev site |
#1240 (closed) | Number counts on open issues for PDF chapters WF is not correct |
#1250 (closed) | Blank page: Clicking on previous versions for chapter-processed books |
#1262 (closed) | Collection metadata updates can't be saved |
File name validations
Can we proceed without filenaming validations on PDF and XML converted files for wholebooks, as per the current specifications?
What further changes to specifications are expected from NCBI for file validations? We haven't accounted for further changes in the MVP schedule so I want to assess what effect that would have on the schedule.
Collaborative focus for this period
We will need to refine details on MVP issues over the next few weeks and will be consulting NCBI team members as needed. We have 43 open MVP issues and 23 days before release.
I want to sharpen our focus on MVP issues only, Ideal targets and our ultimate goals are extremely important, as well as communications to set expectations with submitters about when their content can be supported, but we need to focus on this next step to achieve a first deployment, and then plan further development.
To assist with this focus I've created an 'MVP deployment' label, and you can filter by the MVP label to see all the features and changes targeted for the MVP deployment at the end of July.