Skip to content

GitLab

Open
Created by Dione Mentis@DioneMentisMaintainer

Extend data model: Give more than one organization access to the same book

(Updated 1 July 2021 WIP)

Books in a Funding collection

Use case

  1. Organization A is a 'Funder' Org that owns a Funding collection. Organization B is a 'Publisher' Org that owns and submits books to Organization's A's collection.
  2. Only Organization A can access all books in the collection. Organization B can access whichever books they have submitted to the collection.

Real example

Here's an example of this use case showing multiple organizations submitting books to a Funded collection. In this example, Org C submits books in the XML workflow by FTP; Org D submits books in the PDF workflow (Final published PDFs specifically).

(Note: we are not supporting the Awardee role in Phase 1. These user are likely members of the 'Funder' org but they submit content through a different flow.)

funding-collection-WT

Other examples here.

Create book specs

  1. When a book is submitted to a Funding collection, create the PMCBook domain using the Publisher Org's domain template (Org B in use case example) and link the domain to this publisher (i.e. send Org B's publisher abbreviation in the domain request.)
  2. The book should inherit the collection's metadata (detail to be expanded: at what point and how this happens).
  3. Once the domain is created, update book-collection-name attribute to match selected collection.

funding-collection-flow

Questions to resolve

  1. Can collection owner Org add their org members to the book or chapter team?
  2. Can collection owner Org publish publish books? If yes, any book or only the ones submitted by their organization?
  3. Can collection owner Org add the Publisher Org members to the book or chapter team? If yes, which roles?
  4. Can Publisher Org add the collection owner Org members to the book or chapter team? If yes, which roles?

Books in Published Series collection

Use case

  1. Organization A owns Published Series a collection owns and submits books to Organization's A's collection.
  2. Only Organization A can access all books in the collection. Organization B can access whichever books they have submitted to the collection.

(Note: It's not clear from current use cases whether these orgs are always the 'Publisher' type. We could build flexibility so any type of org can create and submit to a Published Series collection.)

Create book specs

  1. When a book is submitted to a Published Series collection, create the PMCBook domain using the collection as the domain template and link the Collection owner to the domain (i.e. send Collection owner's publisher abbreviation in the domain request.)
  2. The book should inherit the collection's metadata (detail to be expanded: at what point and how this happens).
  3. Once the domain is created, update book-collection-name attribute to match selected collection.

pubseries-collection-flow

[Original issue]

Originally discussed in #53 (closed) here, I'm copying the relevant feedback -- this applies to PDF and XML workflows.

COKO

Queries

Is there an assumption Organization Publisher? Or will Publisher be= clearly set in the Book metadata table? Also, what happens if there are two Organizations involved - you can only select one.

Can we confirm that for one book or collection belonging to more than one org:

  • This applies when there is a funder. The funder is an organization (in our system)
  • Usually this happens in a PDF workflow, sometimes an XML workflow
  • Sometimes, the publisher (also an organization in our system) will submit the a book funded collection (so this org needs access)

Some questions about this are :

  • Do we have one book belonging to many organizations, or one book belongs to only one organization but other organizations can have access to it (which is a different thing from the previous one)?
    • does the whole organization needs access to it, or just certain users?
  • In case we have one book belonging to many organizations, from which organizations it gets the default settings(like metadata #62 (closed) )?

NCBI

Re:

Do we have one book belonging to many organizations, or one book belongs to only one organization but other organizations can have access to it (which is a different thing from the previous one)?

So, I guess maybe I should break it down - a book may have:

  • A copyright holder (that may be an organization) or a funder directing its funded ivestigators to provide a peer-reviewed manuscript evoking their copyright
  • A publisher, which may or may not be the organization with which we have an agreement
  • A Bookshelf participant - the organization we have an agreement to include specific collections or documents in our archive

Depending on how these map to a particular piece of content we work with the Bookshelf participant to make sure the copyright holder and publisher are acurately recorded in the metadata and have as much access to the content in our system per the Bookshelf participant's agreements wit them.

  • does the whole organization needs access to it, or just certain users?

In all cases I thought only certain users acting on behalf of an organization has access to content. Or are you talking about a certain level of permissions. I would say in most cases a copyright holder and publisher may need reviewer permissios at all time, but in some cases also investigator and / or data supplier permissions.

COKO

What we're trying to clarify is whether it is even necessary for the Editor to select 2 Orgs when she create the book.

If we allow the Editor to select two organisations when creating the book, then that Editor and all Org Admins for both organisations will see the book listed in the Dashboard. Both Orgs would be able to add any of their users to the book's team, manage the book's settings and publish the book.

Is this the desired behaviour?

If not, then we can work out a simpler solution that allows users from two orgs to work on one book. The easiest way would we for these users to belong to two orgs, a feature we have previously discussed, instead of the book belonging to two organisations. Bare in mind that the book's metadata will include the copyright holders information, so there is no issue there, so long as the appropriate users have access to add/edit/review this information.

NCBI

My thinking is this (bear with me if it is not too organized) -

Content in our system is currently linked to a primary org who signs our particpant agreement, but we have a way of identifying who the funding agency, publisher and copyright holders are for that content as well.

SO

The cases in which there are often two orgs collaborating to provide us with content (usually when there is a funder and org), as long as the following uses cases ae met, then I think we can put in place your "simpler solution":

  • A funder Orgnization can find all content it has funded even if a publisher has provided the XML for it (and not the investigator) - this could be by a search and ability to pull reports not just on content associated with an org but by funding agency (and its associated grants / contracts) - these funder Orgs will likely want to have a way to report errors in funding agency / grants or associate content submitted by a publisher with their funding agency or grant / contract - NOTE when we get to PDF workflow we will need to discuss how investiagators, etc, select and add grants information, and the integration point of how the system has available all participating funder agency grants and contracts

  • A Publisher can find all content it has published - this could be by content associated with it has Org - or that it is listed as publisher in the metadata - to pull tracking reports, fix reported errors that they need to resupply, review, etc, even if they are not the primary org

  • A copyright holder can also pull reports for tracking for all contebt they own, and have access to add/edit/review even if they are not the Prinary Org

I think we'll need to talk to funders and publishers a bit more about the first two cases when we get to PDF and XML workflows based on funder policies and deposit based only on funding.

Let me know if you'd like to chat briefly about this in person tomorrow @DioneMentis - I don't know if this requires us to break down Org users into Funders and Publishers and Copyright Holders like we did for Reviewers or not to work out the best solution.

In general though, I think the simplest way we can address the uses cases, is the best.

Edited by Dione Mentis