Draft Marked for review

Scenario 6: Author submits to overlay journal using repository to host resource and reviews

The corresponding author submits a paper to an overlay journal. The journal deposits the paper in a repository and arranges reviews. The reviews are deposited in the repository

Overlay Journal

Notifications

Repository

The corresponding author submits a manuscript to the journal. The journal requests that the new manuscript is ingested by the repository.

The overlay journal requests that a repository ingest an author's submitted manuscript

The @context must include:

id

Notify notifications must describe an AS 2.0 activity. The activity has an id which must be a URI, and the use of URN:UUID is recommended. An HTTP URI may be used instead, but in such cases the URI should resolve to a useful resource.

type

The activity has a type array which should be an array including Offer from AS 2.0 and coar-notify:IngestRequest from Notify.

object

The activity has an object representing the submission. The objecthas:

  • An id which is the HTTP URI of the "landing page" for the resource.
  • A type which should be an array containing AboutPage from schema.org.
  • A url containing the details of the actual content resource. The url has:
    • An id containing the HTTP URI of the content file for the resource.
    • A type describing the content file.
    • A mediaType which contains the MIME Type of the content file.

origin

The activity has an origin describing the system which has initiated the activity. The origin has:

  • An id which is an HTTP URI identifying the overlay-journal.
  • A type which should be an array including the value [Service] from AS 2.0.
  • An ldp:inbox which is the HTTP URI of the LDN inbox for the overlay-journal

target

The activity has a target describing the system which has initiated the activity. The target has:

  • An id which is an HTTP URI identifying the repository.
  • A type which should be an array including the value [Service] from AS 2.0.
  • An ldp:inbox which is the HTTP URI of the LDN inbox for the repository

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "http://purl.org/coar/notify"
  ],
  "id": "urn:uuid:0370c0fb-bb78-4a9b-87f5-bed307a509dd",
  "object": {
    "id": "https://overlay-journal.org/submissions/00001/",
    "type": [
      "sorg:AboutPage"
    ],
    "url": {
      "id": "https://overlay-journal.org/submissions/00001/files/content.pdf",
      "media-type": "application/pdf",
      "type": [
        "Article",
        "sorg:ScholarlyArticle"
      ]
    }
  },
  "origin": {
    "id": "https://overlay-journal.org",
    "inbox": "https://overlay-journal.org/requests/inbox/",
    "type": [
      "Service"
    ]
  },
  "target": {
    "id": "https://repository.org",
    "inbox": "https://repository.org/inbox/",
    "type": [
      "Service"
    ]
  },
  "type": [
    "Offer",
    "coar-notify:IngestRequest"
  ]
}
3 Ingest
The repository ingests the manuscript into a dedicated collection corresponding to the particular overlay journal

The repository notifies the overlay journal that it has ingested the resource

The @context must include:

id

Notify notifications must describe an AS 2.0 activity. The activity has an id which must be a URI, and the use of URN:UUID is recommended. An HTTP URI may be used instead, but in such cases the URI should resolve to a useful resource.

type

The activity has a type array which should be an array including Announce from AS 2.0 and coar-notify:IngestSuccess from Notify.

inReplyTo

inReplyTo is specified because this is a response to a previous notification. inReplyTo has:

  • an id which must be the URI (URN:UUID or HTTP URI) which identifies the activity for which this is a response.
  • a type array which mirrors the type of the activity for which this is a response.

object

This offer activity has an object representing the preprint. The object has:

  • An id which is the HTTP URI of the "landing page" for the resource.
  • A type which should be an array containing the value AboutPage from schema.org.
  • An ietf:cite-as which contains the persistent HTTP URI (sometimes called the "PID") which is to be used to cite or link to the resource.
  • A url containing the details of the actual content resource. The url has:
    • An id containing the HTTP URI of the content file for the resource.
    • A type describing the content file.
    • A mediaType which contains the MIME Type of the content file.

origin

The activity has an origin describing the system which has initiated the activity. The origin has:

  • An id which is an HTTP URI identifying the repository.
  • A type which should be an array including the value [Service] from AS 2.0.
  • An ldp:inbox which is the HTTP URI of the LDN inbox for the repository

target

The activity has a target describing the system which has initiated the activity. The target has:

  • An id which is an HTTP URI identifying the overlay-journal.
  • A type which should be an array including the value [Service] from AS 2.0.
  • An ldp:inbox which is the HTTP URI of the LDN inbox for the overlay-journal

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "http://purl.org/coar/notify"
  ],
  "id": "urn:uuid:94ecae35-dcfd-4182-8550-22c7164fe23f",
  "inReplyTo": {
    "id": "urn:uuid:0370c0fb-bb78-4a9b-87f5-bed307a509dd",
    "type": [
      "Offer",
      "coar-notify:IngestRequest"
    ]
  },
  "object": {
    "id": "https://repository.org/preprint/201203/421/",
    "ietf:cite-as": "https://doi.org/10.5555/12345680",
    "type": [
      "sorg:AboutPage"
    ],
    "url": {
      "id": "https://repository.org/preprint/201203/421/content.pdf",
      "media-type": "application/pdf",
      "type": [
        "Article",
        "sorg:ScholarlyArticle"
      ]
    }
  },
  "origin": {
    "id": "https://repository.org",
    "inbox": "https://repository.org/inbox/",
    "type": [
      "Service"
    ]
  },
  "target": {
    "id": "https://overlay-journal.org",
    "inbox": "https://overlay-journal.org/requests/inbox/",
    "type": [
      "Service"
    ]
  },
  "type": [
    "Announce",
    "coar-notify:IngestSuccess"
  ]
}
The journal invites reviewers
A reviewer submits a review for a manuscript. The review becomes a new repository item linked to the original manuscript. The repository notifies the journal that a new review has been submitted.

The repository notifies the overlay journal of a new review

The @context must include:

id

Notify notifications must describe an AS 2.0 activity. The activity has an id which must be a URI, and the use of URN:UUID is recommended. An HTTP URI may be used instead, but in such cases the URI should resolve to a useful resource.

type

The activity has a type array which should be an array including Announce from AS 2.0 and coar-notify:ReviewSuccess from Notify.

actor

The activity may have an actor describing the reviewer. The actor:

  • has an id which must be an HTTP URI identifying the reviewer.
  • has a type which should be an array and, in any case, must include [Person] from AS 2.0.
  • may have an ldp:inbox which must be an HTTP URI
  • may have a name

object

The activity has an object representing the repository-review. The objecthas:

  • An id which is the HTTP URI of the "landing page" for the resource.
  • A type which should be an array containing Document from AS 2.0.
  • An ietf:cite-as which contains the persistent HTTP URI (sometimes called the "PID") which is to be used to cite or link to the resource.
  • An coar-notify:reviews which contains the details of the resource which has been reviewed. The coar-notify:reviews property has:
    • An id containing the HTTP URI of the content file for the resource.
    • An ietf:cite-as which contains the persistent HTTP URI (sometimes called the "PID") which is to be used to cite or link to the resource.

origin

The activity has an origin describing the system which has initiated the activity. The origin has:

  • An id which is an HTTP URI identifying the repository.
  • A type which should be an array including the value [Service] from AS 2.0.
  • An ldp:inbox which is the HTTP URI of the LDN inbox for the repository

target

The activity has a target describing the system which has initiated the activity. The target has:

  • An id which is an HTTP URI identifying the overlay-journal.
  • A type which should be an array including the value [Service] from AS 2.0.
  • An ldp:inbox which is the HTTP URI of the LDN inbox for the overlay-journal

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "http://purl.org/coar/notify"
  ],
  "actor": {
    "id": "https://isni.org/isni/0000000122832703",
    "inbox": "https://hgwells.com/ldn/inbox",
    "name": "H G Wells",
    "type": [
      "Person"
    ]
  },
  "id": "urn:uuid:94ecae35-dcfd-4182-8550-22c7164fe23f",
  "object": {
    "coar-notify:reviews": {
      "id": "https://repository.org/preprint/201203/421/",
      "ietf:cite-as": "https://doi.org/10.5555/12345680"
    },
    "id": "https://repository.org/review/00001",
    "ietf:cite-as": "https://doi.org/10.3214/000001",
    "type": [
      "Document",
      "sorg:Review"
    ]
  },
  "origin": {
    "id": "https://repository.org",
    "inbox": "https://repository.org/inbox/",
    "type": [
      "Service"
    ]
  },
  "target": {
    "id": "https://overlay-journal.org",
    "inbox": "https://overlay-journal.org/requests/inbox/",
    "type": [
      "Service"
    ]
  },
  "type": [
    "Announce",
    "coar-notify:ReviewSuccess"
  ]
}
The journal endorses the manuscript

The overlay journal notifies the repository of its endorsement

The @context must include:

id

Notify notifications must describe an AS 2.0 activity. The activity has an id which must be a URI, and the use of URN:UUID is recommended. An HTTP URI may be used instead, but in such cases the URI should resolve to a useful resource.

type

The activity has a type array which should be an array including Announce from AS 2.0 and coar-notify:EndorsementSuccess from Notify.

object

The activity has an object representing the endorsement. The objecthas:

  • An id which is the HTTP URI of the "landing page" for the resource.
  • A type which should be an array containing Page from AS 2.0.
  • An ietf:cite-as which contains the persistent HTTP URI (sometimes called the "PID") which is to be used to cite or link to the resource.
  • An coar-notify:endorses which contains the details of the resource which has been reviewed. The coar-notify:endorses property has:
    • An id containing the HTTP URI of the content file for the resource.
    • An ietf:cite-as which contains the persistent HTTP URI (sometimes called the "PID") which is to be used to cite or link to the resource.

origin

The activity has an origin describing the system which has initiated the activity. The origin has:

  • An id which is an HTTP URI identifying the overlay-journal.
  • A type which should be an array including the value [Service] from AS 2.0.
  • An ldp:inbox which is the HTTP URI of the LDN inbox for the overlay-journal

target

The activity has a target describing the system which has initiated the activity. The target has:

  • An id which is an HTTP URI identifying the repository.
  • A type which should be an array including the value [Service] from AS 2.0.
  • An ldp:inbox which is the HTTP URI of the LDN inbox for the repository

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "http://purl.org/coar/notify"
  ],
  "id": "urn:uuid:94ecae35-dcfd-4182-8550-22c7164fe23f",
  "object": {
    "coar-notify:endorses": {
      "id": "https://repository.org/preprint/201203/421/",
      "ietf:cite-as": "https://doi.org/10.5555/12345680"
    },
    "id": "https://overlay-journal.org/articles/00001/",
    "ietf:cite-as": "https://overlay-journal.org/articles/00001/",
    "type": [
      "Page",
      "sorg:WebPage"
    ]
  },
  "origin": {
    "id": "https://overlay-journal.org",
    "inbox": "https://overlay-journal.org/requests/inbox/",
    "type": [
      "Service"
    ]
  },
  "target": {
    "id": "https://repository.org",
    "inbox": "https://repository.org/inbox/",
    "type": [
      "Service"
    ]
  },
  "type": [
    "Announce",
    "coar-notify:EndorsementSuccess"
  ]
}
The repository assigns a DOI to the manuscript and updates its metadata to indicate the new status as "endorsed".