CORE: Aggregating and Enriching Content to Support Open Access

Preview:

DESCRIPTION

The last 10 years have seen a massive increase in the amounts of Open Access publications available in journals and institutional repositories. The existence of large volumes of free state-of-the-art knowledge online has the potential to provide huge savings and benefits in many fields. However, in order to fully leverage this knowledge, it is necessary to develop systems that (a) make it easy for users to access, discover and explore this knowledge, (b) that lower the barriers to the development of systems and services building on top of this knowledge and (c) that enable to freely analyse how this knowledge is organised and used. In this paper, we argue why these requirements should be fulfilled and show that current systems do not satisfy them. We also present CORE, a large-scale Open Access aggregation system, outline its functionality and architecture and demonstrate how it addresses the above mentioned needs and how it can be applied to benefit the whole ecosystem including institutional repositories, researchers, general public and government.

Citation preview

1/52

CORE: Aggregating and Enriching Content to Support Open Access

Petr KnothThe Open University

2/52

Outline

1. Aggregating Open Access (OA) publications – why, how, what for?

2. The CORE system3. Supporting research in mining databases of scientific

publications (DiggiCORE)

3/52

Outline

1. Aggregating Open Access (OA) publications – why, how, what for?

2. The CORE system3. Supporting research in mining databases of scientific

publications (DiggiCORE)

4/52

Growth of items in Open Access repositories

5/52

Growth of Open Access repositories

6/52

Growth of articles in OA journals

7/52

Growth of OA journals

8/52

Green Open Access - statistics

9/52

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]

10/52

Access to information according to the level of abstraction

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Semantic Enrichm

ent

Interfaces

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information access

Aggregation

11/52

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.

12/52

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

13/52

Layers of an aggregation system

Metadata Transfer Interoperability

OLTP OLAP

Metadata Content

Enrichment

Interfaces

14/52

Layers of an aggregation system

Metadata Transfer Interoperability

OLTP OLAP

Metadata Content

Enrichment

Interfaces

OAI-PMH, OAI-ORE … Dublin Core, XML, RDF … PDF, Word …

Annotations

Catalog records

StatisticsAPIs (REST, SOAP, XML-RPC), UIs, Dashboards

15/52

Access to information according to the level of abstraction

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

16/52

Related systems

17/52

Aggregation projects – BASE

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

18/52

Aggregation projects – OAISter/WorldCAT

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

19/52

Aggregation projects – RepUK

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

20/52

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• …

21/52

Aggregation projects – CiteSeerX

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

22/52

Should an aggregation system support all three user types?

Can be realised by more than one systemproviding that

the dataset is the same!

23/52

Outline

1. Aggregating Open Access (OA) publications – why, how, what for?

2. The CORE system3. Supporting research in mining databases of scientific

publications (DiggiCORE)

24/52

CORE objectives

• 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.

• A nation-wide aggregation system that will improve the discovery of publications stored in British Open Access Repositories (OARs).

25/52

What does CORE provide at different aggregation levels?

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

26/52

CORE functionality

27/52

CORE functionality

Step 1: Metadata and full-text harvesting

Content harvesting, processing

28/52

What does CORE provide at different aggregation levels?

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

Semantic similarity, Citation extraction, classsification, …

29/52

CORE functionality

Step 2: Semantic enrichment

Semantic enrichment

30/52

What does CORE provide at different aggregation levels?

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

31/52

CORE functionality

Step 3: Providing a set of services on top of the aggregation

Providing services

32/52

CORE applications

• CORE Portal• CORE Mobile• CORE Plugin• CORE API• Repository Analytics

33/52

What does CORE provide at different aggregation levels?

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

34/52

CORE ApplicationsCORE Portal – Allows searching and navigating scientific publications aggregated from Open Access repositories

35/52

CORE Applications

CORE Mobile – Allows searching and navigating scientific publications aggregated from Open Access repositories

36/52

CORE ApplicationsCORE Plugin – A plugin to system that recommendations for related items.

37/52

What does CORE provide at different aggregation levels?

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

38/52

CORE ApplicationsCORE API – Enables external systems and services to interact with the CORE repository.

39/52

What does CORE provide at different aggregation levels?

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

40/52

CORE ApplicationsRepository Analytics – is an analytical tool supporting providers of open access content (in particular repository managers).

41/52

What does CORE provide at different aggregation levels?

Repository

Repository

RepositoryRaw data access

Transaction information access

Analytical information accessInterfaces

Metadata Transfer

Interoperability

OLTP

OLAP

Metadata

Content

Enrichment

Repository Analytics

CORE API

CORE Portal, CORE Mobile, CORE Plugin

42/52

CORE statistics

• Content• 5.4M records• 192 repositories• 402k full-texts

• Started: February 2011• Budget: 140k£

43/52

Outline

1. Aggregating Open Access (OA) publications – why, how, what for?

2. The CORE system3. Supporting research in mining databases of scientific

publications ( )

44/52

Partners

Advisory Board

45/52

Objective

Software for exploration and analysis of very large and fast-growing amounts of research publications stored across Open Access Repositories (OAR).

46/52

DiggiCORE networks

Three networks: (a) semantically related papers,(b) citation network, (c) author citation network

47/52

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

48/52

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?

49/52

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?

50/52

Summary

• The rapid growth of OA content provides both an opportunity as well as a challenge.

• Aggregations should serve the needs of different user groups. • Aggregations need to aggregate content, not just metadata. • We can have many services that are part of the infrastructure,

but should work with the same data.

51/52

Thank you!

Yes we can!

52/52

Recommended