data2semantics/linkitup

Web-based dashboard for enriching data in a Figshare repository to the Linked Data cloud

linkitup's Issues

Session cookie does not persist across requests

Fallback cache for Plugin services

Linkitup should not rely too much on SPARQL endpoints or other REST services being live (and fast). We should use some kind of caching to speed up requests. For instance using a proxy (thanks @cmarat !)

Proxy possibilities: http://mitmproxy.org , or the regular Apache proxy & cache

UI change to browse articles (page views)

Integrate with ORCID

Figshare is integrated with ORCID (Open Researcher and Contributor ID), linkitup should do so too!

Integrate with Linked Data Repository

See http://data.elsevier.com

Add plugin for DBPedia Spotlight

Send the description (or the abstract, or even fulltext) to DBPedia Spotlight to get potential tags.

Use elasticsearch to extract metadata from files

We now use custom extraction services, but elasticsearch is WAY better at doing this. So let's use it instead!

Cannot publish Nanopublication... API change at Figshare?

Add plugin for bio2rdf.org

Upload RDF metadata as Figshare publication

Speaks for itself

Use annotation format for RDF metadata

Enrichments produced by Linkitup should be represented using an annotation format (e.g. the open annotation model).

Add plugin for data.nytimes.com

Add plugin for sameas.org

Add a plugin that suggests matches to figshare 'links' on the basis of the sameas.org service.

Add plugin for Sindice

Add plugin for ConceptWiki

Add plugin for chemspider

Allow users to publish to their own SPARQL endpoint

Perhaps even allow them to specify their own namespace for their publications.

Add plugin for LinkedCT.org

Add plugin for Drugbank