Difference between revisions of "COAR Notify Overview"
Will.fyson (talk | contribs) (→Signposting) |
Will.fyson (talk | contribs) (→PCI) |
||
| (22 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
A collection of academic communities that self-organise peer review processes. COAR Notify enables EPrints repositories to communicate with PCI communities, facilitating a process for the peer review of preprint eprint records, allowing the repository to request reviews and handle rejections or endorsements. | A collection of academic communities that self-organise peer review processes. COAR Notify enables EPrints repositories to communicate with PCI communities, facilitating a process for the peer review of preprint eprint records, allowing the repository to request reviews and handle rejections or endorsements. | ||
| − | For more information, please see https://peercommunityin.org/ | + | For more information about PCI, please see https://peercommunityin.org/ |
| + | |||
| + | For more information about PCI in EPrints, please see [[COAR Notify: PCI]] | ||
===Inter-Repository Linking=== | ===Inter-Repository Linking=== | ||
This use case implements COAR Notify to enable repositories to announce relationships to items held within another repository. For example, where an institution may have a publications repository and a separate research data repository, items within the two can be linked using Notify's linked data notifications. | This use case implements COAR Notify to enable repositories to announce relationships to items held within another repository. For example, where an institution may have a publications repository and a separate research data repository, items within the two can be linked using Notify's linked data notifications. | ||
| − | For more information, please see [COAR Notify: Repository Linking] | + | For more information, please see [[COAR Notify#Repository Linking|COAR Notify: Repository Linking]] |
==Implementation== | ==Implementation== | ||
| Line 25: | Line 27: | ||
This is a minor change which introduces Typed Links to the HTTP response headers. These direct services to links where more information can be found about the resource usng a specified format, supporting COAR Notify's "pass by reference" approach to communication. | This is a minor change which introduces Typed Links to the HTTP response headers. These direct services to links where more information can be found about the resource usng a specified format, supporting COAR Notify's "pass by reference" approach to communication. | ||
| − | For more information about Signposting in EPrints, please see [Signposting] | + | For more information about Signposting in EPrints, please see [[Signposting]] |
For more information about Signposting, please see https://signposting.org/ | For more information about Signposting, please see https://signposting.org/ | ||
===COAR Notify=== | ===COAR Notify=== | ||
| − | The COAR Notify integration is available as either an ingredient or Bazaar plugin at https://github.com/eprintsug/coar_notify | + | The COAR Notify integration is available as either an ingredient or Bazaar plugin at https://github.com/eprintsug/coar_notify and https://bazaar.eprints.org/1257/ |
| − | + | '''Prerequisites: [[Signposting]]''' | |
This integration enables several core COAR Notify components: | This integration enables several core COAR Notify components: | ||
| Line 38: | Line 40: | ||
* LDN inbox and handler | * LDN inbox and handler | ||
* Framework for sending LDNs | * Framework for sending LDNs | ||
| − | * Repository | + | * [[COAR Notify#Repository Linking|COAR Notify: Repository Linking]] - input component, rendering and handling |
| + | |||
| + | For more information, please see [[COAR Notify]] | ||
===PCI=== | ===PCI=== | ||
| − | The PCI integration is available as either an ingredient or Bazaar plugin at: https://github.com/eprintsug/ | + | The PCI integration is available as either an ingredient or Bazaar plugin at: https://github.com/eprintsug/pci_review and https://bazaar.eprints.org/1258/ |
| − | + | '''Prerequisites: [[Signposting]]; [[COAR Notify]] ingredient/plugin.''' | |
| − | For more information please see: [COAR Notify: | + | For more information please see: [[COAR Notify: PCI]] |
==Acknowledgements== | ==Acknowledgements== | ||
COAR Notify development for EPrints has been supported by the [https://coar-repositories.org/what-we-do/notify/ COAR Notify Initiative] via funding from [https://www.arcadiafund.org.uk/ Arcadia]. | COAR Notify development for EPrints has been supported by the [https://coar-repositories.org/what-we-do/notify/ COAR Notify Initiative] via funding from [https://www.arcadiafund.org.uk/ Arcadia]. | ||
Latest revision as of 13:37, 31 July 2025
Contents
Introduction
COAR Notify is a technology for enabling the "bi-directional linking between peer review services, overlay journals and repositories". It uses "well-established W3C technologies/standards" including "linked data notifications and activity streams". For more information about COAR Notify please see: https://coar-repositories.org/what-we-do/notify/
Use Cases
COAR Notify has been implemented in EPrints with two main uses cases in mind.
Peer Community In (PCI)
A collection of academic communities that self-organise peer review processes. COAR Notify enables EPrints repositories to communicate with PCI communities, facilitating a process for the peer review of preprint eprint records, allowing the repository to request reviews and handle rejections or endorsements.
For more information about PCI, please see https://peercommunityin.org/
For more information about PCI in EPrints, please see COAR Notify: PCI
Inter-Repository Linking
This use case implements COAR Notify to enable repositories to announce relationships to items held within another repository. For example, where an institution may have a publications repository and a separate research data repository, items within the two can be linked using Notify's linked data notifications.
For more information, please see COAR Notify: Repository Linking
Implementation
COAR Notify has been integrated into EPrints through changes to the core EPrints code base as well as ingredients (for EPrints 3.4+) and Bazaar plugins (for EPrints 3.3). An overview of the changes are presented below...
Signposting
A pre-requisite for COAR Notify. Signposting has been implemented in EPrints 3.3 and 3.4.
To enable Signposting in your repository you need the following changes https://github.com/eprints/eprints3.4/pull/387
This is a minor change which introduces Typed Links to the HTTP response headers. These direct services to links where more information can be found about the resource usng a specified format, supporting COAR Notify's "pass by reference" approach to communication.
For more information about Signposting in EPrints, please see Signposting
For more information about Signposting, please see https://signposting.org/
COAR Notify
The COAR Notify integration is available as either an ingredient or Bazaar plugin at https://github.com/eprintsug/coar_notify and https://bazaar.eprints.org/1257/
Prerequisites: Signposting
This integration enables several core COAR Notify components:
- Linked Data Notification (LDN) dataset
- LDN inbox and handler
- Framework for sending LDNs
- COAR Notify: Repository Linking - input component, rendering and handling
For more information, please see COAR Notify
PCI
The PCI integration is available as either an ingredient or Bazaar plugin at: https://github.com/eprintsug/pci_review and https://bazaar.eprints.org/1258/
Prerequisites: Signposting; COAR Notify ingredient/plugin.
For more information please see: COAR Notify: PCI
Acknowledgements
COAR Notify development for EPrints has been supported by the COAR Notify Initiative via funding from Arcadia.
