This use case is about endorsement of repository resources, involving an endorsement service of some kind. One common example may be the publishing of repository-based resources in overlay journals, initiated either by the repository, or by the overlay journal.
In the overlay publishing model, a journal performs peer review and endorsement of an article or preprint, but it doesn’t publish articles on its website. Rather, the journal’s website links to final article versions hosted in an online repository. In some cases, the final article versions may also be mirrored on the journal website. The overlay publishing process usually involves a number of steps that can be automated using the Notify technologies.
Name | Description | Categories |
---|---|---|
Announce Endorsement | This pattern is used to announce the existence of an endorsement, referencing (in context ) the resource that has been endorsed |
Announcements |
Request Endorsement | This pattern is used to request endorsement of a resource owned by the origin system. |
Requests |
ID | Scenario | Participating Systems |
---|---|---|
1 | Author requests review with possible endorsement (via overlay journal) | Overlay Journal <-> Repository |
2 | Author requests review with possible endorsement (via repository) | Repository <-> Overlay Journal |
6 | Author submits to overlay journal using repository to host resource and reviews | Overlay Journal <-> Repository |
3 | Overlay Journal Announces Review and Endorsement of Pre-print to Aggregator | Overlay Journal <-> Aggregator |
4 | Overlay Journal Endorses Pre-print (Initiated by Author) | Overlay Journal <-> Repository |