SHARE update
Tyler Walters, SHARE director and dean of libraries at Virginia Tech
Erice Celeste, SHARE technical director
Jeff Spies, Co-founder/CTO at Center for Open Science
Share is a higher education initiative to maximize research impact. (huh?)
Sponsored by ARL, AAU, APRU.
Knowing what’s going on and keeping informed of what’s going on.
Four working groups addressing key tasks: repository, workflow, technical, communication
Received $1 million from IMLS and Sloan to generate a notification service.
SHARE is a response to the OSTP memo, but roots before that.
Infrastructure: Repositories, research network platforms, CRIS systems, standards and protocols, identifiers
Workflow – multiple silos = administrative burden
Policy – public access, open access, copyright, data management and sharing, internal policies.
Insittutional context: US federal agencies join growing trend to require public access to funded research; measureable proliferation of institutional and disciplinary repositories; premium on impact and visibility in higher ed.
Research Context – Scolarly outcomes are contextualized by materials generated in the process and aftermath of scholarly inquiry. Research process gendrates materials covering methods employed, evidence used, and formative discussion.
Ressearch libraries: collaboration among institutions going up; shift from collections as products to collections as components of the academy’s knowledge resources; library is supporting and embedded within the process of scholarship.
Notification Service: Knowing who is producing what, and under whose auspices, is critical to a wide range of stakeholders – funders, sponsored research offices, etc.
Researchers produce articles, preprints, presentations, datasets, and also administrative output like grant reports and data management plans. Research release events. Meant to be public.
Consumers of research release events: repositories, sponsored research offices, funders, public. Interest in process as well as product. Today each entity must relate arrange with one another to learn what’s going on. Notification service shares metadata about research release events.
Center for open science has partnered with SHARE to implement notification service. http://bit.ly/sharegithub/
Looking for feedback on proposed metadata schema, though the system is schema agnostic.
API – push API and content harvesters (pulling data in from various sources). Now have 24 providers and adding more. 16 use OAIPMH while 8 use non-standard metadata formats.
Harvested data gets put into open science framework – pushes out RSS/Atom, PubSubHubbub, etc. Sit on top of elastic search. You can add a lucene format full-text search to a data request.
250k research release events so far.arxiv and crossref are largest providers. Averaging about 900 events per day. Now averaging 2-3k per day in last few days as new providers are added.
Developed push protocol for providers to push data rather than waiting for pull.
Public release: Early 2015 beta release, fall 2015 first full release.
Some early lessons: Metadata rights issues – some sites not sure about thier right to, for example, share abstracts; Is there an explicit license for metadata (e.g. CC Zero)?;
Inclusion of identifiers – need some key identifiers to be available in order to create effective notifications. Most sources to not even collect email addresses of authors, much less ORCID or ISNI. Most sources make no effort to collect funding information or grant award numbers. Guidelines? See https://www.coar-repositories.org
Consistency across providers – reduce errors, simplify preparing for new providers. Required for push reporting.
Next layer: Reconciliation service – takes output of notification service to create enhanced and interrelated data set.
Share Discovery – searchable and friendly.
Phase 2 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.
Relation to Chorus – when items get into Chorus it is a research release event, hopfully will get into notification service.
Oren Sreebny 