A Model for Content Enrichment of Institutional Repositories Using Linked Data

ABSTRACT

Institutional repositories have positioned themselves as an essential service for many libraries. Content-enriched metadata in library records is reported as being helpful to library users in identifying and selecting information objects for their needs. The presence of this extra-enriched content helps users to decide on the relevance of the item without the need to access the full text. Through this paper, we report content enrichment of records in an Institutional Repository using Linked Open Data datasets. In particular, this is done by application of a linked dataset in an institutional repository. The design, implementation, configuration, and workflow of the application is discussed along with implications and potential future work.

KEYWORDS:

• Institutional Repository
• Linked Open Data
• Content Enrichment
• Library Online Services
• Linked Data

Acknowledgments

The author is thankful to Prof. (Ms.) Devika P. Madalli, Indian Statistical Institute, Bangalore for her guidance and the Indian Statistical Institute, Bangalore for providing a fellowship to complete this work.

About the author

Vinit Kumar is an Assistant Professor at the School of Library and Information Science, Central University of Gujarat, Gandhinagar, Gujarat, India. He is having more than 7 years of experience in teaching and research in Library and Information Science. He has successfully guided three students leading to M.Phil. (LIS) degree. His research interests are library online services, Open data, application of Semantic Web in library services and digital libraries.

Notes

¹ http://jquery.com/

² www.eprints.org/software/

³ www.greenstone.org

⁴ www.dspace.org

⁵ http://dbpedia.org

⁶ www.wiki.dbpedia.org

⁷ http://www.umbel.org/

⁸ http://jqueryui.com/autocomplete/

⁹ The same origin policy is an important security concept for a number of browser-side programming languages, such as JavaScript. The policy permits scripts running on pages originating from the same site - a combination of scheme, hostname, and port number - to access each other's methods and properties with no specific restrictions, but prevents access to most methods and properties across pages on different sites. The same origin policy also applies to XMLHttpRequest and to robots.txt (see https://en.wikipedia.org/wiki/Same-origin_policy).