Download to read offline
Uploaded byDuraSpace
12.10.14 Slides, “The SHARE Notification Service”
The Duraspace community webinar series discusses the SHARE initiative, which aims to enhance research impact through a notification service that keeps stakeholders informed about research outputs. SHARE envisions a seamless flow of information between researchers, funders, and institutions, backed by a $1,000,000 funding commitment for development. The initiative addresses challenges related to metadata rights, consistency across providers, and the need for effective communication strategies in the research community.
More Related Content
Similar to 12.10.14 Slides, “The SHARE Notification Service”
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
12.10.14 Slides, “The SHARE Notification Service”
- 1. Hot Topics: TheDuraSpace Community Webinar Series Series Ten: “All About the SHared Access Research Ecosystem (SHARE)” Curated by Greg Tananbaum, Product Lead, SHARE December 10, 2014 Hot Topics: DuraSpace Community Webinar Series
- 2. Webinar 2: TheSHARE Notification Service Presented by: Eric Celeste, Technical Lead, SHARE December 10, 2014 Hot Topics: DuraSpace Community Webinar Series
- 4. TODAY • Briefbackground on SHARE • Description of Notification Service • Early Lessons of Notification Service • Hint of plans for Phase II • Opportunities to Participate • Questions & Answers
- 5. WHO & WHATIS SHARE? SHARE is a higher education initiative to maximize research impact.
- 6. WHO & WHATIS SHARE? SHARE envisions an environment where researchers can keep interested parties seamlessly informed of their activities, where funders can easily determine the impact of their investments, and where institutions can readily collect and assess the output of their community members.
- 7. FUNDING $1,000,000 todevelop Notification Service and long term SHARE vision March, 2014 through September, 2015
- 8. MISSION Infrastructure Maximizing Research Impact Workflow Policy
- 9. NOTIFICATION SERVICE Whois producing what? and Who wants to know?
- 10. USER STORIES Asan IR Manager, I would like to know what output of our researchers is deposited in repositories at other institutions so I can approach them about a copy for our collection. I am a sponsor and I want to know what products have resulted from the research I sponsored so I can determine what additional revenue the original grant may have generated. I am the Director of Institutional Research and I’m tasked with notifying campus stakeholders, including University Communications and Office of Contracts and Grants, when our university’s faculty publishes an article (or other output) funded by an awarded grant.
- 11. RESEARCH RELEASE EVENTS Preprints Articles Data Sets
- 12. CONSUMERS OF RESEARCHRELEASE EVENTS Sponsored Research Offices Campus Funders Repositories
- 14.
- 15. CENTER FOR OPENSCIENCE “We foster openness, integrity, and reproducibility of scientific research” centerforopenscience.org & osf.io
- 16. THE TEAM ATCOS
- 17.
- 25. RSS • “ReallySimple Syndication” designed for blogs and breaking news. • Struggles with large number of updates at one time. • Very easy to set up, a fun way to see what flows through the Notification Service.
- 31. PUBSUBHUBBUB • Developedby Google • “An open, simple, web-scale and decentralized pubsub protocol. Anybody can play.” • Another way for “publisher” like SHARE to inform “subscribers” like our consumers of changes to “our content” like our notifications.
- 32. RESOURCESYNC • Developedby library community. • Uses PubSubHubbub too. • “A synchronization framework for the web consisting of various capabilities that allow third-party systems to remain synchronized with a server's evolving resources.”
- 33.
- 34.
- 35. STATUS AT ENDOF SUMMER Planned for 3 platforms, 5 institutions, 2 agencies, and 5 publishers, 50 research release events, including papers and data. COS harvesting data from Clinical Trials, DOE’s SciTech and Pages, PLoS, UC eScholarship, Wayne State Digital Commons, VTechWorks, NLM PubMedCentral, CrossRef, arXiv, and DataONE. Experimental RSS feed to see output.
- 36. RESEARCH RELEASE EVENTREPORTS Only a dozen sources Over 40,000 reports
- 37. PROTOTYPE PROVIDERS •ArXiv • California Digital Library eScholarship System • Carnegie Mellon University Research Showcase • ClinicalTrials.gov • Columbia Adacemic Commons • CrossRef • DataONE: Data Observation Network for Earth • Department of Energy Pages • Digital Commons at Cal Poly • DigitalCommons@WayneState • DSpace@MIT • OpenSIUC at the Southern Illinois University Carbondale • Public Library Of Science • Repository at St. Cloud State • ResearchWorks at the University of Washington • Scholars Portal Dataverse • SciTech Connect • University of Illinois at Urbana • University of Pennsylvania Scholarly Commons • University of Texas Digital Repository • Virginia Tech VTechWorks
- 38. STILL WORKING ON Push protocol Creation of a “push API” to make participation simpler for some sources. Consumption of notifications Provide subscription methods Recruit trial subscribers Public release Early 2015 beta release Fall 2015 first full release
- 39. SOME EARLY LESSONS Metadata rights issues. Some sites not sure about their right to, for example, share abstracts. Metadata inclusion and consistency. Most of our sources do not even collect email addresses of authors, much less universal identifiers such as ORCID or ISNI. Most sources make no effort to collect funding information or grant award numbers. This data needs to be collected and distributed to make effective notifications. The need for a Phase II. Some consumers will want the enhanced records it will provide.
- 40. METADATA RIGHTS Doesmetadata gathering violate your terms of service? If so, are we granted explicit, written rights to gather data? Does metadata gathering violate your privacy policy? If so, are we granted explicit, written rights to gather data? Does our sharing the metadata we gather from you violate your policies? If so, are we granted explicit, written license to share the metadata? Do you use an explicit license for your metadata (for example, CC Zero)? If not, do you have plans to explicitly license the content?
- 41. VARIETY AND AVAILABILITY • We accept that we will have a variety of providers with a variety of expressions. • But we need some key identifiers to be available in order to create effective notifications.
- 42. @LP@NO @NKJIN@ COOKNˆ™™AMJBRJMG?‰ JH™KD™AMJBN ¡ £ IH@ˆ@MHDO† JGJMˆBM@@I† OTK@ˆA@GO ¤† £ IH@ˆMQDN† JGJMˆBM@@I† OTK@ˆOM@@ ¤ ¢
- 43. @NJPM@¼ @NJPM@½ £ ODOG@ˆNT@DIB M@@I† JIOMD=POJMNˆ¡ @MHDO† MQDN ¢† NJPM@ˆAMJBRJMG?† D?ˆ¼»‰¼»»™AMJBRJMG?‰¼»½ ¤ £ ODOG@ˆNT@DIB M@@I† JIOMD=POJMNˆ¡ @MHDO† MQDN ¢† JMDBDIˆAMJBRJMG?† D?ˆ¼»‰¼»»™AMJBRJMG?‰¼»½† ?@NMDKODJIˆ SKGJMDIBBM@@II@NN‰ ¤
- 44. @NJPM@¼ @NJPM@½ £ ODOG@ˆNT@DIB M@@I† JIOMD=POJMNˆ¡ @MHDO† MQDN ¢† NJPM@ˆAMJBRJMG?† D?ˆ¼»‰¼»»™AMJBRJMG?‰¼»½ ¤ £ IH@ˆNT@DIB M@@I† JIOMD=POJMNˆ¡ MJBD@IODNON
- 45. IOG† HKCD=DINIDO@?† ¢† JMDBDIˆAMJBRJMG?† ?JDˆ¼»‰¼»»™AMJBRJMG?‰¼»½ ¤
- 46. @NJPM@¼ @NJPM@½ £ ODOG@ˆNT@DIB M@@I† JIOMD=POJMNˆ¡ @MHDO† MQDN ¢† NJPM@ˆAMJBRJMG?† D?ˆ¼»‰¼»»™AMJBRJMG?‰¼»½ ¤ £ ODOG@ˆNT@DIB M@@I† JIOMD=POJMNˆ¡ JJIOMD=POJMN ¢† NJPM@ˆAMJBRJMG?† D?ˆ¼»‰¼»»™AMJBRJMG?‰¼»½ ¤
- 47. @LP@NO @NKJIN@ COOKNˆ™™JNA‰DJ™KD™NCM@ £ ODOG@ˆNT@DIB M@@I† JIOMD=POJMNˆ¡ @MHDO† MQDN ¢† NJPM@ˆAMJBRJMG?† D?ˆ¼»‰¼»»™AMJBRJMG?‰¼»½ ¤ P@NN
- 48. RIOXX • Seehttp://rioxx.net/v2-0-rc-2/
- 49. OPENAIRE • Seehttps://guidelines.openaire.eu
- 50.
- 51. GUIDELINES? • Seehttps://www.coar-repositories.org
- 52. INCLUSION OF IDENTIFIERS • Researcher identifiers such as ORCID, ISNI, and so on. • Funding identifier such as FundRef. • Grant award identifiers. • Further metadata elements encouraged by COAR, CASRAI and others.
- 53. CONSISTENCY ACROSS PROVIDERS • We can manage the variety. …however… • Consistency reduces errors. • Consistency simplifies preparing for new providers. • Consistency will be required for push reporting.
- 54. SOME USER STORIESMAY NEED PHASE II As an IR Manager, I would like to know what output of our researchers is deposited in repositories at other institutions so I can approach them about a copy for our collection. I am a sponsor and I want to know what products have resulted from the research I sponsored so I determine what additional revenue the original grant may have generated. I am the Director of Institutional Research and I’m tasked with notifying campus stakeholders, including University Communications and Office of Contracts and Grants, when our university’s faculty publishes an article (or other output) funded by an awarded grant.
- 55. For Systems viaProtocol API For People SHARE Notification Service SHARE Registry SHARE Discovery timely, structured, comprehensive organized and related source of linked data searchable and friendly
- 56. CHALLENGES • Adoptionof key identifiers just getting underway, requires international collaboration, • Inferences prone to error, • Duplicate detection difficult, • Scale quite large, not well understood, • This is a never-ending task requiring sustainable funding and governance.
- 57. For Systems viaProtocol API For People SHARE Notification Service including Phase II? SHARE Discovery timely, structured, comprehensive, reconciling incoming reports with what we already know and can learn from other sources searchable and friendly
- 58. PHASE II BENEFITS • Researchers can keep everyone informed by keeping anyone informed, • Institutions can assemble more comprehensive record of impact, • Open access advocates can hold publishers accountable for promises, • Other systems can count on consistency of metadata from SHARE.
- 59. OPPORTUNITIES • Signup for monthly SHARE update • Subscribe to the RSS feed • Join the Beta in 2015 • Become a prototype participant • Look for SHARE enabling guidelines
- 60. CONTACT US www.arl.org/share bit.ly/sharegithub share@arl.org (or efc@clst.org) www.facebook.com/SHARE.research www.twitter.com/share_research