Skip to content

Using the Issue Tracker

efc edited this page Oct 15, 2014 · 2 revisions

Please include one of these tags at the beginning of your issue title.

[core]: An issue regarding SHARE core, also known as scrAPI.

[schema]: An issue regarding the 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.

[content provider]: Information about a new service to be added to scrAPI that (1) is on the SHARE priority list and has been vetted and met required SHARE criteria or (2) may be a priority for other reasons and has an API. Once technical evaluation is completed, a new issue with the tag [consumer] should be created, and the [content provider] issue should be closed with a link to the new issue.

[consumer]: An issue regarding a consumer that is currently being developed. These issues should include a link to the primary github repo for the consumer. Consumer in this context means an application which accesses a service via API, consumes the content, and normalizes it for inclusion in the search engine in scrAPI. Note that this is distinct from "consumer" in the context of the SHARE Notification Service Architectural Overview where "consumer" refers to the subscriber to notifications.

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