470 likes | 613 Views
CORE: Aggregating, Enriching and Reusing Open Access. Petr Knoth Knowledge Media institute The Open University. Outline. Aggregating Open Access (OA) publications W hy agregate and who is it for The added value of aggregations The CORE system
E N D
CORE: Aggregating, Enriching and Reusing Open Access Petr Knoth Knowledge Media institute The Open University
Outline Aggregating Open Access (OA) publications Why agregate and who is it for The added value of aggregations The CORE system Supporting research in mining databases of scientific publications (DiggiCORE)
Outline Aggregating Open Access (OA) publications Why agregate and who is it for The added value of aggregations The CORE system Supporting research in mining databases of scientific publications (DiggiCORE)
The rapid rise of OA articles The graph (from Laasko and Bjork's paper - BMC Medicine 2012, 10:124) shows the numbers of papers published in three different types of online open access journals from 2000 to 2011.
Why we need aggregations? “Each individual repository is of limited value for research: the real power of Open Access lies in the possibility of connecting and tying together repositories, which is why we need interoperability. In order to create a seamless layer of content through connected repositories from around the world, Open Access relies on interoperability, the ability for systems to communicate with each other and pass information back and forth in a usable format. Interoperability allows us to exploit today's computational power so that we can aggregate, data mine, create new tools and services, and generate new knowledge from repository content.’’ [COAR manifesto]
Access to information according to the level of abstraction Analytical information access Repository Repository Repository Interfaces OLTP OLAP Aggregation Transaction information access Semantic Enrichment Metadata Content Metadata Transfer Interoperability Raw data access
Who should be supported by aggregations? The following users groups (divided according to the level of abstraction of information they need): Raw data access. Transaction information access. Analytical information access.
Who should be supported by aggregations? The following users groups (divided according to the level of abstraction of information they need): Raw data access. Developers, DLs, DL researchers, companies … Transaction information access. Researchers, students, life-long learners … Analytical information access. Funders, government, bussiness intelligence …
BASE Interfaces Analytical information access Repository Repository Repository OLTP OLAP Enrichment Aggregation Transaction information access Metadata Content Metadata Transfer Interoperability Raw data access
OCLC WorldCAT Interfaces Analytical information access Repository Repository Repository OLTP OLAP Enrichment Aggregation Transaction information access Metadata Content Metadata Transfer Interoperability Raw data access
RepUK Interfaces Analytical information access Repository Repository Repository OLTP OLAP Enrichment Aggregation Transaction information access Metadata Content Metadata Transfer Interoperability Raw data access
Aggregations need access to content, not just metadata! Certain metadata types can be created only at the level of the aggregation Certain metadata can be changing in time Ensuring content: accessibility availability validity quality …
CiteSeerX (computer science) Interfaces Analytical information access Repository Repository Repository OLTP OLAP Enrichment Aggregation Transaction information access Metadata Content Metadata Transfer Interoperability Raw data access
Should an aggregation system support all three access levels? Can be realised by more than one system providing that the dataset is the same!
The problem of result transparency Google Scholar Microsoft Academic Search
Outline Aggregating Open Access (OA) publications – why, how, what for? The CORE system Supporting research in mining databases of scientific publications (DiggiCORE)
CORE objective CORE aims to provide a comprehensive technical infrastructure for Open Access scholarly publications that will support access and reuse of scholarly materials at different levels of abstraction.
CORE functionality Content harvesting, processing
CORE functionality Semantic enrichment
CORE functionality Providing services
What does CORE provide at different access levels? Repository Analytics Interfaces Analytical information access Repository Repository Repository OLTP OLAP CORE Portal, CORE Mobile, CORE Plugin Enrichment Aggregation Transaction information access Metadata Content Metadata Transfer Interoperability CORE API CORE API Raw data access
CORE Applications CORE Portal – Allows searching and navigating scientific publications aggregated from Open Access repositories
CORE Applications CORE Mobile – Allows searching and navigating scientific publications aggregated from Open Access repositories
CORE Plugin – A plugin to system that recommendations for related items. CORE Applications
CORE Applications Repository Analytics – is an analytical tool supporting providers of open access content (in particular repository managers).
CORE Applications CORE API – Enables external systems and services to interact with the CORE repository. Search service Pdf and plain text service Similarity service Classification service Citation service
CORE Applications CORE API registered users: British Education Index Cottagelabs UKCORR Europeana ULCC Library, The Open University Los Alamos National Laboratory, USA University of Manchester Library Universidad de los Andes. Bogotá, Colombia UNESCO
Outline Aggregating Open Access (OA) publications – why, how, what for? The CORE system Supporting research in mining databases of scientific publications ( )
Partners Advisory Board
Objective Software for exploration and analysis of very large and fast-growing amounts of research publications stored across Open Access Repositories (OAR).
DiggiCORE networks Three networks: (a) semantically related papers, (b) citation network, (c) author citation network
DiggiCORE objectives Allow researchers to use this platform to analyse publications. Why? To identifying patterns in the behaviour of research communities To detect trends in research disciplines To gain new insights into the citation behaviour of researchers To discover features that distinguish papers with high impact
Questions the system can help answering? What are the attributes of impact publications? Do these attributes differ in the humanities, social sciences and computer sciences? What are the features of research groups within disciplines and how do these features relate to contributions generated by the group? What are the attributes of high-impact authors and what is their role within the group? What are the dynamics of successful research groups?
Questions the system can help answering? What is the mechanism of cross-fertilisation within disciplines, especially between the humanities and the sciences? Who are the authors whose work is worth monitoring because they contribute to the achievements of their own discipline and also inspire other disciplines? How should the novice in the discipline get acquainted with key achievements in the discipline? How should he/she search for the most important publications?
Summary Aggregations should serve the needs of different user groups. We need to aggregate content, not just metadata. Machine access to publications provides lots of new opportunities. We can have many services that are part of the infrastructure, but should work with the same data. CORE (and DiggiCORE) aims to prepare the way for innovative open access services demonstrate the benefits of programmable access to publications
Acknowledgement This work has been partly funded by JISC and AHRC. Contributors to the CORE software: Vojtech Robotka, Magdalena Krygielova, Drahomira Herrmannova, Tomas Korec, Jakub Novotny, Ian Tindle, Harriett Cornish, Gabriela Pavel, Markus Muhr, Loukas Anastasiou, Colin Smith, Chris Yates Participants of CORE Advisory Boards and other CORE related meetings Owen Stephens, Bill Hubbard, Andy McGregor, Stuart Dempster, Andreas Juffinger, Markus Muhr, Jan Molendijk, Paul Walk, Chris Yates, Chris Biggs, Non Scantlebury