Skip to content
erinspace edited this page Dec 5, 2014 · 14 revisions

Here is a place for a glossary of terms used throughout the SHARE project

term definition
checklist A list of questions asked of all potential providers to the SHARE NS, used to make sure SHARE is allowed to use the metadata from the provider and has current contact and API information.
consumer A consumer of the Notification Service is a system or person monitoring one of the feeds out of the service for new research release event notifications. A subscriber to notifications.
content provider A provider of research release event reports to the SHARE NS. A new content provider may be added to scrAPI when (1) it has completed an SHARE NS Checklist interview with SHARE resulting in a completed provider description or (2) it has become a priority for other reasons and has an API which the SHARE NS can use for harvesting reports.
core The core code for the SHARE Notification Service, also known as scrAPI.
harvester An application which accesses a service via API, consumes the content, and normalizes it for inclusion in the search engine in scrAPI. Formerly "consumer" - updated to avoid confusion with a "consumer of the Notification Service"
NS An abbreviation for "Notification Service."
provider Often used to mean "content provider" to the NS.
provider description A document that captures key details of the content provider's scope and API for developers. The provider description also records responses to a small set of metadata rights questions included in the SHARE NS Checklist. A list of provider descriptions is available for developers.
record The metadata gathered by a scrAPI consumer about any given resource.
report A single metadata record that was output by a scrAPI consumer. Since these consumers harvest data from providers, the consumer is actually responsible for constructing the report for SHARE. We are also planning to provide an API whereby a content provider could push reports directly into the SHARE NS.
research release event The emergence of a new research-related resource. Examples of research release events include: the deposit of a paper in a repository, the publication of an article, the submission of a data set, or the addition of a new work on a researcher's public profile.
resource The item to which a report from a content provider refers, the actual paper, data set, etc.
resource The metadata gathered by a consumer about any given resource - also a NormalizedDocument returned by scrAPI.
schema Defined representations of document types, such as what information might be required for a submission to be considered an article, citation, or dataset, or what types of information should be searchable.
scrAPI The core code for the SHARE Notification Service. ScrAPI processes documents from its various consumers and outputs the metadata in a normalized format.
scrAPI-tools A set of tools developed to facilitate the development of new consumers for SHARE content providers.
user A consumer of the notification service.

Harvester Names for Queries

This is a quick and temporary way to document the list of "short" names that are queriable as a source for notifications. A more permanent solution coming soon!

<tr>
    <td> cmu </td>
    <td> Carnegie Mellon University Research Showcase </td>
</tr>
<tr>
    <td> columbia  </td>
    <td> Columbia Adacemic Commons </td>
</tr>
<tr>
    <td> dataone </td>
    <td> DataONE: Data Observation Network for Earth </td>
</tr>
<tr>
    <td> mit </td>
    <td> DSpace@MIT </td>
</tr>
<tr>
    <td> opensiuc </td>
    <td> OpenSIUC at the Southern Illinois University Carbondale </td>
</tr>
<tr>
    <td> plos </td>
    <td> Public Library Of Science </td>
</tr>
<tr>
    <td> spdataverse </td>
    <td> Scholars Portal Dataverse </td>
</tr>
<tr>
    <td> scitech </td>
    <td> SciTech Connect </td>
</tr>
<tr>
    <td> stcloud </td>
    <td> theRepository at St. Cloud State </td>
</tr>
<tr>
    <td> uceschol </td>
    <td> California Digital Library eScholarship System </td>
</tr>
<tr>
    <td> uiucideals </td>
    <td> University of Illinois at Urbana-Champaign Illinois Digital Enviornment for Access to Learning and Scholarship </td>
</tr>
<tr>
    <td> upenn </td>
    <td> University of Pennsylvania Scholarly Commons </td>
</tr>
<tr>
    <td> utaustin </td>
    <td> University of Texas Digital Repository </td>
</tr>
<tr>
    <td> uwdspace </td>
    <td> ResearchWorks at the University of Washington </td>
</tr>
<tr>
    <td> vtechworks </td>
    <td> Virginia Tech VTechWorks </td>
</tr>
<tr>
    <td> wayne </td>
    <td> DigitalCommons@WayneState </td>
</tr>
arxiv_oai ArXiv
calpoly Digital Commons at Cal Poly
clinicaltrials ClinicalTrials.gov
crossref CrossRef
doepages Department of Energy Pages

SHARE Logo

Technical Overview

Creating a Harvester

Running Harvesters with ScrAPI

Consuming Notifications - Feed Options

Issues & Using the Issue Tracker

Metadata Schema

Glossary

Provider Names

Statistics Snapshot

Experimental Push API

Use Cases

SHARE is a project of the ARL, AAU, and APLU. Development of the SHARE Notification Service is being carried out in partnership with the Center for Open Science and is supported by generous funding from The Institute of Museum and Library Services (IMLS) and the Alfred P. Sloan Foundation.

Clone this wiki locally