NCBI testing release 7 June
@lathrops1 the NCBI testing site has been updated.
Development in this release
This release includes:
- Separating the action of uploading files and sending these files to conversion.
- Developing bulk upload of files for XML and PDF chapter-processed books
- Amendments to the files UI
- Amendments to the Create Book step to allow for submissions to the same book from the UI and FTP
- Creating and assigning the BCMS ID
- Submitting XML chapters to conversion via the UI
- Assigning Sys admin role to a user
- Assigning Sys admins to Organizations
- Assigning the role PDF2XML vendor role to a user
- Email notification in all uses cases highlighted in Green in #511
- The PDF2XML vendor issues tab (excluding the functionality of @mentions)
The related issues are labelled release-20210607.
- We had to delay the release of XML wholebook processing due to the use case of multiple source files which requires changes to how file statuses are tracked and how errors are reported. I will detail this is a separate issue.
- We delayed release of FTP submissions for XML chapters because we couldn't complete our testing due to this blocker (#505 (closed)). We'll resume our testing of this use case tomorrow.
- There will be updates to the "In review" workflow so it's best to wait for this before testing books that require approval.
- While you can test Publishing as previously (no changes have been made here), it's best to wait for integrated dev in (#435 and #481).
Testing use cases
These use cases are ready for testing. You can use the existing Organizations that have already been set up or create new ones. It's best to sign up at least a Sys admin, Org admin, and an Editor with real email addresses before testing.
Apply sys admin or PDF2XML vendor role
User signs up
User lets super admin know he has signed up
Super admin goes to 'All users' page
Super admin clicks on user and applies role:
- Sys admin OR
- PDF2XML vendor
Once a user has sys admin role she can be assigned to one or more existing organizations.
Create book in Organization (all types of books)
- Create any type of book in the Org
- See book created with New book status
- Get notification with BCMS ID
Upload and process chapters in Word and XML workflows
From the UI:
- Bulk upload chapters
- Upload any necessary suppl, images and Bookshelf display PDFs
- Submit content for conversion
- Receive email notification when content is Previewing or returns Errors
- Discuss Preview or Errors with assigned team members and receive emails for @mentions.
Question for dev go-ahead
- In which use cases should "submit" be blocked?
Users should only be able to perform this action when it makes sense to do so. As done with other buttons, the "Submit" button should only be active when relevant. Here are the use cases where I think this action shouldn't be allowed.
Submit buttons is inactive when:
- there are no files to submit (i.e. book status = New Book)
- The file status does not = New Upload
- Block TOC ordering during New Upload state
At the moment we block moving components on the book manager when status = Converting or Loading Preview because their correct placement in Front/Body/Back is determined by the
content-type, read from the converted xml file.
Now that we have the status New Upload, the same logic should apply. We have not made this change however since we'll work on everything to do with TOCs in one cycle.
- Block 'request review' when status is New Upload
Users shouldn't be able to request a review because there is no content available on the preview tab
Please check the existing bugs before reporting any issues, and provide sufficient information on incorrect and expected behaviour.