ncbi issueshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues2024-01-16T07:47:29Zhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1635Document and Implement Stress Testing into Coko QA2024-01-16T07:47:29ZStacy LathropDocument and Implement Stress Testing into Coko QA<!-- Required. Provide a general summary of the issue in the title above -->
## Context
Once #1456 is implemented, regular stress testing should be conducted as part of Coko QA to ensure performance, data model, XML writing, files mana...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
Once #1456 is implemented, regular stress testing should be conducted as part of Coko QA to ensure performance, data model, XML writing, files management, processing high level acceptance criteria are continually met against real NCBI load and content types as development is ongoing.
## Proposal
Coko will document and implement a stress testing QA process acceptable to NCBI to ensure performance, data model, XML writing, fles management, and processing high level user stories are continuously met against real NCBI data load and types. This may include unit and other regular automated QA tests run against this data, such as large file types, combinations of large files in different component types, and XML complexity use cases in chapter-processed books. The process will include how any issues encountered during this process will be reported and addressed.
## Testing process
TBD
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature. -->
## Acceptance criteria
- A documented process for how all stress test and processing issues including crashes using the NCBI data in Coko QA environment will be regularly monitored, troubleshoot, and timely addressed to meet MVP BCMS user story specifications
- Logging of any bug issues once this QA process is implemented with agreement they will be addressed for MVP deployment, unless NCBI agrees they can be postponed
## Definition of ready
<!-- A checklist of what needs to be done to a product backlog item before the team can start implementing it in the next sprint. -->
- [ ] BCMS User Story / Context has been well defined
- [ ] The priority of the user story is specified and agreed
- [ ] Digital assets added (design, database scheme, mockups etc if relevant)
- [ ] Coko Technical Proposal approved by NCBI
- [ ] Testable Acceptance Criteria approved by NCBI
- [ ] Estimate of effort to complete (time or points)
- [ ] The issue has been broken down into development tasks (if necessary)
- [ ] Requirements Clarified
- [ ] The product owner and development team agree that the user story is ready for development
- [ ] NCBI adds “Dev_Ready”
## Definition of done
<!-- A checklist of criteria that must be completed for a story to be considered “done.” -->
- [ ] All coding tasks are finished and implemented
- [ ] QA approved
- [ ] Deployed and tested on “ncbidev” (by Coko team)
- [ ] Deployed and tested on “ncbi” (by NCBI team)
- [ ] Acceptance Criteria Met
## Implementation
<!-- A description of the steps to implement the feature. To be completed by the lead dev. If there are multiple tasks, then break these down into "task" below.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
* [x] Milestone is linked
* [ ] Iteration is linked
* [ ] Dependencies: ("None" or list issue numbers if relevant)
* [ ] Development estimate is added to issue time tracking
---P02: Performance and Infrastructure MVP improvements for expected production stress loadshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1631Support added GeneReviews Editorial note in chapter-processed book metadata UI2024-01-16T08:13:54ZStacy LathropSupport added GeneReviews Editorial note in chapter-processed book metadata UI<!-- 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? -->
GeneReviews has added a new Editorial Note in Production we need support for in the MVP BCMS chapter-processed Book Metadata Notes UI fields.
## Proposal
<!-- A precise statement of the proposed feature. -->
Add an option for "Editorial note: targeted therapy" after the current "Editorial note: resources" in the Notes type selection dropdown in the chapter-processed Book Metadata UI. See below:
![image](/uploads/e5d662ec64ef12579e4a23399da808fc/image.png)
Tag this in the book metadata as below and atttached:[mdel1q21_1__1_.xml](/uploads/d0695abfd8cab0ae093790cb9ccac2bc/mdel1q21_1__1_.xml):
```
<notes>
<p content-type="genetic_counseling">
<italic>Genetic counseling is the process of providing individuals and families with
information on the nature, mode(s) of inheritance, and implications of genetic disorders to help them
make informed medical and personal decisions. The following section deals with genetic
risk assessment and the use of family history and genetic testing to clarify genetic
status for family members; it is not meant to address all personal, cultural, or
ethical issues that may arise or to substitute for consultation with a genetics
professional</italic>. —ED.</p>
<p content-type="resources">
<italic>GeneReviews staff has selected the following disease-specific and/or umbrella
support organizations and/or registries for the benefit of individuals with this disorder
and their families. GeneReviews is not responsible for the information provided by other
organizations. For information on selection criteria, click <related-object source-id="gene" document-id="app4">here</related-object>.</italic></p>
<p content-type="targeted_therapy">
<italic>In GeneReviews, a targeted therapy is one that addresses the specific underlying mechanism of disease causation (regardless of whether the therapy is significantly efficacious for one or more manifestation of the genetic condition); would otherwise not be considered without knowledge of the underlying genetic cause of the condition; or could lead to a cure</italic>. —ED</p>
</notes>
```
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature. -->
## Acceptance criteria
<!-- Provide the criteria that should be met for this feature. These criteria must be clearly defined customer requirements aligned to NCBI’s user stories in its Statement of Work. These criteria must be testable by either user testing, unit tests or integration tests.-->
- [ ] System Admin only can select an "Editorial note: targeted therapy" option after the current "Editorial note: resources" in the Notes type selection dropdown in the chapter-processed Book Metadata UI
- [ ] After a System Admin selects and saves the "Editorial note: targeted therapy" option it remains selected until user unselects it
- [ ] When the "Editorial note: targeted therapy" is selected by System Admin, the converted XML book metadata will have the following paragraph tagged in its `<notes>`: ` <p content-type="targeted_therapy">
<italic>In GeneReviews, a targeted therapy is one that addresses the specific underlying mechanism of disease causation (regardless of whether the therapy is significantly efficacious for one or more manifestation of the genetic condition); would otherwise not be considered without knowledge of the underlying genetic cause of the condition; or could lead to a cure</italic>. —ED</p>`
## Definition of ready
<!-- A checklist of what needs to be done to a product backlog item before the team can start implementing it in the next sprint. -->
- [ ] BCMS User Story / Context has been well defined
- [ ] The priority of the user story is specified and agreed
- [ ] Digital assets added (design, database scheme, mockups etc if relevant)
- [ ] Coko Technical Proposal approved by NCBI
- [ ] Testable Acceptance Criteria approved by NCBI
- [ ] Estimate of effort to complete (time or points)
- [ ] The issue has been broken down into development tasks (if necessary)
- [ ] Requirements Clarified
- [ ] The product owner and development team agree that the user story is ready for development
- [ ] NCBI adds “Dev_Ready”
## Definition of done
<!-- A checklist of criteria that must be completed for a story to be considered “done.” -->
- [ ] All coding tasks are finished and implemented
- [ ] QA approved
- [ ] Deployed and tested on “ncbidev” (by Coko team)
- [ ] Deployed and tested on “ncbi” (by NCBI team)
- [ ] Acceptance Criteria Met
## Implementation
<!-- A description of the steps to implement the feature. To be completed by the lead dev. If there are multiple tasks, then break these down into "task" below.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
* [ ] Milestone is linked
* [ ] Iteration is linked
* [ ] Dependencies: ("None" or list issue numbers if relevant)
* [ ] Development estimate is added to issue time tracking
---P03: Support valid and compliant metadata for all migrated Bookshelf contenthttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1628Switch from FTP to AWS S3 for data exchange with NCBI2024-01-30T12:16:33ZEvgenySwitch from FTP to AWS S3 for data exchange with NCBINCBI Systems is planning to prohibit ftp access from the Kubernetes cluster where BCMS is deployed, because they want to control all outgoing network connections via Istio service mesh, which does not support ftp protocol. Instead of FTP...NCBI Systems is planning to prohibit ftp access from the Kubernetes cluster where BCMS is deployed, because they want to control all outgoing network connections via Istio service mesh, which does not support ftp protocol. Instead of FTP, AWS S3 (which is accessed via HTTPS REST API) will be used for data exchange between NCBI and Coko BCMS.
NCBI will create two buckets in AWS S3 for each environment (NCBI-AWS-DEV and NCBI-AWS-PROD), one for APEX and another one for everything else (conversion, submission, package ingest etc). NCBI will specify buckets name/URL/ARN and provide AWS IAM access keys with permissions to upload/download objects in these buckets. Directory structure within S3 buckets and file naming convention will be mapped to object prefixes / names in S3 and remain the same. Kafka messages / data exchange protocol should also remain the same, except that the `package` attribute in Kafka message JSON would be used to construct an object key within a bucket, for example `"S3://ncbi-books-bcms-dev/AHRQ/hcup_sb261.zip"`
CC @latternm @lathrops1P05: Address MVP Files Management and Processing Issues to support all current Bookshelf submitters and NCBI Integration specificationshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1562Add "Sending" status to book manager chapter rows2024-01-16T17:19:02ZDione Mentisdione@coko.foundationAdd "Sending" status to book manager chapter rows## Context
Coko implemented a job queue which resolved a number of package sending and receiving issues. What this means:
* If there are 10 chapters submitted to conversion,
* chapter 1 is sent, then chapter 2, then chapter 3, etc.
...## Context
Coko implemented a job queue which resolved a number of package sending and receiving issues. What this means:
* If there are 10 chapters submitted to conversion,
* chapter 1 is sent, then chapter 2, then chapter 3, etc.
The result in the UI is it that can take longer for users to see the status change, for example, from "new upload" to "converting", especially when the queue is long. This has resulted in a number of queries to NCBI Bookshelf staff from submitters thinking the BCMS is broken. It has also resulted in submitters pressing "Submit" multiple times sending multiple jobs to the pipeline causing delays and failures.
Users should see the result of their action in the UI immediately. At the moment they will see a "Submitting" spinner for the time it takes to send the first package, then that chapter's status will update to "converting."
Consequently there can be *no visible change* on other chapters that we selected and submitted in bulk for a while, which may lead to confusion.
## Proposal
* Implement an interim status called "Sending"
* Apply new status to all use cases:
* sending for conversion
* sending for previewing
* sending for publishing
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature. -->
TBD
## Acceptance criteria
- [ ] When user presses "Submit" to bulk send more than one component to Converting, user sees "Sending" for all Components until they reach their turn in queue to changing to "Converting"
- [ ] When user presses "Reload Preview" to bulk send more than one component to Loading Preview, user sees "Sending" for all Components until they reach their turn in queue to changing to "Loading Preview"
- [ ] When user presses "Publish" to bulk send more than one component to Publishing, user sees "Sending" for all Components until they reach their turn in queue to changing to "Publishing"
- [ ] User can Filter by the status "Sending" from main Dashboard for Book Components and from Book Manager for Book Part Components
- [ ] User can Retrigger any Component stuck in "Sending" from the Jobs UI
## Definition of ready
<!-- A checklist of what needs to be done to a product backlog item before the team can start implementing it in the next sprint. -->
- [ ] BCMS User Story / Context has been well defined
- [ ] The priority of the user story is specified and agreed
- [ ] Digital assets added (design, database scheme, mockups etc if relevant)
- [ ] Coko Technical Proposal approved by NCBI
- [ ] Testable Acceptance Criteria approved by NCBI
- [ ] Estimate of effort to complete (time or points)
- [ ] The issue has been broken down into development tasks (if necessary)
- [ ] Requirements Clarified
- [ ] The product owner and development team agree that the user story is ready for development
- [ ] NCBI adds “Dev_Ready”
## Definition of done
<!-- A checklist of criteria that must be completed for a story to be considered “done.” -->
- [ ] All coding tasks are finished and implemented
- [ ] QA approved
- [ ] Deployed and tested on “ncbidev” (by Coko team)
- [ ] Deployed and tested on “ncbi” (by NCBI team)
- [ ] Acceptance Criteria Met
## Implementation
<!-- A description of the steps to implement the feature. To be completed by the lead dev. If there are multiple tasks, then break these down into "task" below.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
* [ ] Milestone is linked
* [ ] Iteration is linked
* [ ] Dependencies: ("None" or list issue numbers if relevant)
* [ ] Development estimate is added to issue time trackingP05: Address MVP Files Management and Processing Issues to support all current Bookshelf submitters and NCBI Integration specificationshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1492Not all suppl files are sent to PMC ingest when multiple files with same base...2024-01-08T22:59:34ZStacy LathropNot all suppl files are sent to PMC ingest when multiple files with same base name but different file extension<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
All suppl files uploaded to BCMS UI should be packaged and sent to PMC ingest to avoid loading errors.
## Current behaviour
When multi...<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
All suppl files uploaded to BCMS UI should be packaged and sent to PMC ingest to avoid loading errors.
## Current behaviour
When multiple suppl files are upload to BCMS UI with same base name but different extensions not all of them are package and sent to PMC for ingest causing loading errors.
## Steps to reproduce
1. Go to: https://ncbi.cloud68.co/organizations/3c48a8ec-05e4-465c-b9ea-b1cb93c688ac/bookmanager/797a661f-eab3-4c6c-a970-7e66bbdca49e -note loading error
2. Look at all files in suppl folder in UI
3. See that not all files were sent in package sent to ingest attached - [bcms6774.640b1a.2023_02_23-03_30_17.zip](/uploads/b0079d8d2ce25880b7a810697eae7877/bcms6774.640b1a.2023_02_23-03_30_17.zip)
4.
## Environment
<!-- Required. Provide relevant information such as browser name and version, PC or Mac use, internet speed, etc.]-->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->
## QA Steps
[To be completed by Coko once dev is done]
## Scheduling
<!-- Select all the relevant options -->
- [ x] This issue is blocking current user testing
- [ ] This issue is blocking current migration testing
- [ x] Fixing this issue is required for [Priority 1: Deploy MVP](https://gitlab.coko.foundation/groups/ncbi/-/epics/56)
- [ ] This issue should be triaged into later epics in the PM weekly meetingP05: Address MVP Files Management and Processing Issues to support all current Bookshelf submitters and NCBI Integration specificationshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1491Not all section titles are written into TOC.xml as required2024-01-16T17:36:48ZStacy LathropNot all section titles are written into TOC.xml as required
## Expected behaviour
Per TOC.xml writing specifications, all sections / parts should be written into the TOC.xml
## Current behaviour
Some sections are not getting written into TOC.xml per migration testing.
## Steps to reproduce
...
## Expected behaviour
Per TOC.xml writing specifications, all sections / parts should be written into the TOC.xml
## Current behaviour
Some sections are not getting written into TOC.xml per migration testing.
## Steps to reproduce
1. Go to: https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/ec697f80-db87-4094-8af3-cd796e8049c1/toc/25d90194-0a0a-44c0-aa99-04e839a9afc3
2. Go to TOC Preview: see:
![Screenshot_2023-10-11_at_09.55.18](/uploads/5f2330bec03ee686c89d517c8a4c30c9/Screenshot_2023-10-11_at_09.55.18.png)
3. Download TOC.XML and see only that section was tagged:
[TOC__47_.xml](/uploads/e70dae0fd766652752365dd9bf2c5ca7/TOC__47_.xml)
4. Compare to chapter XML which has many more sections that should have been tagged in TOC.xml: https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/ec697f80-db87-4094-8af3-cd796e8049c1/8a23e0b0-801d-41b6-ab33-f3b6ebc5c742#5ccc8109-867a-4df9-8b96-83b08dd353e4 - [wt605742_ch7__1_.xml](/uploads/de650a3018605e77ecaa613a737e3601/wt605742_ch7__1_.xml)
![Screenshot_2023-10-11_at_09.57.39](/uploads/8b5b49d001dceb19c10779f30ac5188c/Screenshot_2023-10-11_at_09.57.39.png)
## Environment
<!-- Required. Provide relevant information such as browser name and version, PC or Mac use, internet speed, etc.]-->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->
## QA Steps
[To be completed by Coko once dev is done]
## Scheduling
<!-- Select all the relevant options -->
- [ ] This issue is blocking current user testing
- [ x] This issue is blocking current migration testing
- [ x] Fixing this issue is required for [Priority 1: Deploy MVP](https://gitlab.coko.foundation/groups/ncbi/-/epics/56)
- [ ] This issue should be triaged into later epics in the PM weekly meetingP04: Support valid and compliant TOC XML for all migrated Bookshelf contenthttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1490Loading error because both source and converted XML sent in ingest package2024-01-08T22:59:34ZStacy LathropLoading error because both source and converted XML sent in ingest package@DioneMentis @douglassue
## Expected behaviour
Ingests should load without error if converted XML is valid and meets Bookshelf tagging guidelines.
## Current behaviour
Ingests are failing for chapters because both source and convert...@DioneMentis @douglassue
## Expected behaviour
Ingests should load without error if converted XML is valid and meets Bookshelf tagging guidelines.
## Current behaviour
Ingests are failing for chapters because both source and converted XML are sent in ingest packages and system does not know which file of same name and extension to read.
## Steps to reproduce
1. Go to: https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/7fb00b76-dd57-4ce8-881c-d503ac6249c5/80b6a22a-1468-44a4-8e19-6d0e093f20f9#0b681b1c-5fe7-47e7-a8e7-548b07d238e9
2. See attached ingest package that shows both source and converted files are sent: [bcms7148.chapter7.1.6b95d0.2023_04_27-04_54_46.zip](/uploads/26ec461fce3492a3e3c87fc45aa0b47a/bcms7148.chapter7.1.6b95d0.2023_04_27-04_54_46.zip)
## Possible solution
Only send converted files for ingests.
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->
## QA Steps
[To be completed by Coko once dev is done]
## Scheduling
<!-- Select all the relevant options -->
- [ ] This issue is blocking current user testing
- [x] This issue is blocking current migration testing
- [x] Fixing this issue is required for [Priority 1: Deploy MVP](https://gitlab.coko.foundation/groups/ncbi/-/epics/56)
- [ ] This issue should be triaged into later epics in the PM weekly meetingP05: Address MVP Files Management and Processing Issues to support all current Bookshelf submitters and NCBI Integration specificationshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1489Unable to upload images to wholebook images folder2024-01-16T17:28:32ZStacy LathropUnable to upload images to wholebook images foldercc @douglassue
## Expected behaviour
BCMS needs to support upload of all image files to their wholebook in one bulk action as long as those images meet Bookshelf file submission specifications.
## Current behaviour
Bookshelf submitt...cc @douglassue
## Expected behaviour
BCMS needs to support upload of all image files to their wholebook in one bulk action as long as those images meet Bookshelf file submission specifications.
## Current behaviour
Bookshelf submitter provided a submission with over 300 images files that all together are 7 GB. Submitter tried to upload all images to their wholebook but was unable. I reproduced this - after ~80 minutes I got a JSON pop up error that for some reason my video recording did not capture. The saving progress where the Save button stopped and
## Steps to reproduce
1. See: https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/1dd6e2bb-c601-4491-9a5f-f275d88948ee
2. Try to upload images in this package to the Files folder: `/am/ftp-private/bookshelf/coko/samples/iarcwcr_images.zip`
3. See that after about ~80 minutes when you do not move from that page you get a red pop up JSON error
## Environment
N/A
## Possible solution
The estimate here is to fix the bug (i.e. what causing the "JSON pop up error").
Navigating away from the page and handing bulk uploads requires the feature described in #1497.
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->
## QA Steps
[To be completed by Coko once dev is done]
## Scheduling
<!-- Select all the relevant options -->
- [ ] This issue is blocking current user testing
- [ ] This issue is blocking current migration testing
- [ ] Fixing this issue is required for [Priority 1: Deploy MVP](https://gitlab.coko.foundation/groups/ncbi/-/epics/56)
- [ ] This issue should be triaged into later epics in the PM weekly meetingP05: Address MVP Files Management and Processing Issues to support all current Bookshelf submitters and NCBI Integration specificationshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/1488User unable to Submit New Upload Source file when Converted BXML is in Previe...2024-01-08T23:03:49ZStacy LathropUser unable to Submit New Upload Source file when Converted BXML is in Previewing Status - Submit Button Greyed Outcc @douglassue @kin
## Expected behaviour
Per status / action rules (https://docs.google.com/spreadsheets/d/1M4ZdBbzr2s4-PUXqEblfsKoPBUuk4aG343u9ZAUn_Tk/edit#gid=625909583), user should be able to Submit a New Upload of a Source file....cc @douglassue @kin
## Expected behaviour
Per status / action rules (https://docs.google.com/spreadsheets/d/1M4ZdBbzr2s4-PUXqEblfsKoPBUuk4aG343u9ZAUn_Tk/edit#gid=625909583), user should be able to Submit a New Upload of a Source file.
## Current behaviour
User is unable to Submit a New Upload of a Source file because the Submit button is greyed out. This seems to happen when the Converted BXML file is in a Previewing Status.
## Steps to reproduce
Case 1:
1. Go to: https://ncbi.cloud68.co/organizations/b2223519-5e84-453f-b494-c4bee4427bf5/bookmanager/24a7b586-cb0e-472e-bf75-17524def0760
2. See Cannot Submit the Source file in New Upload
3. See it is not a problem with the Source / Converted file, per this test: https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/5fa0e015-b26e-4eaa-b91f-e90d671b29b1
Case 2:
1. Go to: https://ncbi.cloud68.co/organizations/97635691-11c5-482c-adcb-d16e69b49e79/bookmanager/39863de9-5a40-416b-bfa4-36d58981349c
2. See Cannot Submit the Source file in New Upload
3. See it is not a problem with the Source / Converted file, per this test: https://ncbi.cloud68.co/organizations/308db55a-21c9-4a64-9a70-d5aa7574726c/bookmanager/1c55275a-21bf-45a2-abfe-c4b07f236eaf
## Environment
N/A
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->
## QA Steps
[To be completed by Coko once dev is done]
## Scheduling
<!-- Select all the relevant options -->
- [ ] This issue is blocking current user testing
- [ ] This issue is blocking current migration testing
- [ ] Fixing this issue is required for [Priority 1: Deploy MVP](https://gitlab.coko.foundation/groups/ncbi/-/epics/56)
- [ ] This issue should be triaged into later epics in the PM weekly meetingP05: Address MVP Files Management and Processing Issues to support all current Bookshelf submitters and NCBI Integration specifications