Preseted at OR2017 - Brisbane Panel Discussion: COAR Next Generation Repositories: Results and Recommendations The presentation focus on the recommended technologies to implement in Repository platforms The nearly ubiquitous 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. To that end, in April 2016, COAR launched a working group to identify the technologies and architectures of the next generation of repositories. There are two threads to our work: (1) increase the exposure by repositories of uniform behaviors that can be used by machine agents to fuel novel scholarly applications that reach beyond the scope of a single repository and that enable to smoothly embed repository content into mainstream web applications. (2) integrate with existing scholarly infrastructures, specifically those aimed at identification, as a means to solidly embed repositories in the overall scholarly communication landscape. This panel will present the results of the COAR Next Generation Repositories Working Group including our vision, design assumptions, use cases, architectural and technical recommendations, and next steps. The session will also include time for audience discussion and feedback.

1. Andrea Bollini1 & David Wilcox2
1 4Science 2 DuraSpace
Repository
Technologies

2. A new level of interoperability
In the past years we have focused on
interoperability at the Repository level,
now we need interoperability at the
resource level (and below)
Resources need to talk to each other to be
reusable, this in turn will make the
Repositories the base of a global scholarly
ecosystem
2
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

3. IIIF - http://iiif.io/
IIIF International Image Interoperability
Framework is a set of shared APIs to
provide access to image based
resources in a strongly interoperable
way.
It is growing in adoption and scope
covering now also audio/video and 3D
objects.
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

4. IIIF - http://iiif.io/
What Is an Interoperable Resource?
• Discoverable
• Viewable via APIs
• Interactive and Manipulable (for tools, analytics)
• Citable / Shareable
• Mash Up-able
• Annotation-ready
• With attribution, license and links (back to the
image in local context)
Credits: Tom Craimer
International Image Interoperability Framework

5. Why is it relevant in the context of the NGR
work?
It is a concrete example of technology that enables
interoperability at the resource level
You can combine resources hosted in different
repositories at any level of granularity:
- Single images in a set
- Region of a specific image
Other repositories can host additional related
resources like web annotation, comments, etc.
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

6. Le manuscrit 5 de la
Bibliothèque municipale de
Châteauroux, c. 1460
Folio in BVMM
Miniature in the BNF
Credits: Tom Craimer
International Image Interoperability Framework

7. Put the pieces togheter

8. IIIF and Repositories
• Several projects are exploring the use of IIIF
technologies in the repositories software (DSpace,
Fedora, Hydra)
https://wiki.duraspace.org/display/DSPACE/IIIF+and+DSpace
• Don’t miss my presentation:
DSpace for Cultural Heritage: adding support for
images visualization,audio/video streaming and
enhancing the data model
Session: DSpace IG 3: Integrating DSpace
Room: Ballroom C
Session time: 29/Jun/2017, 3:30pm - 5:00pm
8
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

9. Dataset – OpenDATA
• Datasets need to be usable: preview,
sampling, visualization, remote
computation & more
• OpenDATA: standards formats & APIs
required. CKAN provides automatic REST
WS on top of your tabular data. Now
available also to the DSpace users thanks
to the open source DSpace-CKAN
integration by 4Science
9
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

10. 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
The following discovering patterns are currently defined:
• Author
• Bibliographic Metadata
• Identifier
• Publication Boundary
• Resource Type
The Signposting approach is fully aligned with
hypermedia (REST, HATEOAS) lines of thinking
regarding web interoperability. (DSpace7 REST –
Fedora API)
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

11. Signposting -
http://signposting.org/
As an example, Herbert Van de Sompel and
Michael L. Nelson are the authors of the paper
with DOI https://doi.org/10.1045/november2015-
vandesompel; their
respective ORCIDs are http://orcid.org/0000-0002-
0715-6126 and http://orcid.org/0000-0003-3749-
8116
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

12. Signposting -
http://signposting.org/
curl -I "https://doi.org/10.1045/november2015-
vandesompel”
HTTP/1.1 303 See Other
Location:
http://www.dlib.org/dlib/november15/vandesompel/11vande
sompel.html
Link: <http://orcid.org/0000-0002-0715-6126> ;
rel="author",
<http://orcid.org/0000-0003-3749-8116> ;
rel="author"
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

13. Signposting -
http://signposting.org/
• The new versions of DSpace-CRIS 5.7 &
6.1 ship with support for the following
patterns:
– Author
– Identifier
– Publication Boundary
– An issue has been open to track this
requirement also for DSpace 7
https://jira.duraspace.org/browse/DS-3589
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

14. A reflection on the current
repositories data model
• A revision of the current data model is
needed
• Precise identification of persons,
organizations, projects, concepts and
linked resources (dataset, different
versions etc.)
• Avoid loss of details to allow a fine grain
and effective interoperability
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

15. ResourceSync -
http://www.openarchives.org/rs/1.1/resourcesync
• 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
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

16. ResourceSync -
http://www.openarchives.org/rs/1.1/resourcesync
A first implementation of resourcesync for
DSpace was produced in the past years:
https://github.com/CottageLabs/DSpaceRes
ourceSync
a ticket now exists to resume such
implementation and maybe include in the
mainstream:
https://jira.duraspace.org/browse/DS-3590
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

17. ResourceSync -
http://www.openarchives.org/rs/1.1/resourcesync
The Hydra-in-a-box team tested ResourceSync
with the Hyku repository:
http://hydrainabox.samvera.org/2017/06/22/resou
rcesync.html
ResourceSync shows great promise and the
team will continue working toward an
implementation
Andrea Bollini, 4Science / David Wilcox, Duraspace – OR 2017 – Brisbane, Australia

18. Thank for you
attention!
Andrea Bollini
andrea.bollini@4science.it
skype: a.bollini
linkedin: andreabollini
orcid: 0000-0002-9029-
1854
David Wilcox
dwilcox@duraspace.org
twitter: d_wilcox
linkedin: dwilcox1