ncbi issueshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues2022-06-16T21:43:06Zhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/918Update error message when user role is added twice2022-06-16T21:43:06ZSidorela UkuUpdate error message when user role is added twiceSteps to see the error:
* Go to users tab on an organization page
* Add role Editor or Org Admin to a user if there is no user with that role
* Select the user from the checkbox and try to add the same role again from bulk actions
* It w...Steps to see the error:
* Go to users tab on an organization page
* Add role Editor or Org Admin to a user if there is no user with that role
* Select the user from the checkbox and try to add the same role again from bulk actions
* It will show the error as below:
![image](/uploads/e0caa34d1e3e4a54c3cae1791c665613/image.png)
##### Possible solutions
Change this error message to something more descriptive, for example `$username already has the role assigned`.
##### QA Steps:
* Go to users tab on an organization page
* Add role Editor or Org Admin to a user if there is no user with that role
* Select the user from the checkbox and try to add the same role again from bulk actions
* It will show the updated error '[Username] already has the role assigned.'2022-Apr-AChristinaTrompChristinaTromphttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/917Error trying to manually submit wholebook XML that belongs to a collection2022-01-05T21:11:49ZStacy LathropError trying to manually submit wholebook XML that belongs to a collection
## Expected behaviour
Should be able to submit a wholebook XML whether it belongs to a collection or not.
## Current behaviour
Getting this error when try to submit a wholebook XML book that belongs to a colletion.
![image](/uploads...
## Expected behaviour
Should be able to submit a wholebook XML whether it belongs to a collection or not.
## Current behaviour
Getting this error when try to submit a wholebook XML book that belongs to a colletion.
![image](/uploads/9417ccdaa103600aa9f612e1ae5f3970/image.png)
## Steps to reproduce
See: https://ncbi.cloud68.co/organizations/6804540d-8ecd-419a-a34d-6513718abf76/bookmanager/44bc4e60-3f0c-466d-83d8-617f32bc0900/3d57b8c9-4168-4b05-ba69-167e3ec909eb
1. Create Collection like: https://ncbi.cloud68.co/organizations/6804540d-8ecd-419a-a34d-6513718abf76/collectionmanager/bb423e8c-9fc0-4e8b-b8dd-46d24fba8a95/
2. Create Book with same settings as: https://ncbi.cloud68.co/organizations/6804540d-8ecd-419a-a34d-6513718abf76/bookmanager/44bc4e60-3f0c-466d-83d8-617f32bc0900/3d57b8c9-4168-4b05-ba69-167e3ec909eb
3. Upload files and press Submit - get error preventing you from doing so
## Priority
Y, blocks full testing of latest metadata buildGiannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/916NCBI testing release: 22 Dec2022-01-28T17:01:29ZDione Mentisdione@coko.foundationNCBI testing release: 22 Dec@lathrops1
## Features
This release is focused on the Metadata Epic (ncbi&9)
* All acceptance criteria are up to date at the epic, and I have made a note "not included in 22 Dec release" for any that do not apply.
* I have labelled a...@lathrops1
## Features
This release is focused on the Metadata Epic (ncbi&9)
* All acceptance criteria are up to date at the epic, and I have made a note "not included in 22 Dec release" for any that do not apply.
* I have labelled all feature issues with [test-20211222-metadata](https://gitlab.coko.foundation/ncbi/ncbi/-/issues?scope=all&state=closed&label_name[]=test-20211222-metadata)
* The relevant documentation is in #678
### Metadata
1. #355: Collection metadata UI and backend
2. #815: Write collection xml file for package to send to load to PMC -- please see instructions there for downloading this file
3. #813: Copy and save collection meta values to book meta (for collection members)
4. #814: Write collection meta node to include in converted chapter.xml files
5. #819: Wholebook metadata UI and backend
6. #423: Chapter-processed book metadata UI and backend
7. #424: Book component metadata UI
8. #737: How styled metadata in the UI translates to xml
### Excluded metadata features
This release does not include:
1. Granthub funding -- #433
2. Support for new covers workflow in #751 -- these means that you should not test uploading of covers at all
3. write abstract graphic into book-meta (WORD WF) -- #914
4. A minor UI fix in #911
## Bugs: metadata
We have resolved a number of bugs that we have found while testing metadata specifically. These don't necessarily need to be tested by your team since they have not been in a ncbi testing build, but it useful to know what has been dealt with already:
* #886
* #908
* #909
* #910
* #912
* #913
## Additional bugs resolved:
* #895: NCBIDEV and NCBI sites lose connection
* #851: Chapter components stuck in "New Upload" status
* #848: main_xml not specified in packages sent to ncbi for conversion
* #864: User able to hit some "sweet spot" to upload files when upload button is greyed out
* #795: Reworked PDF2 XML tagged packages posted to FTP not ingested into BCMS
* #558: Book title duplicated and beyond title area
## Support for downtime
If the testing site goes down while we are away, please send an email to support@cloud68.co (cc me) with the subject NCBI site down -- restart needed. This support is available Monday to Friday 9.00 - 17.00 CET/CEST timezone.Stacy LathropStacy Lathrophttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/915Upgrade to nodejs 16.13.1 LTS version to address security vulnerabilities2022-02-18T05:21:46ZEvgenyUpgrade to nodejs 16.13.1 LTS version to address security vulnerabilitiesNCBI GitLab runs security scans of the bcms Docker image on every build in 'develop' branch. It currently reports 176 Critical and 1243 High vulnerabilities, mostly because of the old not supported versions of various Linux system librar...NCBI GitLab runs security scans of the bcms Docker image on every build in 'develop' branch. It currently reports 176 Critical and 1243 High vulnerabilities, mostly because of the old not supported versions of various Linux system libraries, Python and nodejs packages. NCBI DevOps / Systems are asking us to address these security issues before production deployment.
![gitlab_vulnerability_report](/uploads/3357a538a793f11df8c498bfe46e69df/gitlab_vulnerability_report.JPG)
I've tried using `16.13.1-buster-slim` as a base image. Here are the changes in Dockerfile I made, seems the image has been built successfully but the resulting container fails to run. Please correct / update as needed. Once a new container builds and runs successfully in 'develop' branch, we will review the vulnerability report again.
```docker
# IMAGE FOR BUILDING
FROM node:16.13.1-buster-slim
RUN apt-get update && apt-get install -y git python3 make g++
```
```
# IMAGE FOR RUNNING
FROM node:16.13.1-buster-slim as server
```2022-Jan-Ahttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/914write abstract graphic into book-meta (WORD WF) and send to Load to PMC2022-03-27T23:33:00ZDione Mentisdione@coko.foundationwrite abstract graphic into book-meta (WORD WF) and send to Load to PMCThis is the last item to do from #423
1. [x] Write abstract graphic into book meta, for example:
```xml
<abstract>
<title>BOOK LEVEL ABSTRACT</title>
<graphic xlink:href="JohnHopfield_0.jpg"/>
<p>
Its very
<italic> abstract!</italic>...This is the last item to do from #423
1. [x] Write abstract graphic into book meta, for example:
```xml
<abstract>
<title>BOOK LEVEL ABSTRACT</title>
<graphic xlink:href="JohnHopfield_0.jpg"/>
<p>
Its very
<italic> abstract!</italic>
</p>
</abstract>
```
2. [x] include the image in the TOC package that is sent load to PMC step
## QA steps
1. upload an image to "Abstract graphic" in the metadata UI for a chapter processed book (and complete required fields)
2. Publish the Book TOC (there must be at least one chapter published first)
3. When TOC is published, see the "Abstract graphic" displayed on the "Live" tab (note it may take up to 10 mins for the for the image to display)2022-Feb-Bhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/913chapter-processed book meta fields missing from written XML2022-01-05T11:21:35ZDione Mentisdione@coko.foundationchapter-processed book meta fields missing from written XML## Expected behaviour
The BCMS should write all chapter-processed book meta as described in #423
## Current behaviour
These fields are missing for the xml:
- [x] Edition
- [x] Volume / Issue number in series
- [x] DOI
- [x] ISBN
- [ ...## Expected behaviour
The BCMS should write all chapter-processed book meta as described in #423
## Current behaviour
These fields are missing for the xml:
- [x] Edition
- [x] Volume / Issue number in series
- [x] DOI
- [x] ISBN
- [ ] Abstract graphic (in Word books)
- [x] Collaborative author
- [x] Suffix and Role in "author" and "editor" type contributors
- [x] Date created and Date updated in Publication History
- [x] Book source type
- [x] All notes
## Steps to reproduce
1. Create a chapter processed book and fill in all metadata fields, save
2. Upload a chapter and wait for a successful preview
3. Download the converted xml -- this should have the `<book-meta>` node with all fields complete in the UI
Alternatively reload preview or publish an existing chapter, then download the converted xml
(The same can be done by publishing a TOC.xml)
I did this in [this book](https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/bookmanager/709b89aa-5fa3-4736-be37-436f0cfb1d01/) on:
1. [Dedication](https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/bookmanager/709b89aa-5fa3-4736-be37-436f0cfb1d01/7ddd23a0-1528-481d-8fd1-559899d989ab) -- xml: [dedication.xml](/uploads/97c7fc050490c6c46c6223ce24d86c42/dedication.xml)
2. [Introduction](https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/bookmanager/709b89aa-5fa3-4736-be37-436f0cfb1d01/4b5f8ddd-005d-4b89-a12d-395585d2fe31) -- xml: [introduction__2_.xml](/uploads/dd4fce72cd51b5b8cf5cedc50a9c15af/introduction__2_.xml)
3. TOC -- xml: [TOC__25_.xml](/uploads/8ccc1842805f24f5fcead62b8bfc7d0d/TOC__25_.xml)
Note: this was at around 20:20 Athens time -- *after* [MR702](https://gitlab.coko.foundation/ncbi/ncbi/-/merge_requests/702) but prior to experiencing the bug in #910
## Priority
Y, for migrationDec.02Andy NicholsonAndy Nicholsonhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/912UI: subtitle and alternative title in chapter-processed book meta should be e...2021-12-23T00:03:39ZDione Mentisdione@coko.foundationUI: subtitle and alternative title in chapter-processed book meta should be editors## Expected behaviour
As in the spec in #423 and #737 -- these fields should have Wax editor with: bold, italic, superscript, subscript:
- subtitle
- alternative title
## Current behaviour
Plain text fields are shown
## Steps to r...## Expected behaviour
As in the spec in #423 and #737 -- these fields should have Wax editor with: bold, italic, superscript, subscript:
- subtitle
- alternative title
## Current behaviour
Plain text fields are shown
## Steps to reproduce
Go to any chapter processed book, for example: https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/bookmanager/5ad24fd0-76b9-49b1-9523-2ea0a0ed6d34/
## Priority
Assume Yes, for migration -- @lathrops1 to confrimDec.02Danjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/911Collab author text field and label do not match in book and collection meta2022-01-07T10:22:00ZDione Mentisdione@coko.foundationCollab author text field and label do not match in book and collection meta@danjela A minor fix:
`Given name` in the text field should be `Author name` as in the Label
![Screenshot_2021-12-21_at_19.20.28](/uploads/e923e88923d24f9ad76aca3bf80b1689/Screenshot_2021-12-21_at_19.20.28.png)@danjela A minor fix:
`Given name` in the text field should be `Author name` as in the Label
![Screenshot_2021-12-21_at_19.20.28](/uploads/e923e88923d24f9ad76aca3bf80b1689/Screenshot_2021-12-21_at_19.20.28.png)Danjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/910Error: Metadata cannot be updated2021-12-23T00:03:39ZDione Mentisdione@coko.foundationError: Metadata cannot be updated## Steps to reproduce
Metadata cannot be updated in [this chapter-processed book](https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/bookmanager/262e5d7e-06af-46da-aa7d-95b56856de0d/)
1. Create book -- and ad...## Steps to reproduce
Metadata cannot be updated in [this chapter-processed book](https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/bookmanager/262e5d7e-06af-46da-aa7d-95b56856de0d/)
1. Create book -- and add to a collection at this point.
2. Open book meta to see if "book source type" value has been applied (it's not, so I must complete required fields to save meta from)
3. Update title and save meta from
4. Try to update title again and get error
### Update:
Another example [here](https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/bookmanager/709b89aa-5fa3-4736-be37-436f0cfb1d01/) -- this was working at about 20:20 Athens time
## Possible solution
From Andy:
>There seems to be errors saving Metadata for Books via the UI -- something to do with the Publication date, if you change from a date to a date range -- Funder courtesy notes gives a error in the backend, you can't save via UI
## Priority
Workaround for testing:
>I re-entered the pubDate per Dione's example and it started working.. (editing the publication year gets around the bug)
This is a priority for deploymentDec.02Danjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/909"Book source type" not applied to collection members2021-12-23T00:03:39ZDione Mentisdione@coko.foundation"Book source type" not applied to collection members## Expected behaviour
In spec in #355 -- when a collection is step up, the user specifies the "Book source type" for all wholebook and chapter-processed books. Once this is set, users should not be able to change it at the book level, u...## Expected behaviour
In spec in #355 -- when a collection is step up, the user specifies the "Book source type" for all wholebook and chapter-processed books. Once this is set, users should not be able to change it at the book level, unless the book is removed from the collection.
## Current behaviour
1. When I add a book to a collection, it does not always inherit the "Book source type"
2. I can edit "Book source type" when the book belongs to a collection.
## Steps to reproduce
See example books in [this collection](https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/collectionmanager/4735319a-c2fc-4be5-b45f-c5a42c4bd853/)
1. Create collection and set "Book source type" for the members
2. Create book and add to the collection at creation
3. Open book meta form and see "Book source type" is blank
(same behaviour for wholebooks and chapter-processed books)
![Screenshot_2021-12-21_at_23.14.58](/uploads/edf76580038d9032dafd1ec4eca061c4/Screenshot_2021-12-21_at_23.14.58.png)
## Priority
I assume this must be prioritised before migration -- @lathrops1 to confirmDec.02Sidorela UkuDione Mentisdione@coko.foundationSidorela Ukuhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/908"Publisher book series title" is shown in "funder" collection instead of "boo...2021-12-23T00:03:39ZDione Mentisdione@coko.foundation"Publisher book series title" is shown in "funder" collection instead of "book series" collection## Expected behaviour
In the spec in #355 -- "Publisher book series title" should display in "Book series" collection only
## Current behaviour
* "Publisher book series title" is missing from "Book series" collection
* "Publisher bo...## Expected behaviour
In the spec in #355 -- "Publisher book series title" should display in "Book series" collection only
## Current behaviour
* "Publisher book series title" is missing from "Book series" collection
* "Publisher book series title" is added to "Funder" collection
## Steps to reproduce
1. See "Book series" collection: https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/collectionmanager/4735319a-c2fc-4be5-b45f-c5a42c4bd853
2. See "Funder" collection : https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033/collectionmanager/804d3bf5-5b76-489d-a4e7-88fb826a387c/
## Priority
I assume YES for migration, but @lathrops1 and @deniskar should confirmDec.02Sidorela UkuDione Mentisdione@coko.foundationSidorela Ukuhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/907pasting in search bar creates blank screen2022-05-11T16:48:54ZDione Mentisdione@coko.foundationpasting in search bar creates blank screen## Steps to reproduce
1. go to user tab
2. paste name of user to search for
3. screen goes blank
happened at ncbi site: https://ncbi.cloud68.co/organizations/32d78686-4b9a-46af-b52a-f5d0c4052177
and replicated at ncbidev: https://ncb...## Steps to reproduce
1. go to user tab
2. paste name of user to search for
3. screen goes blank
happened at ncbi site: https://ncbi.cloud68.co/organizations/32d78686-4b9a-46af-b52a-f5d0c4052177
and replicated at ncbidev: https://ncbidev.cloud68.co/organizations/a2c1e381-f348-41a9-9d76-e4f11f761033
4. refreshing screen resolves error
If you can't replicate it, paste the username twice in the search bar with a separating space, for example 'dianagmail dianagmail'
## Environment
Mac, Chrome Version 96.0.4664.93
## Priority
N
## QA Steps
1. Go to an organization page
2. Go to the users tab of this organization
3. write something like username and add a space after it or paste 'test username' on search box
4. Screen should not go blank after it.
5. Try this also on all users tab in main dashboard.2022-Apr-AChristinaTrompChristinaTromphttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/906Adding style to collection title causes errors in toc.xml2021-12-21T15:07:20ZDione Mentisdione@coko.foundationAdding style to collection title causes errors in toc.xml@lathrops1
We have in the spec that the Collection title can be styled with: bold, italics, superscript and subscript (#737) but this results in errors when the collection title is inserted into toc files. See attached toc which gets t...@lathrops1
We have in the spec that the Collection title can be styled with: bold, italics, superscript and subscript (#737) but this results in errors when the collection title is inserted into toc files. See attached toc which gets this error:
```
> No declaration for element em
> ^
> Element em is not declared in title list of possible children
> ^
> No declaration for element em
> ^
> Element em is not declared in title list of possible children
```
How should this be resolved?
[TOC__24_.xml](/uploads/9d5b51387e1d32c7fdd7c43af5cb632b/TOC__24_.xml)Stacy LathropStacy Lathrophttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/905Progress review agenda 21 Dec 212022-01-17T11:13:50ZDione Mentisdione@coko.foundationProgress review agenda 21 Dec 21@lathrops1 For our update call today
## Agenda
1. NCBI testing release will be postponed to tomorrow (22 Dec)
* Our team is still busy testing some features related to metadata
* We have one priority bug that requires investigat...@lathrops1 For our update call today
## Agenda
1. NCBI testing release will be postponed to tomorrow (22 Dec)
* Our team is still busy testing some features related to metadata
* We have one priority bug that requires investigation today (#895)
* I've grouped all issues for the release by label [release-20211222](https://gitlab.coko.foundation/ncbi/ncbi/-/issues?label_name%5B%5D=release-20211222)
2. Priority feedback on 23 Dec: our team will be available in case there any issues that block your testing
3. Coko team leave: 24 Dec -- 4 Jan
4. New contract schedule
* I am working on milestone for the new contact
* before we leave I'd like to confirm development issues for January, especially by priority of pre vs post deploymenthttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/904Session links don't display in errors report2022-10-09T12:49:23ZDione Mentisdione@coko.foundationSession links don't display in errors report## Expected behaviour
Error reports from NCBI conversion and Load to PMC contain session links (e.g. xx). These should display above the relevant table of errors.
## Current behaviour
The session links do not dislay
## Steps to rep...## Expected behaviour
Error reports from NCBI conversion and Load to PMC contain session links (e.g. xx). These should display above the relevant table of errors.
## Current behaviour
The session links do not dislay
## Steps to reproduce
Example book: https://ncbi.cloud68.co/organizations/099273a1-565e-4085-b0d6-55b5a0392e3f/bookmanager/c4398939-5de2-4da4-9e22-5912fa645a0d/043df27a-fbfe-49e8-8ffa-fa57ab191bf9
1. Go to errors tab, see there are three reports: one Conversion and two for Loading to PMC
2. From the TM emails you can see the session links that should have been included
### Task manager email
wholebook loaded (bcms2364)
Book : bcms2364.af02cd
Target : PMCA3
Started at : 2021-12-19 11:50:48
Completed at : 2021-12-19 12:04:45
https://preview.ncbi.nlm.nih.gov/bookshelf/coko/br.fcgi?accid=NBK126753.1
http://ipmc-prod.be-md.ncbi.nlm.nih.gov:5701/internal/utils/tm/index.fcgi?s=monitor&sel=1&sessid=11554835
---
wholebook loaded (bcms2364)
Book : bcms2364.bd850d
Target : PMCA3
Started at : 2021-12-17 19:07:49
Completed at : 2021-12-17 19:17:04
https://preview.ncbi.nlm.nih.gov/bookshelf/coko/br.fcgi?accid=NBK126753.1
http://ipmc-prod.be-md.ncbi.nlm.nih.gov:5701/internal/utils/tm/index.fcgi?s=monitor&sel=1&sessid=11551271
---
Package : bcms2364.e1f5d0.2021_12_17-11_59_31.zip
BCMS jobid : e1f5d0
Started at : 2021-12-17 19:00:48
Completed at : 2021-12-17 19:06:35
http://ipmc-prod.be-md.ncbi.nlm.nih.gov:5701/internal/utils/tm/index.fcgi?s=monitor&sel=1&sessid=11551240
## Priority
2. This can be prioritised after migration (Y/N)https://gitlab.coko.foundation/ncbi/ncbi/-/issues/903FTP submission with collection-submit-id not added to collection2021-12-22T00:39:41ZStacy LathropFTP submission with collection-submit-id not added to collection
## Expected behaviour
If an FTP submission has a `collection-submit-id` with a valid id, then the submission should be added to the collection.
## Current behaviour
A book submission posted to FTP with a valid `collection-submit-id` ...
## Expected behaviour
If an FTP submission has a `collection-submit-id` with a valid id, then the submission should be added to the collection.
## Current behaviour
A book submission posted to FTP with a valid `collection-submit-id` was not added to the collection with that id.
## Steps to reproduce
Package - [ntptoxdemo.zip](/uploads/47e714710e93ce77cda4df6d5f8921ce/ntptoxdemo.zip)
See in BCMS: https://ncbi.cloud68.co/organizations/099273a1-565e-4085-b0d6-55b5a0392e3f/bookmanager/c4398939-5de2-4da4-9e22-5912fa645a0d/043df27a-fbfe-49e8-8ffa-fa57ab191bf9
See it is was not added to its Collection: https://ncbi.cloud68.co/organizations/881d4db3-dfd5-44ff-a8b2-d4c5872e2bb5/collectionmanager/729a12bb-0829-4291-9f43-296498043177/
Note, this was also had multiple Task Manager sessions - and there is no TM link from the Errors page for the book.
[dts_custom_summary_bookshelf_20211221.xlsx](/uploads/3f3e30d0bddb2ac6e6931e8f6323cc83/dts_custom_summary_bookshelf_20211221.xlsx)
## Priority
Not for migration, yes for deploymentDione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/902Nested parts are not nested in TOC preview / xml2022-01-13T02:39:43ZStacy LathropNested parts are not nested in TOC preview / xml
## Expected behaviour
If parts are nested by user in TOC manager, they should be nested in TOC XML and preview.
## Current behaviour
Parts nested in TOC manager are flat in TOC XML and preview.
## Steps to reproduce
See: https://nc...
## Expected behaviour
If parts are nested by user in TOC manager, they should be nested in TOC XML and preview.
## Current behaviour
Parts nested in TOC manager are flat in TOC XML and preview.
## Steps to reproduce
See: https://ncbi.cloud68.co/organizations/9f638bd9-4226-4d99-a9fb-579dba128443/bookmanager/cff93765-f1b1-43c8-a1c9-22f5f6397eb2/
Transcription and Resistance is nested inside Transcription
![image](/uploads/d0dacbf4b8f91c84de926a22cbf449b8/image.png)
In TOC preview they are all flat:
https://ncbi.cloud68.co/organizations/9f638bd9-4226-4d99-a9fb-579dba128443/bookmanager/cff93765-f1b1-43c8-a1c9-22f5f6397eb2/toc/2bb7b39a-18a3-4377-81d4-e9b175dec4e5
![image](/uploads/148966ccebc931a2eac74e6853f7e01d/image.png)
## Priority
Not for migration - low priority for deployment (research to determine number use cases)2022-Jan-ASidorela UkuSidorela Ukuhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/901Unable to reload all components with loading errors2022-01-13T01:00:03ZStacy LathropUnable to reload all components with loading errors
## Expected behaviour
Any component in status of "loading errors" should be able to be retriggered by user via "Reload preview"
## Current behaviour
In some cases where a converted file was loaded to preview and failed you cannot ret...
## Expected behaviour
Any component in status of "loading errors" should be able to be retriggered by user via "Reload preview"
## Current behaviour
In some cases where a converted file was loaded to preview and failed you cannot retrigger a "Reload Preview"
## Steps to reproduce
See: https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/075fd597-3d31-4d3f-9177-73946ad03bd4
- Try to select all and trigger reload preview - you are unable:
![image](/uploads/901a48d84169d2e91aaeb092b56cdc07/image.png)
See: https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/075fd597-3d31-4d3f-9177-73946ad03bd4/62b38a98-54f3-4f1f-ac2f-bb367e2749f8
- Try to select file with Loading failed and Reload Preview - you are unable:
![image](/uploads/2bdef14632bc4c53539ad67619612186/image.png)
## Priority
No for migration, yes for onboarding external users2022-Feb-ADanjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/900Filters don't "stick"2024-01-16T18:23:00ZStacy LathropFilters don't "stick"<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
cc @douglassue @ErinS
## Context
On Dashboards, users are using filters a lot, particularly as the list of contents grows. Users express *a lot" of frustration that once they filter content and click on a book and go back to the dashboard their filtered contents are lost and they have to redo the filtering. We should consider improvements for how to "save" filters or have them "stick" if the user uses a browser back button.
When admin features are scoped and developed to onboard publishers (orgs) and their users, consider how to make the filters more usable along with a search function, that would also include the ability to pull reports.
## Proposal
<!-- A precise statement of the proposed feature. -->
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
<!-- Delete the irrelevant options -->
Schedule this feature to be scoped and designed for Epic:
- [4.0 Priority: Onboard remaining XML and PDF users and advanced admin features](https://gitlab.coko.foundation/groups/ncbi/-/epics/59)
<!-- Assignee and labels are added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->https://gitlab.coko.foundation/ncbi/ncbi/-/issues/899Adding new upload file version moves component out of part it had belonged2022-02-01T23:46:36ZStacy LathropAdding new upload file version moves component out of part it had belongedcc @douglassue
## Expected behaviour
Once a user moves a chapter component to a part, it should stay in that part where it was moved until the user herself moves it.
## Current behaviour
When the user uploaded a new converted file v...cc @douglassue
## Expected behaviour
Once a user moves a chapter component to a part, it should stay in that part where it was moved until the user herself moves it.
## Current behaviour
When the user uploaded a new converted file version the component move out of the part to the top of the TOC manager.
## Steps to reproduce
See: https://ncbi.cloud68.co/organizations/effa49bf-5391-4583-ba39-228af77ec3a2/bookmanager/2b36ae8c-a9ba-4601-91ac-393112bf31e8
1. Create book with same settings and parts, etc
2. Upload files for both components - only send converted files to preview
3. Move both components to the part
4. For one component, upload a new converted file version
## Priority
Not for migration, but yes for onboarding new users2022-Jan-ADione Mentisdione@coko.foundationDione Mentisdione@coko.foundation