# Next generation repositories

## Rationale

The widespread deployment of repository systems in higher education and research institutions provides the foundation for a distributed, globally networked infrastructure for scholarly communication. However, repository platforms are still using technologies and protocols designed almost twenty years ago, before the boom of the Web and the dominance of Google, social networking, semantic web and ubiquitous mobile devices. This is, in large part, why repositories have not fully realized their potential and function mainly as passive recipients of the final versions of their users’ conventionally published research outputs. In order to leverage the value of the repository network, we need to equip it with a wider array of roles and functionalities, which can be enabled through new levels of web-centric interoperability.

![image by Petr Knoth](/files/-LKWqxaakumtgIiUwySA)

Eloy Rodrigues presents "Introduction to Next Generation Repositories" at at COAR 2017 Annual Meeting, Italy. [Slides of the talk](http://doi.org/10.5281/zenodo.579976) are available on Zenodo. 

{% embed url="<https://youtu.be/Fo-YsbT-Iy4>" %}

Paul Walk presents "What Does the Next Generation Repository Look Like" at COAR 2017 Annual Meeting, Italy. [Slides of the talk](http://doi.org/10.5281/zenodo.579982) are available on Zenodo.&#x20;

{% embed url="<https://youtu.be/U9QsGyeJmmo>" %}

Andrea Bollini presents "Next Generation Repositories" at COAR 2018 Annual Meeting, Germany. [Slides of the talk](http://doi.org/10.5281/zenodo.1250154) are available on Zenodo.&#x20;

{% embed url="<https://youtu.be/pY5q0JWgzn4>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://coartraining.gitbook.io/coar-repository-toolkit/nextgen-repositories.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.