As presented by Eric Celeste to the DLF Forum, October 2014.

1. ANUPDATEONSHARE
DLFForum
EricCeleste,SHARETechnicalDirector,efc@clst.org
27October2014

2. SHARE
Facilitating
preservation,
access,
and reuse
of research output.

3. WHATWE’VEBEENDOING
Joint initiative of ARL,AAU,APLU (Summer 2013)
Incorporated community feedback (through 2013)
Convened advisory board and working groups
Presented initial SHARE vision (December 2013)
Developed Notification Service Plan (early 2014)
IMLS and Sloan Support for NS (Summer 2014)
Building prototype Notification Service (ongoing)
Beginning to plan for “registry”

4. OURCHALLENGES
Infrastructure
Workflow Policy

5. WHATWEAREABOUT
Facilitating
preservation,
access,
and reuse
of research output.
Infrastructure
Workflow Policy

6. RESEARCHRELEASEEVENTS
Data SetsArticles
Preprints

7. CONSUMERSOFRESEARCHRELEASEEVENTS
FundersCampus
Repositories
Sponsored
Research Offices

9. SHARE
Notification
Service

10. CENTERFOROPENSCIENCE
“We foster openness,integrity,
and reproducibility of scientific research”
centerforopenscience.org & osf.io

11. THETEAMATCOS

12. SHARE
Notification
Service

21. STATUSATENDOFSUMMER
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.

22. RESEARCHRELEASEEVENTREPORTS
Only a dozen sources (how do you count CrossRef?)
Over 40,000 reports

23. PROTOTYPEPLANSTHISFALL
Plans for prototype expansion include:
10 more campus sites from DuraSpace
and bepress;
More data,perhaps Data Management
Plans;
At least one more agency;
150 more research release events.

24. NEXTSTEPS
Push protocol
Creation of a “push API” to make participation simpler for some
sources.
Consumption of notifications
Provide subscription methods
Recruit trial subscribers and use cases
Public release
Early 2015 beta release
Fall 2015 first full release

25. SOMEEARLYLESSONS
Clarity about intent to share.
Some sites not sure about their right to,for example,share
abstracts.
Encourage collection of vital metadata.
Most of our sources do not even collect email addresses of
authors,much less more effective identifiers such as ORCID or
ISNI. Most sources make no effort to collect funding information
or grant award numbers. We need this data to make effective
notifications.
Importance of the SHARE Registry.
Some consumers will want the enhanced records it will provide.

26. SHARE
Notification
Service
SHARE
Registry
SHARE
Discovery
For Systems via Protocol & API For People
timely,structured,
comprehensive
organized and
related source of
linked data
searchable and
friendly

27. SHARE
Notification
Service
SHARE
Registry
SHARE
Discovery
For Systems via Protocol & API For People
http://bit.ly/shareregistry

28. CHALLENGES
Adoption of key identifiers not yet
widespread,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.

29. 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,
Relationships between narrative and
supporting works more evident.

30. bit.ly/sharegithub
facebook.com/SHARE.research
twitter.com/share_research
share@arl.org
efc@clst.org
tyler.walters@vt.edu

31. QUESTIONS?