ncbi issueshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues2020-04-13T11:10:42Zhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/32Sign up page review and fixes2020-04-13T11:10:42ZDione Mentisdione@coko.foundationSign up page review and fixesHi @John.kopanas and @danjela
This is working as expected, but there is UX one issue:
When a user signs up, the confirmation text "User has been created successfully!" appears at the top of the screen, which is out of view. I.e. the ...Hi @John.kopanas and @danjela
This is working as expected, but there is UX one issue:
When a user signs up, the confirmation text "User has been created successfully!" appears at the top of the screen, which is out of view. I.e. the user will need to scroll up to see this text, so it's not clear to the user that the sign up was successful. Can you move this confirmation text next to the 'Sign up' button?
Also, one minor correction: 'Givenname' should read 'Given name'
![ncbi](/uploads/c6dd6602c6003afe511fdf366671737e/ncbi.png)Login and registration UIsDanjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/9Register page2020-02-18T09:00:24ZDanjela Shehidanjelashehi@gmail.comRegister pageLogin and registration UIsGiannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/8Login page2020-02-18T08:59:47ZDanjela Shehidanjelashehi@gmail.comLogin pageLogin and registration UIsGiannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/138Workflow for resolving conversion errors2020-12-04T16:06:09ZDione Mentisdione@coko.foundationWorkflow for resolving conversion errorsHi @lathrops1
Here's a first draft of the wireframe for the errors tab for each book component.
![NCBI_error_tab___Figma](/uploads/a91de767715828e38da58c1c3ac18ad3/NCBI_error_tab___Figma.png)
**Workflow for conversion errors**
* A ...Hi @lathrops1
Here's a first draft of the wireframe for the errors tab for each book component.
![NCBI_error_tab___Figma](/uploads/a91de767715828e38da58c1c3ac18ad3/NCBI_error_tab___Figma.png)
**Workflow for conversion errors**
* A user uploads files which convert with errors (status = Errors reported)
* The user who uploaded the file gets notified about the errors (with link to errors tab)
* The errors are reported on this tab. The errors have two severity types: "error" and “warning”. Warnings do not need to be resolved prior to publication.
* The user who uploaded the file tries to resolve them, either by making fixes to the Word doc and uploading the corrected file or uploading missing supplementary files and reconverting the source file.
* When a new file version is uploaded (or the current file version reconverted), the previous (out-of-date) errors are moved to the history, accessible from the ‘Show history’ button.
* If there are still errors, the user needs to assign them to someone in their team or an NBCI sys admin for help. (Currently your Word users do this via email or slack.)
Questions:
1. Is there really a need to assign individual errors, as opposed the all remaining errors? Since the errors relate to one file version, only one person can fix the errors in the file at one time.
2. When errors are assigned to system admins, is the expectation that the sys admin must fix the error, or is the goal to provide the user with the information she need to fix the error herself?
@John.kopanas -- do you have any other questions?
(I'll deal with publish to PCM errors later this week).Scoping features requirementshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/25Workflow: Word-source chapters processed at book-part level2020-03-31T12:00:07ZDione Mentisdione@coko.foundationWorkflow: Word-source chapters processed at book-part levelHi @lathrops1
Attached is the Word-source workflow diagrams for your team to review. Each Step in diagram shows:
```
What the users sees/
What the user does
```
For example:
```
Book manager (Metadata modal)/
1. Add book metadata...Hi @lathrops1
Attached is the Word-source workflow diagrams for your team to review. Each Step in diagram shows:
```
What the users sees/
What the user does
```
For example:
```
Book manager (Metadata modal)/
1. Add book metadata
2. Save
```
At this stage our aim is to confirm that "what the user does" is accurate. Based on your feedback, we will review and update the current wireframes.
The Word doc has questions and comments for your attention. The PDF includes all workflow diagrams.
[Word-source_workflows_for_NCBI_review.docx](/uploads/a1df63ea9e242bbc6fccc34808013d3d/Word-source_workflows_for_NCBI_review.docx)
[SFM__Word-source_workflows-20200306.pdf](/uploads/b1d401f4c87eb8193a07c12558a3b068/SFM__Word-source_workflows-20200306.pdf)Scoping features requirementsStacy LathropStacy Lathrop2020-03-13https://gitlab.coko.foundation/ncbi/ncbi/-/issues/15Draw workflow diagram: SFM overview2020-08-06T14:18:05ZDione Mentisdione@coko.foundationDraw workflow diagram: SFM overviewHi @John.kopanas, @jure, @yannis and @danjela This diagram show an overview of the SFM workflow for content that is manually submitted.
cc @adam
![SFM-workflow-overview-20200218](/uploads/228a6e666e126c6f81c7e3f36ce1e94a/SFM-workflo...Hi @John.kopanas, @jure, @yannis and @danjela This diagram show an overview of the SFM workflow for content that is manually submitted.
cc @adam
![SFM-workflow-overview-20200218](/uploads/228a6e666e126c6f81c7e3f36ce1e94a/SFM-workflow-overview-20200218.png)
There are a lot of different tasks that can happen in the 'Editing' and 'Reviewing' states depending on the type (Word/PDF) and quality (complete/incomplete/with issues/etc.) of the files submitted. I'll break these down in more diagrams, but the important things to understand now include:
1. The **'Editing' state means preparing content for publishing**. This work is done by the Organisation team who submits the content.
2. The **'Reviewing' state means checking, resolving issues, and approving content for publishing**. Both the Organisation and NCBI teams do this work at various stages in the workflow.
3. A preview of the content is only available after it has been successfully converted to XML and pushed to NCBI's staging site.
4. There are essentially only two states that the content can be in before it is published live: Editing and Reviewing. These states can be made more meaningful for the users with standardised or customised statuses. At a minimum I think we should differentiate between content that is being reviewed by the Org or by the NCBI.
5. The Source files being managed are:
* the original source files submitted by the organisation: Word/PDF book documents and supplementary files
* the converted XML files (provided by the data supplier) that will be used for publication.
6. Versioning needs to be tracked for both original source and published source at the file and document level.
Here is an example set of files that a Org might submit manually:
![Untitled_drawing](/uploads/55dc55d71a529b4c690c94d6f8072f53/Untitled_drawing.jpg)
And here is the final published book on NCBI's Bookshelf: https://www.ncbi.nlm.nih.gov/books/n/cer141
Let me know if you have questions. I'll ask NCBI to sense-check too.
Scoping features requirementsDione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/14Draw workflow diagram: single PDF book via FTP pathway2020-03-24T15:23:20ZDione Mentisdione@coko.foundationDraw workflow diagram: single PDF book via FTP pathwayMapping out the workflow based on discussions at design meetings with NBCI and current wireframes.Mapping out the workflow based on discussions at design meetings with NBCI and current wireframes.Scoping features requirementsDione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/13Review workflow diagram: single doc XML book via FTP pathway2021-05-09T10:42:41ZDione Mentisdione@coko.foundationReview workflow diagram: single doc XML book via FTP pathwayHi @John.kopanas and @danjela
I've created a diagram to show the flow of a single document XML book via FTP pathway.
Note that a "single document XML book" means that a book's text is provided in one XML file, but there are other fil...Hi @John.kopanas and @danjela
I've created a diagram to show the flow of a single document XML book via FTP pathway.
Note that a "single document XML book" means that a book's text is provided in one XML file, but there are other files included in the FTP upload, as in the example screenshot:
## Example FTP files
![ukhsdr0807_2020-02-06_08-37-23.tar](/uploads/a40fe6ff85b24ba9c13d7a8809bbe396/ukhsdr0807_2020-02-06_08-37-23.tar.jpeg)
I've added this example book to NCBI/client-shared/sample-content/ukhsdr0807_2020-02-06_08-37-23.tar.gz
See the final published version here: https://www.ncbi.nlm.nih.gov/books/n/ukhsdr0807 (note the redirect URL is https://www.ncbi.nlm.nih.gov/books/NBK553523/)
## Workflow diagram
Here's the workflow diagram:
![workflow-single-doc-book-XML-from-FTP-20200213](/uploads/042faaf225ec4a3284b0b92321d35315/workflow-single-doc-book-XML-from-FTP-20200213.png)
## Queries to resolve
I've noted queries in orange boxes. Some of these came up during our recent design session at NCBI; others are new queries I had while drawing the workflow. We need to resolve these with NBCI, but first, please:
* [x] prioritise the queries in order or urgency -- what do you need to know asap to continue current work versus what can wait and for how long.
* [x] provide your feedback on workflow and the queries
* [x] let me know what other queries you have on this workflow
### Notes on queries
Query 2.1: What kind of unique identifier should be used?
The example file has this book ID information:
```
<book-id book-id-type="pmcid">ukhsdr0807</book-id>
<!--publisher-id: 12/209/27-->
<book-id book-id-type="doi">10.3310/hsdr08070</book-id>
<book-title-group>
```
We should not assume that this will be the ID going forward. The files provided here are for NCBI's current FTP workflow (according to [these general XML file submission specifications](https://www.ncbi.nlm.nih.gov/books/about/filespec/)) which may differ from the specifications going forward.
[workflow-single-doc-book-XML-from-FTP-20200213.pdf](/uploads/20a7fc2e38f848afd22cc07bb083eb25/workflow-single-doc-book-XML-from-FTP-20200213.pdf)Scoping features requirementshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/12scoping milestones2020-03-31T11:01:40ZGiannis Kopanasjkopanas@gmail.comscoping milestonesevaluating wireframes and functionality, so we can make solid estimations about the milestonesevaluating wireframes and functionality, so we can make solid estimations about the milestonesScoping features requirementshttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/2Data Modeling for the application2022-03-02T03:06:19ZDanjela Shehidanjelashehi@gmail.comData Modeling for the applicationExtracting the main entities of the application and tracking the relationships between them.
Organisations
Books
Divisions
Book_components
Metadata
FilesExtracting the main entities of the application and tracking the relationships between them.
Organisations
Books
Divisions
Book_components
Metadata
FilesData model design and implementationGiannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/6Questions on workflow and data modeling of the app2020-11-10T18:36:46ZGiannis Kopanasjkopanas@gmail.comQuestions on workflow and data modeling of the appGathering here questions that came up while working on data modeling.
* [x] 1. are reviews and comments related? Comments can be made only during "review" status of the book?
Comments relate to a book component version (chapter-proc...Gathering here questions that came up while working on data modeling.
* [x] 1. are reviews and comments related? Comments can be made only during "review" status of the book?
Comments relate to a book component version (chapter-processed) or a book version (book-processed)
* [x] 2. Does review mean a new version of the original book (replaced files, comments, decisions)?
Reviews happen per book component version (chapter-processed) or a book version (book-processed). A new version is created after 'Published' state
* [x] 3. What are the things that we want to track during the lifecycle of a book ? is there a need to revert to a previous state by reading the tracked events
List of activity to track for user activity stream and production reports in #209.
There is no need to revert to a previous state of the content.
* [x] 4. Preview functionality is happening only during REVIEW status? What actually is a preview of the book? Rendered content of all the chapters? using PageJS for example?
Preview link generated by NCBI and sent to BCMS. Available to view during all states except Converting and Errors
* [x] 5. only the latest generated preview is saved ? or do we need versioning on previews?
Only the latest file version
* [x] 6. Identify metadata of a book
Done in #142
* [x] 7. What are the User Preferences?
Email notification preferences (scoped at this stage for one-to-one or daily digest) #252
* [x] 8. What is the difference between Person and Unaffiliated Individual?
These user roles are not relevant anymore Data model design and implementationDione Mentisdione@coko.foundationDione Mentisdione@coko.foundation2020-02-17https://gitlab.coko.foundation/ncbi/ncbi/-/issues/194Revised workflow and wireframes for joining an org (publisher or funder)2021-03-25T09:45:43ZDione Mentisdione@coko.foundationRevised workflow and wireframes for joining an org (publisher or funder)@lathrops1
These wireframes show these features mentioned in #17
1. Define type of organisation: Funding org, Publisher, or both
1. Amend sign up so that users can sign up first, and then join an organisation.
## Define type of orga...@lathrops1
These wireframes show these features mentioned in #17
1. Define type of organisation: Funding org, Publisher, or both
1. Amend sign up so that users can sign up first, and then join an organisation.
## Define type of organisation: Funding org, Publisher, or both
When the Sys admin creates a new organization, she selects the type of organisation: 'Funder', 'Publisher' or both.
![01a-new-organization-20200924](/uploads/800ca1e647de2044f7ffff66ecf7b013/01a-new-organization-20200924.jpg)
This affects some of the default settings that will be available for that org (wireframes to come) and controls whether the organization will be listed in the dropdown for 'publisher organization' or 'funder organization' (or both) during the join org workflow described below.
## Join organization workflow
Since Investigators need to provide grant information at the time of joining an org so that the Funder org admin knows enough about the user to accept him, joining an org needs to occur after a user has signed up to the BCMS.
The 'select organization' dropdown on the sign up pages gets removed. The user signs up and sees an **empty** dashboard page and the button 'Join organization'. Users can come back to this button at any stage to join another organization if necessary.
![01-dashboard-20200924](/uploads/d9310391b1ebcbb8edd007a1caf7f136/01-dashboard-20200924.jpg)
All users will see this modal and choose whether to join a publisher or funder org.
### Join Publisher org
![02-Join-pub-org-20200924](/uploads/9f0bfa9465dabe7d85bd221dde824ea8/02-Join-pub-org-20200924.jpg)
* When the user selects 'Publisher organization' he's shown a dropdown to select the org and request an org role.
* Sys admins (assigned to the org as shown above) get notified of Org admin requests.
* Org admins get notified of Editor requests.
* To clarify: should the Org admin or all Editors get notified for all other user requests?
* The flow for assigning org roles is modified since the request to join the org can include a role.
* Admin/Editor sees pending user request in user table, as currently developed, and the individual user modals below.
**Pending user request (no role requested)**
![Pending-user-request-20200924](/uploads/af9c42cc7d61b6e8b99d14e003f8b571/Pending-user-request-20200924.jpg)
**Accepted user**
![Accepted-user-2020924](/uploads/0a2345739ea64d11608b4abb34f4f468/Accepted-user-2020924.jpg)
### Join Funding org
The same workflow as above applies when users request to join a funder org. The Funder Admin would see this screen only:
![03-Join-funding-org-as-admin-20200924](/uploads/04e0acd4200134c3ada91eeb0e5e7967/03-Join-funding-org-as-admin-20200924.jpg)
A user joining as 'Investigator' is shown this additional form to fill in.
![04-join-funding-org-as-investigator-A-20200924](/uploads/848d7a80fca5a452a8e92b9bd9ceab74/04-join-funding-org-as-investigator-A-20200924.jpg)
And the funder admin would see the information provided when accepting the user:
![06-Pending-Investigator-20200924](/uploads/5645b152674ce06141b40852b2d16065/06-Pending-Investigator-20200924.jpg)
I'll discuss the specifics of the form for the Investigator in a separate issue, for now I'd like your go ahead on this change to the workflow of joining an org. Since it affects the current sign up page our team needs to develop this before other features outlined in #17.Create and sign up to an organizationhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/41Sign up page bug: select organisation(s) from dropdown2020-04-13T18:57:22ZDione Mentisdione@coko.foundationSign up page bug: select organisation(s) from dropdown@John.kopanas
This is from NCBI's feedback in #37.
* [x] 1. The first time I select an organization to be added to when I am creating a new user account, there are no options in the dropdown area. If I leave the arrow and then selec...@John.kopanas
This is from NCBI's feedback in #37.
* [x] 1. The first time I select an organization to be added to when I am creating a new user account, there are no options in the dropdown area. If I leave the arrow and then select it again, I see the currently available organizations.
* [x] 2. When you have only one organization selected – the x in the organization box [next to the org name] doesn’t work. [You] have to use X to remove all. When you have 2 organizations selected – you can use x to remove the second, but not the first.
I have tested both bugs:
* I have the same experience for point 1.
* For point 2, when two or more organisations are selected, you can remove each organisation by selecting the X next to the org's name, except for the *last remaining* organisation. To remove the last remaining organisation, the user must select the 'remove all' X.
My question is: Assuming the bug in point 2 is fixed, do we need the 'remove all' X?Create and sign up to an organizationhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/26Admin UI wireframes (system admin point of view)2020-04-13T18:50:34ZDione Mentisdione@coko.foundationAdmin UI wireframes (system admin point of view)Hi @lathrops1
### Admin UI (System Admin)
Here are the wireframes from the point of view of the system admin. I'll post the wireframes for the Org Admin in a separate issue. Development is in progress but there are some points for cla...Hi @lathrops1
### Admin UI (System Admin)
Here are the wireframes from the point of view of the system admin. I'll post the wireframes for the Org Admin in a separate issue. Development is in progress but there are some points for clarification.
**Overview of all organisations**
On this page the Sys Admins:
1. see all organisations, and click through to each org and its users.
2. access the modal to create a new organisation
3. access the page to view and manage *all* users in the system.
Questions:
We spoke about the need to show when an organisation has signed an agreement because that needs to be in place before books can be published.
1. Will NBCI's system pass this status to our system or the other way around?
2. We have planned two possible statues: "pending" and "signed". Is this sufficient?
![Sys_admin_org_overview_page](/uploads/a8d4a9b93b62e8bc9a08dc5f6737f9fe/Sys_admin_org_overview_page.jpg)
**Create new organisation**
Clicking the "New organisation" button takes the Sys Admin here.
![Sys_admin_new_org](/uploads/20c2357349573ccbaac67c6f7d40c310/Sys_admin_new_org.jpg)
**View of one organisation**
Clicking on one organisation row (see first wireframe above) takes the Sys Admin here.
![Sys_admin_user_page](/uploads/44e58b2c5a8a0ca9fa80437e593119b6/Sys_admin_user_page.jpg)
Clicking on one user row opens the view of that user's information for the relevant organisation.
![Sys_admin_user_popup](/uploads/ca81591caf664a17d36c4a893c89d756/Sys_admin_user_popup.jpg)
**View and manage all users**
Clicking the "Users" button (see first wireframe above) takes the Sys Admin here.
![Sys_admin_all_users_page](/uploads/e61f68062817230f697848fd581d6d3f/Sys_admin_all_users_page.jpg)
Clicking on one row opens the view of that user's information across all organisations.
![Sys_admin_all_users_page_-_popup](/uploads/172f8b7c367211a67db4b2c8d1210cb2/Sys_admin_all_users_page_-_popup.jpg)Create and sign up to an organizationhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/47Integration testing (dashboard , new book)2020-04-30T09:42:15ZDanjela Shehidanjelashehi@gmail.comIntegration testing (dashboard , new book)* [x] List of books
* [x] New book* [x] List of books
* [x] New bookCreate a new book recordDanjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/46Dashboard Page: create new book record2020-04-13T19:32:45ZDanjela Shehidanjelashehi@gmail.comDashboard Page: create new book record* [x] List of books
* [x] New Book
* [x] Click book title (go to book manager)
* [x] Delete Bulk
* [x] List of books
* [x] New Book
* [x] Click book title (go to book manager)
* [x] Delete Bulk
Create a new book recordDanjela Shehidanjelashehi@gmail.comDanjela Shehidanjelashehi@gmail.comhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/87Review of bulk upload, chapter metadata, and design improvements2020-07-08T17:26:30ZDione Mentisdione@coko.foundationReview of bulk upload, chapter metadata, and design improvementsHi @lathrops1
The site is ready for your team to check here: http://ncbi.coko.foundation/
We had to remove the existing organisations, but I have create two orgs with pending users.
Please bare in mind that:
* We have not impleme...Hi @lathrops1
The site is ready for your team to check here: http://ncbi.coko.foundation/
We had to remove the existing organisations, but I have create two orgs with pending users.
Please bare in mind that:
* We have not implemented a check for uploading duplicate files nor a way to delete a book component after it's been created.
* Faking the extraction of metadata is not included in this dev, so all book component metadata fields are blank and editable.
**Bulk uploads**
See the documentation [here](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Workflows-and-wireframes/create-book-components-in-bulk). We've improved on the functionality shown in the wireframes so that users can remove files from the list of files to be uploaded, in case users select the incorrect files.
**Metadata modal**
See the documentation [here](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Workflows-and-wireframes/Book-manager-structure)
**Additional improvements**
This dev includes the following bug fixes and design improvements:
1. From your feedback in #75, we've streamlined the workflow of accepting and assigning roles. Instead of adding additional warning messages, we have made the "Accept User" and "Assign roles" bulk action buttons inactive when the action cannot be performed. This is standard practice and improves the usability. The logic is:
* Only "pending" users can be accepted or rejected, therefore the "Accept User" button is inactive for "accepted" and "disabled" users.
* Only active users (those that have been accepted and are enabled) can be assigned roles, therefore the "Assign roles" button is inactive for "pending" and "disabled" users. Similarly, on an individual user's pop up, roles cannot be assigned if the user's organisation membership is disabled.
2. #77: Accept individual users and assign role at the same time
3. #78: Add org name to user's modal
4. #81: All the fixes to the team modal from your feedback
5. From your feedback in #75, replacing the date picker in the metadata modal so it's easier to pick the year.
**Next Review**
The following feedback will be implemented in the current dev cycle, for review 22 June:
* #67: Waring message on saving the New Book modal "Please check your book settings. These settings cannot be changed after the book has been created".
* #80: Placing the lock icons closer to setting toggles and making the lock open/close for the system admin in the Settings modal.
* #79: Fixing the action/click area for the cancel button on modals.Create a new book recordDione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/53Review of development: 'create book' workflow step2020-07-06T22:56:24ZDione Mentisdione@coko.foundationReview of development: 'create book' workflow stepHi @lathrops1
This step of the workflow, described [here](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Workflows-and-wireframes/Create-new-book) and discussed in #40 is ready to review at: http://ncbi.coko.foundation/
Changes have...Hi @lathrops1
This step of the workflow, described [here](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Workflows-and-wireframes/Create-new-book) and discussed in #40 is ready to review at: http://ncbi.coko.foundation/
Changes have been made to the database so you'll need to create users and organizations again, however I have added one organization with two users as a test.
Please provide your feedback in this issue.Create a new book recordhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/40Review of 'create book' workflow and wireframes for development2021-04-16T09:19:13ZDione Mentisdione@coko.foundationReview of 'create book' workflow and wireframes for developmentHi @lathrops1
I've written up the 'create new book' workflow with the wireframes. Please review this on the wiki [here](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Workflows-and-wireframes/Create-new-book) and let us know when we ...Hi @lathrops1
I've written up the 'create new book' workflow with the wireframes. Please review this on the wiki [here](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Workflows-and-wireframes/Create-new-book) and let us know when we can expect feedback.Create a new book recordDione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/ncbi/ncbi/-/issues/35Admin page: bulk actions don't work when all records are selected2020-04-13T18:55:35ZDione Mentisdione@coko.foundationAdmin page: bulk actions don't work when all records are selected@John.kopanas
As discussed in #31, there is a bug with the *select all* box which affect the following tasks:
1. Bulk delete organisation
2. Bulk accept or reject users to an organisation
3. Bulk assign users to a team@John.kopanas
As discussed in #31, there is a bug with the *select all* box which affect the following tasks:
1. Bulk delete organisation
2. Bulk accept or reject users to an organisation
3. Bulk assign users to a teamAccept users to the organizationGiannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.com