GitLab

Context

The backend development to support book versions is in progress. See Book versions epic for full proposal. This issue describes the related changes and additions to the frontend. See Figma here.

Design

The order of priority:

1. New version button and modal (@shubtiwari) (Due: Friday 24 June) !933
2. Amendments to new book and Book settings (@shubtiwari !936)
3. Amendments to Book manager page ( @danjela )
4. Amendments to Dashboard and collection manager (@shubtiwari) !935

New book step

"Content type" is used for the version name.

Tasks:

• Rename "Funded content type" to "Content type"
• change tooltip text to: The content type released to Bookshelf
• Add "Final full-text" to the "Content type" dropdown
• Make "Content type" a required field in the form
• Allow users to select any of the Conversion workflow options when "Final full-text" is selected

Book settings

"Content type" should always display in Book settings. It is disabled after book creation and cannot be changed by any user.

Tasks:

• Display content type in Book settings (inactive)

Wholebook book manager

The following design applies to wholebooks only. I.e. the PDF and XML workflow

Tasks:

• move Metadata form from modal to tab
• move Settings form from modal to tab
• move Team selection from modal to tab
• Add "New version" button. This is only active when the book status = Published
• Add the dropdown to show the version name and number, and allow users to change between versions

New version modal

Tasks:

• Create new modal for creating a new version of a book
• Version name options are the same values as content type
• Version number is an integer but may not follow in sequence
• Conversion workflow only has PDF and XML (Word to be supported in later development phases)
• NCBI to provide body text

Dashboard

Tasks:

• Add version name and number to book row
• Realign Organization name in book row
• Apply these same changes to book rows in the Collection manager page

Implementation (if applicable)

[A description of the steps to implement the feature.]

Alternative approaches (if applicable)

[Include any alternatives to meet this use case.]

Open issues (if applicable)

[Links to and a discussion of related issues, if applicable.]