SHARE Update, February 2015

What’s New?

Launch of SHARE Joint Working Group

Over the course of 2014, SHARE greatly benefited from community participation in our four working groups—Workflow, Technical, Repository Community, and Communications. These groups contributed substantially in the following areas:

  • Defining the scope of the Notification Service
  • Identifying potential roadblocks in the Notification Service development process
  • Refining our communication strategy as we talk with a range of stakeholders
  • Holding us accountable for our commitments
  • Serving as a sounding board on a variety of issues

Starting this month, SHARE has moved to a single SHARE Joint Working Group structure. The aim of this transition is to create a more efficient workflow for all parties, and inject the discussions with the type of cross-functional expertise that so energized our fall 2014 face-to-face meeting.

Much of the actual work performed by working group participants will move to task groups designed to allow participation across the old working group boundaries, encourage community leadership, and ensure that participants know the purpose and duration of their commitment. Each task group will have a defined charge, life span, and leadership.

We are pleased that the vast majority of members from the original four working groups will be joining us in this new structure. We will continue to benefit from their wise counsel and candid feedback.

Technical Update

As we move towards the release of the public beta of the SHARE Notification Service, the Center for Open Science has continued to focus on making improvements to the stability, usability, and support structure of the service. We have centralized the harvester code under one repository, to make discovery, documentation, and testing more streamlined. We have also examined databases to replace our current storage solution that would continue to expand the scalability and flexibility of the SHARE backend. We have written prototypes for a variety of database options to examine how they will work with our system in practice. We expect to launch the public beta later this spring.

What’s Next?

SHARE Notify: On the Path to Beta

While we have added a number of new providers to the Notification Service prototype, our primary focus has turned to making the improvements necessary for a beta launch later this spring. Tasks include reviewing code already in place, creating clearer documentation, testing the push protocol, and more. The heaviest work, though, will be in two areas: (1) creating a self-registration process for providers and consumers and (2) nailing down our beta metadata schema.

Managing self-registration not only requires a web tool for the registration, but also the workflow to handle parties as they register and some policy work on the way we want to frame metadata rights issues for those joining SHARE as providers.

A task group of the Joint Working Group is building the beta metadata schema, which we hope to provide to our developers at the end of February.

As we move toward beta we are rebranding the Notification Service as “SHARE Notify,” a more active name.

Learn More

As always, there is a wealth of resources at your disposal to help you better comprehend and communicate the ins and outs of SHARE, including:

  • SHARE Knowledge Base — provides short, non-technical answers to key SHARE questions ranging from “Who is behind SHARE?” to “What is SHARE doing about data?” If you or someone on your campus has a practical or conceptual question about SHARE, the Knowledge Base is likely to have your answer.
  • SHARE Webinars — recordings and slides of three recent webinars presented by the SHARE team as part of the DuraSpace Hot Topics Webinar Series. The presentations cover the motivation behind SHARE, the Notification Service’s progress to date, and SHARE’s future.
  • EDUCAUSE Review article on SHARE — Tyler Walters and Judy Ruttenberg describe SHARE’s first project, the SHARE Notification Service, as well as the other three layers of SHARE that will be developed in tandem with the Notification Service: a distributed content and registry layer, a discovery layer, and a content-aggregation layer that moves beyond curation and discovery to facilitate data and text mining.
  • SHARE Notification Service Project Plan (PDF) — details the first in a series of activities to be undertaken by SHARE to ensure that scholarly research outputs are discovered and built upon in a manner that facilitates and accelerates the research process.
  • SHARE on GitHub — Technical developments pertaining to the SHARE Notification Service are discussed and tracked in real time via GitHub. The SHARE GitHub site includes a list of active notification sources and consumers, as well as information regarding prototypes, APIs, and other key issues. The site is open and welcomes public input.
  • Supporting Organizations — SHARE is a higher education and research community initiative to ensure the preservation of, access to, and reuse of research outputs. We are pleased that a wide array of stakeholders endorse these goals. If you would like to add your organization to this list, please e-mail share@arl.org.

Acknowledgments

The SHARE Notification Service is being developed with the generous support of the Institute of Museum and Library Services (IMLS) and the Alfred P. Sloan Foundation.

Comments, Questions, Conversation

Wide community input is vital for the success of the SHARE initiative.

Please contact us with feedback, inquiries, and to join the conversation about SHARE.

Please sign up to receive this update via email.

We are always looking for volunteers for future participation.