The full text of this article
Who is open data for and why could it be hard to use it in the digital humanities? Federated application programming interfaces for interdisciplinary research
by Go Sugimoto
International Journal of Metadata, Semantics and Ontologies (IJMSO), Vol. 12, No. 4, 2017
Abstract: Open data has prevailed across the research community for the past few years. However, there are a number of reasons why data reuse could be hard for digital humanities scholars. This paper is based on an application that addresses the issues of data-owning culture, interdisciplinary studies, and distributed-data research in terms of Application Programming Interface (API) and open data. The James Cook Dynamic Journal assists users to study the Cook's journal, by aggregating information from various sets of APIs that facilitate full-text search, named entity recognition, and map views. The development of the application revealed some critical issues of data federation and processing automation. In particular, the standardisation of JSON and the development of user-friendly GUI tools would significantly increase the value of APIs. The paper also proposes 'Easy Data' to avoid a digital divide and to liberate open data for a wider spectrum of users.
Online publication date: Tue, 17-Jul-2018
is only available to individual subscribers or to users at subscribing institutions.
Go to Inderscience Online Journals to access the Full Text of this article.
Pay per view:
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.
Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Metadata, Semantics and Ontologies (IJMSO):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable).
See our Orders page to subscribe.
If you still need assistance, please email firstname.lastname@example.org