ncbi issues
https://gitlab.coko.foundation/ncbi/ncbi/-/issues
2022-03-14T05:24:32Z
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/1013
uncaughtException: could not read message SyntaxError: Unexpected end of JSON...
2022-03-14T05:24:32Z
Andy Nicholson
uncaughtException: could not read message SyntaxError: Unexpected end of JSON input
```
server_1 | 2022-02-10T00:21:08.340Z - info: Saved ActivityLog with UUID 2e3e0f7a-e3be-44f6-8a17-582a67425406
server_1 | 2022-02-10T00:21:08.340Z - info: kafka Got Message from ncbi server topic: submit_apex_package_receip...
```
server_1 | 2022-02-10T00:21:08.340Z - info: Saved ActivityLog with UUID 2e3e0f7a-e3be-44f6-8a17-582a67425406
server_1 | 2022-02-10T00:21:08.340Z - info: kafka Got Message from ncbi server topic: submit_apex_package_receipt data: {"session_id": "11809952", "status": 0, "timestamp": "2022-02-08 03:10:09", "package": "APEX/bcms3315.bcms3315.2022_02_08.zip", "publisher": "", "book": "bcms3315", "job_id": "xzy", "notices":[]
server_1 | 2022-02-10T00:21:08.340Z - info: kafka Couldn't Parsed Message {} message: {"session_id": "11809952", "status": 0, "timestamp": "2022-02-08 03:10:09", "package": "APEX/bcms3315.bcms3315.2022_02_08.zip", "publisher": "", "book": "bcms3315", "job_id": "xzy", "notices":[]
server_1 | 2022-02-10T00:21:08.345Z - error: uncaughtException: could not read message SyntaxError: Unexpected end of JSON input
server_1 | {
server_1 | date: 'Thu Feb 10 2022 00:21:08 GMT+0000 (Coordinated Universal Time)',
server_1 | process: {
server_1 | pid: 168,
server_1 | uid: 1000,
server_1 | gid: 1000,
server_1 | cwd: '/home/node/app',
server_1 | execPath: '/usr/local/bin/node',
server_1 | version: 'v16.13.2',
server_1 | argv: [ '/usr/local/bin/node', '/home/node/app/startServer.js' ],
server_1 | memoryUsage: {
server_1 | rss: 139440128,
server_1 | heapTotal: 52924416,
server_1 | heapUsed: 50289216,
server_1 | external: 1227306,
server_1 | arrayBuffers: 187709
server_1 | }
server_1 | },
server_1 | os: { loadavg: [ 0.24, 0.47, 0.69 ], uptime: 6979083.39 },
server_1 | trace: [
server_1 | {
server_1 | column: 13,
server_1 | file: '/home/node/app/server/services/handleNcbiMessage/ncbiParse.js',
server_1 | function: 'NcbiParse.parseMessage',
server_1 | line: 33,
server_1 | method: 'parseMessage',
server_1 | native: false
server_1 | },
server_1 | {
server_1 | column: 46,
server_1 | file: '/home/node/app/server/services/kafkaService/StreamConsumer.js',
server_1 | function: null,
server_1 | line: 148,
server_1 | method: null,
server_1 | native: false
server_1 | },
server_1 | {
server_1 | column: 5,
server_1 | file: 'node:internal/process/task_queues',
server_1 | function: 'processTicksAndRejections',
server_1 | line: 96,
server_1 | method: null,
server_1 | native: false
server_1 | }
server_1 | ],
server_1 | stack: [
server_1 | 'Error: could not read message SyntaxError: Unexpected end of JSON input',
server_1 | ' at NcbiParse.parseMessage (/home/node/app/server/services/handleNcbiMessage/ncbiParse.js:33:13)',
server_1 | ' at Consumers.ConsumerStream.<anonymous> (/home/node/app/server/services/kafkaService/StreamConsumer.js:148:46)',
server_1 | ' at processTicksAndRejections (node:internal/process/task_queues:96:5)'
server_1 | ]
server_1 | }
server_1 | [nodemon] app crashed - waiting for file changes before starting...
```
Andy Nicholson
Giannis Kopanas
jkopanas@gmail.com
Andy Nicholson
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/969
Display heading level setting is not get inherited from NCBI clone domains
2022-05-27T10:05:44Z
Stacy Lathrop
Display heading level setting is not get inherited from NCBI clone domains
## Expected behaviour
All domain attribute settings from NCBI clone domains should be inherited from any book created using that clone
Heading fields should be required.
## Current behaviour
Some domain attributes settings are no lo...
## Expected behaviour
All domain attribute settings from NCBI clone domains should be inherited from any book created using that clone
Heading fields should be required.
## Current behaviour
Some domain attributes settings are no longer getting inherited from NCBI clone domains
Able to save heading fields with empty values.
## Steps to reproduce
Chapter processed
See: ![image](/uploads/4a31b9461de38a40ff2ed4ae845c4b30/image.png)
https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/dfaba29d-ed34-4422-9525-dd4a677979e7
Book processed
See: ![image](/uploads/8dc387f82515e3f260a02552af4c53dd/image.png)
## Priority
Need to test further if it calls NCBI Bookshelf issues if left empty and if other fields are now broken.
Dione Mentis
dione@coko.foundation
Dione Mentis
dione@coko.foundation
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/956
Editor access and permissions on collections and its members
2024-01-16T18:22:59Z
Dione Mentis
dione@coko.foundation
Editor access and permissions on collections and its members
## Context
As confirmed in https://gitlab.coko.foundation/ncbi/ncbi/-/issues/832#note_74879
As with any book, relevant team members should be added to the collection to give them access. Roles that need access
- Editors
- Previewers...
## Context
As confirmed in https://gitlab.coko.foundation/ncbi/ncbi/-/issues/832#note_74879
As with any book, relevant team members should be added to the collection to give them access. Roles that need access
- Editors
- Previewers (unclear at this stage)
## Proposal
Follow same approach as books
- team button open team modal
- Sys admin or Org admin adds 'Editor' users from the Organisation to the collection
Questions:
- What actions can the editor take at collection level?
- what actions can't the editor take at collection level?
- If Editor has access to collection, should they automatically get Editor access to all the books in the collection?
## Design
Same teams component as books
![Screenshot_2022-01-07_at_08.59.37](/uploads/02153f7c413b1bd6e5b7a46dc18d9e7c/Screenshot_2022-01-07_at_08.59.37.png)
## 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.]
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/954
Improve alternative title field in book metadata UI(s)
2024-01-16T18:33:51Z
Stacy Lathrop
Improve alternative title field in book metadata UI(s)
cc @ErinS @jordandc -
Per #936 - **before we onboard external users to BCMS beyond our current CMS user base**__, we need to improve the alternative title field in the book metadata UI(s).
To do so, we should look what attribute types...
cc @ErinS @jordandc -
Per #936 - **before we onboard external users to BCMS beyond our current CMS user base**__, we need to improve the alternative title field in the book metadata UI(s).
To do so, we should look what attribute types we support, what we are doing with this, how to communicate and support that in the UI without confusion or introducing quality issues.
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/952
Book title cut off on main dashboard
2022-06-10T20:08:40Z
Stacy Lathrop
Book title cut off on main dashboard
## Expected behaviour
Should be able to see entire title on Bookmanager page
## Current behaviour
Some titles are not appearing in full
## Steps to reproduce
For example, search from main dashboard for - bcms233
![image](/uploads/...
## Expected behaviour
Should be able to see entire title on Bookmanager page
## Current behaviour
Some titles are not appearing in full
## Steps to reproduce
For example, search from main dashboard for - bcms233
![image](/uploads/a4067b3094167c83fb1e9cfdacf1c8bd/image.png)
Compare to title on book landing page:
https://ncbi.cloud68.co/organizations/099273a1-565e-4085-b0d6-55b5a0392e3f/bookmanager/6a37b90b-7ce8-49d9-a7dc-fcaba54dca0b/894c0488-f252-4383-8c06-ed2973d731ed
![image](/uploads/99478c52968971d8cac4f7a607974a54/image.png)
Priority for onboarding external users
### QA Steps
1. Create a book and add a long title, like for example: ```test book - Autologous chondrocyte implantation in the knee joint11Translation of Chapters 1 to 6 of the final report N19-02 Autologe Chondrozytenimplantation am Kniegelenk (Version 1.1; Status: 3 November 2020 [German original], 01 April 2021 [English translation]). Please note: This document is provided as a service by IQWiG to English-language readers. However, solely the German original text is absolutely authoritative and legally binding.```
2. Save the book
3. Check in the main dashboard the book title should be fully visible
4. Check organization books and collection page (where this book belongs) the title should be fully visible
5. Move to the next page in pagination, to see that the rows there appear normal as well.
2022-Apr-A
ChristinaTromp
ChristinaTromp
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/933
Read OA status from converted file and add to PDF and XML wholebook metadata
2024-01-16T18:33:54Z
Erin Schmieder
Read OA status from converted file and add to PDF and XML wholebook metadata
## Requested behaviour
PDF and XML wholebook metadata should show the following fields: Copyright Statement, Open Access License, Creative Commons License Type, and License statement, read from the converted file.
When a user uploads ...
## Requested behaviour
PDF and XML wholebook metadata should show the following fields: Copyright Statement, Open Access License, Creative Commons License Type, and License statement, read from the converted file.
When a user uploads a converted file or when a converted file is received, these values are updated in the Metadata UI and are read only. The Open Access status is not kept in sync with the Open Access status in Settings. As per the [BITS specifications](https://jats.nlm.nih.gov/extensions/bits/tag-library/2.1/element/license.html), if we receive a converted XML file with `license-type="open-access"` in the `<license>` section, we will display the toggle as on. In all other cases (where we don't receive that value at all, or receive a different value) we will leave the toggle off.
```
...
<book-meta>
<book-id>...</book-id>
...
<pub-history>...</pub-history>
<permissions>
<copyright-statement>Copyright: © 2004 Eichenberger
et al.</copyright-statement>
<copyright-year>2004</copyright-year>
<license license-type="open-access"
xlink:href="http://creativecommons.org/licenses/by/2.0/">
<license-p>This is an open-access article distributed under the
terms of the Creative Commons Attribution License, which permits
unrestricted use, distribution, and reproduction in any medium,
provided the original work is properly cited.</license-p>
</license>
</permissions>
<abstract>...</abstract>
</book-meta>
...
```
## Current behaviour
This field is not in the PDF and XML whole book metadata templates.
## Steps to reproduce
1. Open a PDF whole book
2. Open the metadata template for that book by clicking the metadata button in the upper right hand corner
3. Scroll down to look for the listed fields
4. The fields are not present
5. Repeat for XML whole books
## Environment
PC - Edge
## Possible solution
1. Ignore any entities (`<!ENTITY...>`) before the top-level <book> element as confirmed here: https://gitlab.coko.foundation/ncbi/ncbi/-/issues/933#note_95606
2. Read these values from converted XML for PDF and XML wholebooks.
3. Display read only values in Metadata UI for PDF and XML wholebooks.
## QA Steps
1. Create a PDF or XML whole book
2. Upload the converted file or submit the book for converting after uploading the required files.
3. Open the metadata template for that book by clicking the metadata button in the upper right hand corner (after receiving the converted file in the case you have submitted the book for conversion)
4. Scroll down to look for Permission session
5. Check that the fields in the permission are filled in accurately according to the converted file
## Priority
[Select "Y" for the relevant priority and provide an explanation]
1. Resolving this bug is required for migration (Y/N)
2. This can be prioritised after migration (Y/N)
@lathrops1
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/891
If book is Failed during Loading to Preview should only see Reload Preview bu...
2022-04-11T12:05:09Z
Stacy Lathrop
If book is Failed during Loading to Preview should only see Reload Preview button
cc @jordandc
## Expected behaviour
If a book is Failed during Loading to Preview user should only see Reload Preview button to retrigger the loading
## Current behaviour
If a book is Failed during Loading Preview user sees both the ...
cc @jordandc
## Expected behaviour
If a book is Failed during Loading to Preview user should only see Reload Preview button to retrigger the loading
## Current behaviour
If a book is Failed during Loading Preview user sees both the Reload Preview and Submit buttons and doesn't know what to do
## Steps to reproduce
See: https://ncbi.cloud68.co/organizations/32d78686-4b9a-46af-b52a-f5d0c4052177/bookmanager/4796f4f3-edf8-4d09-adea-385bbbbb412d/78510388-9849-4cb7-a6ac-2dad802d39e3
![image](/uploads/2af3a557d0049221f7e8462d0807f9f1/image.png)
## Priority
Not for migration, but yes for deployment
Dione Mentis
dione@coko.foundation
ChristinaTromp
Dione Mentis
dione@coko.foundation
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/880
Published link of TOC not displaying
2024-01-16T18:22:59Z
Stacy Lathrop
Published link of TOC not displaying
## Expected behaviour
The final published link Bookshelf URL does not display on the TOC BCMS page. I know we asked that it be added during a review, but then I don't see it in the last mockups. It isn't critical for deployment, but we...
## Expected behaviour
The final published link Bookshelf URL does not display on the TOC BCMS page. I know we asked that it be added during a review, but then I don't see it in the last mockups. It isn't critical for deployment, but we do want it, because if someone copies and pastes the BCMS one it isn't always viewable, whereas the live version would be.
## Current behaviour
Only have the BCMS preview URL.
## Steps to reproduce
See: https://ncbi.cloud68.co/organizations/9f638bd9-4226-4d99-a9fb-579dba128443/bookmanager/ae125988-a08e-4b1e-81da-9941995a1f51/toc/96c2f636-3c7a-411c-865c-01db585e6bef
## Priority
N - but would be good to have earlier when Bookshelf staff need to proxy publishers and need to send preview URLs they can see before being BCMS members
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/873
Improve links to PMC Task Manager for Bookshelf staff users
2022-10-09T12:52:33Z
Stacy Lathrop
Improve links to PMC Task Manager for Bookshelf staff users
## Context
Currently links to PMC Task Manager sessions are ONLY provided if there are error notifications recorded on an errors page. These links are visible to all users even though only Bookshelf staff can view them.
## Proposal
Ma...
## Context
Currently links to PMC Task Manager sessions are ONLY provided if there are error notifications recorded on an errors page. These links are visible to all users even though only Bookshelf staff can view them.
## Proposal
Make all PMC Task Manager session links visible ONLY to Bookshelf staff users.
Add PMC Task Manager session links for all active statuses that have a TM session near the status indicator, e.g.,:
- Converting
- Loading to Preview
- Publishing
This will become very useful to troubleshoot things like software issues and when Bookshelf staff have the ability to manually fail a job with such a problem.
## Design
TBD during scoping
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/871
Clearly label System Admin and Org Admin in User Tabs
2024-01-16T18:20:59Z
Stacy Lathrop
Clearly label System Admin and Org Admin in User Tabs
cc @jordandc
## Context
Users are not clear what kind of Admin a user is looking at User pages, so do not know what permissions they have and should be tested for / expected.
## Proposal
Clearly label System Admin and Org Admin by ...
cc @jordandc
## Context
Users are not clear what kind of Admin a user is looking at User pages, so do not know what permissions they have and should be tested for / expected.
## Proposal
Clearly label System Admin and Org Admin by those role labels.
## Design
![image](/uploads/17df1837d68bae57831b15d98f92795a/image.png)
Change Admin to Org Admin or System Admin - according to assigned role
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/869
If assign user as Sys Admin to an Org, they must also be / or be added as Sys...
2024-01-16T18:19:05Z
Stacy Lathrop
If assign user as Sys Admin to an Org, they must also be / or be added as Sys Admin at global BCMS level
cc @douglassue
## Expected behaviour
Should only be able to add Sys Admin to Org that are Sys Admin at global BCMS level
## Current behaviour
User is able to assign a user as sys admin at the org admin, but don't have any permission...
cc @douglassue
## Expected behaviour
Should only be able to add Sys Admin to Org that are Sys Admin at global BCMS level
## Current behaviour
User is able to assign a user as sys admin at the org admin, but don't have any permission to do anything at the org until they are added as sys admin at global bcms level causing confusion
## Steps to reproduce
1. Create Org
2. Add user as System Admin (that is not typed System Admin in global BCMS)
3. Try getting notificaitons, doing things, etc, at Org level
## Environment
Mac
## Priority
N, needed for onboarding external users
Sidorela Uku
Sidorela Uku
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/863
Improve Publishing Settings Display for Collection Settings
2024-01-16T18:33:53Z
Stacy Lathrop
Improve Publishing Settings Display for Collection Settings
cc @ErinS
## Context
Users don't clearly understand what the Publishing Settings do for Collection Settings and the relations between them. We think this can be improved by some minor display changes.
For example of context in UI, cl...
cc @ErinS
## Context
Users don't clearly understand what the Publishing Settings do for Collection Settings and the relations between them. We think this can be improved by some minor display changes.
For example of context in UI, click on Settings here:
https://ncbi.cloud68.co/organizations/dbdf7c10-9f78-44dd-bef2-31c85cf9b8e0/collectionmanager/302a5d8d-b4bb-4c3f-9a05-63d9e7db49c2/
## Design Proposal
![image](/uploads/1508467554dbae3b921a00298657ca49/image.png)
Not a priority for migration or deployment.
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/861
Relabel the "Books and Collections" and "Users" tabs to help orient whether y...
2024-01-16T18:19:04Z
Erin Schmieder
Relabel the "Books and Collections" and "Users" tabs to help orient whether you're looking at all BCMS or specific org
[Template for request for comments (RFC) on feature proposals]
# RFC: Feature proposal: [Title]
## Context
Because the design of different dashboards (i.e. overall BCMS dashboard ) across the BCMS are so similar, it help to provide mo...
[Template for request for comments (RFC) on feature proposals]
# RFC: Feature proposal: [Title]
## Context
Because the design of different dashboards (i.e. overall BCMS dashboard ) across the BCMS are so similar, it help to provide more customized labels between the two to help users orient where they are. For instance, there is a "Users" tab in both, but it lists a different set of users.
## Proposal
1) Relabel the "Books and Collections" and "Users" tabs in the BCMS dashboard as "All Books and Collections" and "All BCMS Users"
2) For the "Books and Collections" and "Users" tabs tab in the dashboards for individual organization, institute dynamic labels with the format:
"[Org abbreviation] Books and Collections".
"[Org abbreviation] Users".
This would dynamically populate the tab with the abbreviation that was provided by the organization, and the system would need to reformat the abbreviation from lower case to upper case.
Some examples:
AHRQ Books and Collections | AHRQ Users
WHO Books and Collections | WHO Users
## Design
See attached
![Tab_relabeling_example](/uploads/042ea0047f9ded696314e1d9af01660d/Tab_relabeling_example.jpg)
## Implementation (if applicable)
See proposal above
## Alternative approaches (if applicable)
If the dynamic labeling is difficult or not possible, we could relabel the organization's tabs as:
This Org's Books and Collections | This Org's Users![Tab_relabeling_example]
## Open issues (if applicable)
[Links to and a discussion of related issues, if applicable.]
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/852
Some settings are showing in the New Collection UI that should not be there
2024-01-16T18:33:50Z
Erin Schmieder
Some settings are showing in the New Collection UI that should not be there
[Provide a general summary of the issue in the title above]
## Expected behaviour
According to the spreadsheet, the following settings should not be present in the New Collection UI:
Publishing Settings: Open Access Status
Publishing S...
[Provide a general summary of the issue in the title above]
## Expected behaviour
According to the spreadsheet, the following settings should not be present in the New Collection UI:
Publishing Settings: Open Access Status
Publishing Settings: UKPMC
Landing Page Links: Publisher URL
Landing Page Links: Citation self-URL
## Current behaviour
I am seeing these settings in Collection Settings UI when I log in as a system admin
## Steps to reproduce
1.Lon into the BCMS as a System Admin
2.Click on the "New Collection" button
3.Go to the second page of the new collection setup process
4.I am seeing these settings on the second page
## Environment
Microsoft Edge, PC
## Possible solution
If spreadsheet is correct, don't show these settings
## Priority
1. Resolving this bug is required for migration N
2. This can be prioritised after migration (Not sure)
@lathrops1
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/802
Remove incoming packages from FTP after successful ingest to BCMS
2024-01-16T18:33:50Z
Martin Latterner
Remove incoming packages from FTP after successful ingest to BCMS
We would like you to remove incoming FTP packages after successful ingest to BCMS.
This impacts "conversion", i.e. packages in:
```
/convert/xml/word/out/
/convert/xml/book/out/
/convert/xml/chapter/out/
```
And it impacts "FTP submiss...
We would like you to remove incoming FTP packages after successful ingest to BCMS.
This impacts "conversion", i.e. packages in:
```
/convert/xml/word/out/
/convert/xml/book/out/
/convert/xml/chapter/out/
```
And it impacts "FTP submissions", i.e.
```
/submit/*/
```
These are packages called out as `package` in the `submit_apex_package_receipt` and `submit_package_receipt` Kafka notifications.
It's important to remove the packages at the very last step, after successful ingest.
Rationale: The FTP site is not intended to be permanent storage: we will run out of space if we let too much pile up.
We also discussed cleaning the FTP NCBI-side, but decided that removal immediately following successful load to BCMS is the best option.
cc @Kireev
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/791
Published status / link improvements
2024-01-16T18:33:48Z
Stacy Lathrop
Published status / link improvements
## Context
For BCMS Phase 1, it is was agreed to implement minimal support for published status. However, there are some areas that are unclear for a user that should be improved post-deployment, namely about which URL is being viewed i...
## Context
For BCMS Phase 1, it is was agreed to implement minimal support for published status. However, there are some areas that are unclear for a user that should be improved post-deployment, namely about which URL is being viewed in the BCMS and the status of chapter-processed book domains.
## Proposal
Post-deployment, the following would be implemented:
- Status of chapter-processed book domains
- Clear details and tab names for Preview (QA) vs Published (live) URLs provided in BCMS
- Possibly domain settings for `live_in_pmc` and `journal_qa_status`
## Design
@DioneMentis - please provide the wireframe you shared during a review
## Implementation (if applicable)
N/A
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/788
TOC Placement Issues Resulting in Innacurate TOCs
2024-01-16T18:23:01Z
Stacy Lathrop
TOC Placement Issues Resulting in Innacurate TOCs
## USER STORY
Sometimes the system does not know exactly where to place a chapter component in the book manager page. Coko without NCBI review tried to address this with a "TOC?" icon that is not fully understood by users. The user is a...
## USER STORY
Sometimes the system does not know exactly where to place a chapter component in the book manager page. Coko without NCBI review tried to address this with a "TOC?" icon that is not fully understood by users. The user is also not forced to address this icon notification before a TOC is built and automatically published that has resulted during testing in inaccurate TOCs being built.
## PROPOSED SOLUTIONS
- [ ] Require ALL chapter-processed books to have an Admin / Editor required to approve chapter components before they are published
- [ ] Rename icon to a "Cannot Place in TOC" red query, and provide a tool tip saying "The BCMS does not know where to place this in the table of contents. Please address in your source Word file or manually drag the component to where it belongs."
- [ ] The "Cannot Place in TOC" query is communicated in an email notification to users.
- [ ] User is forced to click and resolve any "Cannot Place in TOC" red warning if / once they have resolved it via a manual action.
- [ ] No TOC.XML will be written and published if there are any "Cannot Place in TOC" queries.
## RELATED DOCUMENTATION
From issue #24
Manual grouping / sorting rules:
* [ ] IF manual sorting order is selected by the user, user can drag their chapter exactly where they want it in the body of the TOC
**- \[ \] IF more than one front matter component, the BCMS places the component at the top of the Front unit and provides a notification (on the display page and by email?) that it is unable to place the document per supported automatic rules AND will not code that entry in any TOC.XML until that notification is addressed by the user**
**- \[ \] IF more than one back matter component, the BCMS places the component at the top of the Back unit and provides a notification (on the display page and by email?) that it is unable to place the document per supported automatic rules AND will not code that entry in any TOC.XML until that notification is addressed by the user**
**- \[ \] IF support for parts is selected by the user AND the user adds parts, the BCMS places the component at the top of the Body unit and provides a notification (on the display page and by email?) that it is unable to place the document per supported automatic rules AND will not code that entry in any TOC.XML until that notification is addressed by the user**\*\*
* [ ] IF support for parts is selected, user can place their component in the part they created and wishes that component to belong, and then that component will be autosorted withing the part it was added by any selected auto-sorting rules or manually sorted within that part if a manual order is selected
* [ ] IF support for parts is selected by the user, user can still have a component in the body that does not belong to any part
**- \[ \] Users must resolve any notifications that the system does not know how to place a componet (even if it is ticking an "I accept where it is placement) before a TOC.XML is sent for publication** **- OR SIMPLIFICATION PHASE 1, ALL CHAPTER-PROCESSED BOOKS REQUIRE PREVIEW APPROVAL OF ALL CHAPTER COMPONENTS AND A SINGLE TOC.XML APPROVAL ACKNOWLEDGEMENT)**
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/784
Add a Cancel button to the first New Book settings screen
2024-01-16T18:33:48Z
Erin Schmieder
Add a Cancel button to the first New Book settings screen
[Template for request for comments (RFC) on feature proposals]
# RFC: Feature proposal: [Title]
## Context
I suggest adding a Cancel button on the first screen when a user is creating a new book (on the same level as the Next button.)...
[Template for request for comments (RFC) on feature proposals]
# RFC: Feature proposal: [Title]
## Context
I suggest adding a Cancel button on the first screen when a user is creating a new book (on the same level as the Next button.) Once you're on this screen, there is no built-in way to back out. Users can currently use the back button, but it feels like a work around, and like you're unsure whether using the back button is actually cancelling the new book you started to create. This feels doubly true if you start to create a new book on the first screen, hit Next, get the pop-up asking if you're sure, and you press Cancel and are brought back to the first screen with no way to cancel out of the whole thing.
Not at all a priority since the back button does exist, but I think it would come in handy especially because you might get a decent amount of new users after launch clicking on the "New Book" button out of curiosity, and then having no clear way to cancel out of it.
## Proposal
Add a Cancel button to the bottom of the first settings screen after a user presses the "New Book" button.
Cancel button would wipe out anything they had put in the form on settings form in the first New Book screen and bring them back to teh previous screen.
## Design
![image](/uploads/0279191d4419ff8224378f5434328385/image.png)
## Implementation (if applicable)
[A description of the steps to implement the feature.]
## Alternative approaches (if applicable)
Users can currently access the same behavior by using the browser's back button, this would just be a slightly better user flow
## Open issues (if applicable)
[Links to and a discussion of related issues, if applicable.]
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/756
Sorting labels are not always lowest to highest so need to address for all wo...
2024-01-16T18:33:53Z
Stacy Lathrop
Sorting labels are not always lowest to highest so need to address for all workflows
## Expected behaviour
Users should be able to sort by label in the way that makese sense to them for their content
## Current behaviour
Chapter labels work properly 1-#
Issue labels do not work as #-1 per current rules
## Steps to ...
## Expected behaviour
Users should be able to sort by label in the way that makese sense to them for their content
## Current behaviour
Chapter labels work properly 1-#
Issue labels do not work as #-1 per current rules
## Steps to reproduce
See: https://ncbi.cloud68.co/organizations/9f638bd9-4226-4d99-a9fb-579dba128443/bookmanager/0980f579-6bf7-440d-a354-07db04a1cd81/
Can't generate TOC preview yet
1. Note order is lowest to higest
2. Compare issues for XML and PDF books with labels are highest to lowest:
https://www.ncbi.nlm.nih.gov/books/NBK378971/
## Environment
[Provide browser name and version and if you're working from a PC or Mac]
## Possible solution
We allow user to set what order (highest-lowest, lowest-highest) as part of setting, or we turn off this setting for non Word books.
## Priority
Y - because it can potentially cause content errors
https://gitlab.coko.foundation/ncbi/ncbi/-/issues/755
Unable to search by chapter BCMSID
2024-01-16T18:23:03Z
Stacy Lathrop
Unable to search by chapter BCMSID
## Expected behaviour
Users should be able to retrieve any component by a search by any BCMSID
## Current behaviour
Unable to retrieve a chapter component by BCMSID when testing PDF workflow where we submit chapters to taggers
## St...
## Expected behaviour
Users should be able to retrieve any component by a search by any BCMSID
## Current behaviour
Unable to retrieve a chapter component by BCMSID when testing PDF workflow where we submit chapters to taggers
## Steps to reproduce
See: https://ncbi.cloud68.co/organizations/4dd138c1-1baa-437b-8a0e-d25b91319687/bookmanager/821733d2-6057-425e-bc8f-955457f6c36c/59f88edc-5f7c-4aa8-b39b-6258570f3608
1. See chapter BCMSID is bcms763
2. Try to search by that bcmsid
3. See you get no results
## Priority
Y - because my understanding is this is the bcmsid being communicated to users for all notifications, so they need to be able to search by it to get to it, unless there is a clear link in email notifications