Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
stylecircle

Introduction

The The Arcadia-funded COAR Notify Project is developing and accelerating community adoption of a standard, interoperable, and decentralised approach to linking research outputs hosted in the distributed network of repositories with resources from external services such as overlay-journals and open peer review services, using linked data notifications. As part of this project, COAR is funding the development of platforms and systems to support the exchange of linked data notifications across partner organisations and the workflows to manage notifications in those platforms and systems. As the largest adopted repository platform in the World one of the first platforms to be addressed is DSpace the implementation of which has been entrusted to 4Science.

...

The context section is the same for any LDN NotificationNotification 

  "@context": [


    "https://www.w3.org/ns/activitystreams",


    "https://purl.org/coar/notify"
  ]
]

actor

This section describes the actor which performs the request
This is a descriptive section and doesn't include important information

  "actor": {


    "id": "https://
research
review-
organisation
service.
org
com",


    "name": "
Research Organisation",
"type":"Organization"
}

context

...

Review Service",
    "type": "Service"
  }

context

This is one of the most important section.
In this section we have a description of the Item being involved in the LDN Notification

  • id → is the identifier URL of the item in the repository
    this field is really important to identify and link the Item to the current notification

other fields are descriptive fields for the item

  "context": {
    "id": "https://research-organisation.org/repository/preprint/201203/421/",
    "ietf:cite-as": "https://doi.org/10.5555/12345680",
    "type": "sorg:AboutPage",
    "url": {
      "id": "https://research-organisation.org/repository/preprint/201203/421/content.pdf",
      "mediaType": "application/pdf",
      "type": [
        "Article",
        "sorg:ScholarlyArticle"
      ]
    }
  }

id

The identifier of the LDN notification (Each notification has a different id)

"id": "urn:uuid:94ecae35-dcfd-4182-8550-22c7164fe23f"

inReplyTo

This field is used to reply to other LDN notification so that the system knows if the current notification is a response

"inReplyTo": "urn:uuid:0370c0fb-bb78-4a9b-87f5-bed307a509dd"

object

This is a descriptive section of the received Review, Endorsement etc..

  • id → is the URL of the review/endorsement etc.
  "object": {
    "id": "https://review-service.com/review/geo/202103/0021",
    "ietf:cite-as": "https://doi.org/10.3214/987654",
    "type": [
      "Document",
      "sorg:Review"
    ]
  }

origin

This is an important section since it is used (for incoming notifications) to determine the service among the registered ones.
If the service is not recognized as registered the notification is untrusted

The field being used for this check is inbox

  

  "origin": {
    "id": "https://review-service.com/system",
    "inbox": "https://review-service.com/inbox/",
    "type": "Service"
  }

target

This section is used to describe the target system involved in the notification workflow 

  "target": {
    "id": "https://generic-service.com/system",
    "inbox": "https://generic-service.com/system/inbox/",
    "type": "Service"
  }

type

This type section is important since it's determining how to process/evaluate any received notification

  "type": [
    "Announce",
    "coar-notify:ReviewAction"
  ]

id

object

origin

target

...




...

Testing

Request Endorsement (LDN Message on item submission)

...