next generation repositories scaling up repositories to a ...€¦ · next generation repositories...

Next Generation RepositoriesScaling up repositories to a global knowledge

commons

Kathleen Shearer, Eloy Rodrigues, Andrea Bollini, Alberto Cabezas, Donatella

Castelli, Les Carr, Leslie Chan, Chuck Humphrey, Rick Johnson, Petr Knoth, Paolo Manghi, Lazarus Matizirofa, Pandelis Perakakis, Jochen Schirrwagen, Tim Smith,

Herbert Van de Sompel, Paul Walk, David Wilcox, Kazu Yamaji

The current scholarly

communication system

is broken!

NotSustainable,

Equitable or

Innovative

COAR’s Vision

A global knowledge commons based on a network of open access repositories

4

But… repository systems are using old technologies developed over 15 years ago that do not support the functionalities we need.

Major strategic priority for COAR

Working Group launched in April 2016

Aim: to identify functionalities and architectures for the next generation repositories within the context of scholarly communication

Next Generation Repositories

6

Next generation repositories working group

The aim of this activity is to develop a global network of repositories

that allows frictionless access to open content and encourages the

creation of cross-repository added-value services.

Current repositories

Services we can

develop with

repositories

today

Persistence layer

Interoperability

Conceptual layer

Interoperability

Metadata

Batc

h

dis

co

very

Current repositories

Services we can

develop with

repositories

today

Persistence layer

Interoperability

Conceptual layer

Interoperability

Metadata

Batc

h

dis

co

very

Interoperability CORE to the

IRs mission. (Crow, 2002 -

SPARC’s position paper on

IRs);(COAR, 2011 - The Case

for Interoperability for Open

Access repositories)

Repositories in crises?

»Richard Poynder’s interview with Clifford Lynch: http://poynder.blogspot.ch/2016/09/q-with-cnis-clifford-lynch-time-to-re_22.html

»Eric van de Velde: “Institutional Repository (IR) is obsolete. Its flawed foundation cannot be repaired. The IR must be phased out and replaced with viable alternatives”: http://scitechsociety.blogspot.ch/2016/07/let-ir-rip.html

»Criticism of lack of interoperability across repositories.

»No comparison with the publishing platforms which are by far less interoperable!

Importance of interoperability

Lack of interoperability in the scholarly communication system is a

major barrier to innovation.

User stories

• Data mining • Discovering metadata that describe a

scholarly resource • Discovering the identifier of a scholarly

resource• Discovering usage rights• Resource syncing and notification

• Recognizing the user • Commenting & annotating• Providing a social notification feed • Recommender systems for repositories • Preservation

• Peer-review• Comparing usage

https://www.coar-

repositories.org/files/COAR-Next-

Generation-Repositories-February-7-

2017.pdf

Current repositories

Services we can

develop with

repositories

today

Persistence layerPersistence layer

Interoperability Interoperability

Metadata

Usage

interactions

and metrics

ContentLinks between

resourcesNotifications

Global sign-on

CommentsPeer-

reviewsMessages

Metadata

Services we can

develop with the next

generation

repositories

Next generation repositories

Conceptual layer

Conceptual layer

Dis

covery

mechanis

ms

-B

atc

h

-N

avig

ation

-N

otification

Batc

h

dis

co

very

Next generation repositories working group

“...making the resource, rather than the repository, the focus of

services and infrastructure.”

Behaviours and Technical Recommendations

https://www.coar-

repositories.org/files/NGR-

Final-Formatted-Report-cc.pdf

• Exposing Identifiers• Discovery Through Navigation• Interacting with Resources (Annotation,

Commentary, and Review)• Resource Transfer• Batch Discovery• Collecting and Exposing Activities• Identification of Users• Authentication of Users• Exposing Standardized Usage Metrics• Declaring Licenses at the Resource Level• Preserving Resources

November 28, 2017

Supporting technologies

• Notification protocols: AMQP,

Kafka, WebSub, Webmention,

Linked Data Notifications, Activity

Streams

• ResourceSync

• Signposting

• ETag

• HTTP Signatures

• IPFS

• ORCID

• OpenID Connect

• Activity Streams 2.0

• SUSHI

• SWORD

•Sitemaps

• Social Network Identities

• Web Annotation Model & Protocol

• WebID

• WebID/TLS

• WebSub

• Webmention

• IIIF

• COUNTER

• Creative Commons Licenses

User stories and priority areas

Discovery

and

exposing

resources

Batch

Navigation

Notification

Research

workflows

and lifecycle

Annotation

Commenting

Social

interaction

Research

evaluation

Peer review

Metrics

• Data mining • Discovering metadata that describe a

scholarly resource • Discovering the identifier of a scholarly

resource• Discovering usage rights• Resource syncing and notification

• Recognizing the user • Commenting & annotating• Providing a social notification feed • Recommender systems for repositories • Preservation

• Peer-review• Comparing usage

User stories and priority areas

Discovery

and

exposing

resources

Batch

Navigation

Notification

Research

workflows

and lifecycle

Annotation

Commenting

Social

interaction

Research

evaluation

Peer review

Metrics

• Data mining • Discovering metadata that describe a

scholarly resource • Discovering the identifier of a scholarly

resource• Discovering usage rights• Resource syncing and notification

• Recognizing the user • Commenting & annotating• Providing a social notification feed • Recommender systems for repositories • Preservation

• Peer-review• Comparing usage

Three vertical discovery mechanisms

»Batch – Transferring bulk data

»Navigation – Helping robots to find resources in repositories by means of navigation

»Notification – Enabling robots to subscribe to changes in repositories

Visualize technologies and behaviour

Priority technologies: Signposting & ResourceSync

Signposting - http://signposting.org/

»Signposting is an approach to make the scholarly web more friendly to machines exposing relations as Typed Links in HTTP Link headers, fully aligned with hypermedia (REST, HATEOAS) lines of thinking regarding web interoperability

»Signposting is now implemented in DSpace-CRIS and OJS. DSpace 7 plans to provide Signposting support

A license link type has been proposed

to drive this information

ResourceSync - http://www.openarchives.org/rs/toc

»Successor of the OAI-PMH protocol and much more…

»Faster, reliable and scalable

»Allows real-time notification (and recovering of missed messages)

»Drives resource synchronization: content and metadata are both managed

ResourceSync – core specification

» Based on the Sitemap protocol…

» essentially some XML files that list your resources (ResourceList)…but also machine «discoverable» from well known URLs…auto explicative in the supported functionalities (CapabilityList) and able to eventually deal with changes (ChangeList) and synchronization of large amount of data (Dumps)

» It is a framework: additional specifications add more features, for example the Change notification allows «push-based» synchronization

ResourceSync Framework Specification (ANSI/NISO Z39.99-2017)

A Next Generation Repository…

» manages and provides access to a wide diversity of resources

» is resource-centric

» is a networked repository

» is machine-friendly

» is active (notify other systems, allow local active interaction)

Types of metadata: descriptive and activity

• Active Repository Pattern• repositories could become pro-active

components in an event-driven scholarly system

• publishing ‘events’ such as the addition of a new item to one or more notification hubs

• third-party systems ‘subscribing’ to these notifications - many potential applications

• would involve very little or no effort by repository administrators

• modest software development http://www.paulwalk.net/2015/10/19/the-active-repository-pattern/

Notification services

Repositories and notification hubs

comments/annotations hubpeer review hubMetadata changes hub

Ongoing work and next steps

1. Implementation of technologies in repository platforms

2. Development of network or hub services

3. Ongoing monitoring of new technologies, standards and protocols

1.Implementation of technologies in repository platforms

• Already progress – several platforms are implementing NGR

recommendations• OpenAIRE – Europe

• National Institute of Informatics (NII) - Japan

• US Next Generation Repositories Implementers Group

• CARL Open Repositories Working Group - Canada

• Meeting of repository platforms here at OR 2018

2. Support the development of network or hub services

• 2 days of meeting of Repository Networks, May 14 & 15, 2018 in

Hamburg, Germany to discuss NGR

functionality and international alignment

• Pilot Projects 2nd half 2018 (Open Peer Review, Common

Standards for Usage Statistics, Recommender Systems)

3. Monitoring of new technologies, standards and protocols

COAR Next Generation Repositories Editorial Group

Andrea Bollini Kathleen Shearer

Rick Johnson Herbert Van de Sompel

Petr Knoth Paul Walk

Paolo Manghi Kazu Yamaji

Eloy Rodrigues

How to contribute?

Support the implementation of the identified behaviours and technologies in your community (DSpace, Eprints, Fedora, Dataverse, Samvera, etc., etc.)

Join the conversation on GitHub

https://github.com/coar-repositories/ngr