EPrints Technical Mailing List Archive
Message: #08690
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] COAR Notify
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] COAR Notify
- From: Paul Walk <paul@paulwalk.net>
- Date: Fri, 6 Aug 2021 12:01:19 +0100
CAUTION: This e-mail originated outside the University of Southampton. Hi, I'd like to draw your attention to the "Notify" project from COAR. https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnotify.coar-repositories.org%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C601ceb9d92364ef34f1808d958c98634%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637638445426731461%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=tm0j4u%2BDFjx6feaRyjlfIRhSiK6k%2FiCevTSkw5jdDb4%3D&reserved=0 Based on open standards (especially Linked Data Notifications and Activity Streams 2 - both from W3C), this is a community effort to develop a widely interoperable mechanism for communicating simple "events" between repositories and related services. The idea is that many common interactions between repositories and services will involve an exchange of bi-directional links to resources. For example, a repository offers one of its pre-prints to a review service for review. If the service accepts this offer, then one outcome might be that a review is published by the review service. Notify will allow these two services to communicate these simple "events" so that the repository can link to the review from its preprint's "splash-page", and the review service's review can link to the repository's preprint. We have a number of repositories, services and organisations participating already in this project. So far we have focussed on: * establishing some common, reusable patterns for notification 'payloads' * documenting a number of scenarios involving repositories interoperating with review and endorsement services, detailing the notification-payloads used in each scenario All of this can be seen in the "Notify" website: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnotify.coar-repositories.org%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C601ceb9d92364ef34f1808d958c98634%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637638445426731461%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=tm0j4u%2BDFjx6feaRyjlfIRhSiK6k%2FiCevTSkw5jdDb4%3D&reserved=0 Technical development has begun (or in some cases is just about to begin) on some reference implementations, including a plugin for DSpace. We are looking for more repository platform communities to get involved! Cheers, Paul ------------------------------------------- Paul Walk https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.paulwalk.net%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C601ceb9d92364ef34f1808d958c98634%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637638445426731461%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=fiRapiy%2BrhOAcIVZvxBPzxrU0K9CZGnbHiPux3IRCPc%3D&reserved=0 Founder and Director, Antleaf Ltd https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.antleaf.com%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C601ceb9d92364ef34f1808d958c98634%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637638445426731461%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=m8tvQa5bgh79LwoBZEY8I6dmpuhZtNChsPU5s7iClyU%3D&reserved=0 -------------------------------------------
- Follow-Ups:
- [EP-tech] COAR Notify
- From: Paul Walk <paul@paulwalk.net>
- [EP-tech] COAR Notify
- References:
- [EP-tech] COAR Notify
- From: Paul Walk <paul@paulwalk.net>
- [EP-tech] COAR Notify
- Prev by Date: Re: [EP-tech] Adding Menu and Banner in 3.4.3
- Next by Date: [EP-tech] enlarging of text field fails?
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):