NCBI testing release 22 Sept
This release completes development for the below user stories in the Chapter-processed TOCs epic. This has involves work on feautures, design improvements and bugs so I have groups all relevant issues here.
- Place and order chapters by 'Title A-Z' and 'chapter number' for Users Sys Admin, Org Admin and Editor to create a TOC in chapter-processed books that do not support parts in workflows Word and XML only.
- Let these users know when a chapter can't be placed in the order they have selected, so that they can fix the relevant chapter
- Create a toc.xml file that includes chapter and main section headings and metadata for pub-history, contributors, sub- and alt-titles when available.
These relate to the following User Stories:
Add and modify their preferred settings to build TOCs for chapter-processed books, including
- auto-sorting rules
- auto placing of components in correct structural unit of the book (front, body, back)
Ensure that there aren't any content changes to their current TOCs when their content is migrated and processed in the new BCMS workflows, including beyond their chosen settings, support for
- alpha indices if content is sorted alphabetically
- Save a toc package whenever a chapter gets published and send this to NCBI once a day.
This relates to following User Story:
Be able to coordinate the publication of TOCs when they are publishing multiple chapters / books a day, so there are not issues with loading ingests,
either through a manual on demand trigger orpreferred auto-build overnight cron jobs to coordinate with overnight Bookshelf indexing
(Note, this is partially tested as confirmed in this thread. Bear in mind that covers images won't display and if there are any issues in seeing the toc preview, as linked from the chapter preview, please review with Martin first as this may require a change on NCBI side.)
Work completed not included in this review
Since the last testing ticket (release-20210824) there have been a number of features, bugs and improvements completed and these are reflected on your site. However to align with the new testing process you've requested, I'm not including them here because they don't comprise full user stories that can be tested end-to-end.
So to improve our process going forward I'll group all closed issues that relate to a specific epic and give then a
test-date label (as done now).
Please let me know if you have any questions or feedback that can improve this.