ESciDoc Services DataAcquisitionHandler

ID (Label)
DAAS

Complete Name
Data Acquisition Service

Status
Implemented

Description
Acquisition Service for data from internal and external sources with an unAPI interface.

Supported Systems

 * Implemented:
 * eSciDoc [no mapping required]
 * Arxiv [find mapping here] Important Note: Fetch from arxiv will only be successful if the PubMan server is registered at arxiv.org, otherwise your fetching attempts will be blocked
 * PubMed Central [find mapping here]
 * Spires [find mapping here]
 * BioMed Central [find mapping here]


 * In Design:


 * Considered:
 * CrossRef, CoLab Page for CrossRef
 * MathNetScience
 * Astrophysics Data System (ADS)

Service interfaces
The four steps to fetch data:

1. Choose the presentation of the data
 * dataacquisition/view: Views the fetched data in the browser
 * dataacquisition/download: The fetched data will be provided as a download

2. Specify the interface you want to use (currently only unAPI)
 * dataacquisition/view/unapi
 * dataacquisition/download/unapi

3. Provide the identifier of the item you want to fetch
 * dataacquisition/view/unapi?id=escidoc:1234
 * dataacquisition/download/unapi?id=escidoc:1234

4. Provide the format you want the fetched item in
 * dataacquisition/view/unapi?id=escidoc:1234&format=bibtex
 * dataacquisition/download/unapi?id=escidoc:1234&format=bibtex

Supported Identifiers:

1. A identifier from a supported source (explained in /dataacquisition).

2. A identifier = any URL (the eSciDoc DataAcquisition Service has no information about this source and can only try to call the given URL for the fetching request).
 * The format has to be set to "url". The response will be a zip file of the fetched content. The view option for url identifiers is disabled

Future Development

 * Prioritize fetching formats for import (client or serverside?). E.g. fetch pdf if not possible fetch doc.
 * Prevent DAAS to be a security leak for the sources he fetches from.