2010
Journal article
Open Access
Not just another portal, not just another digital library: a portrait of Europeana as an application program interface
Concordia C, Gradmann S, Siebinga S
To the general public, Europeana is primarily perceived as a portal exposing a great amount of cultural heritage information. Even though this perception is not entirely misleading, the main goal of Europeana rather is to build an open services platform enabling users and cultural institutions to access and manage a large collection of surrogate objects representing digital and digitized content via an Application Program Interface (API) The paper covers some details of the overall data space schema, of the API description and of the Europeana Portal implementation; it also discusses use cases and the mental approach that users, in particular cultural institutions, should adopt to completely exploit the potential of the Europeana services platform together with a discussion of related risks. The authors represent key players in the Europeana specification, development and implementation process currently under way.Source: IFLA JOURNAL, vol. 36, pp. 61-69
DOI: 10.1177/0340035209360764
Metrics:
Concordia C, Gradmann S, Siebinga S
To the general public, Europeana is primarily perceived as a portal exposing a great amount of cultural heritage information. Even though this perception is not entirely misleading, the main goal of Europeana rather is to build an open services platform enabling users and cultural institutions to access and manage a large collection of surrogate objects representing digital and digitized content via an Application Program Interface (API) The paper covers some details of the overall data space schema, of the API description and of the Europeana Portal implementation; it also discusses use cases and the mental approach that users, in particular cultural institutions, should adopt to completely exploit the potential of the Europeana services platform together with a discussion of related risks. The authors represent key players in the Europeana specification, development and implementation process currently under way.Source: IFLA JOURNAL, vol. 36, pp. 61-69
DOI: 10.1177/0340035209360764
Metrics:
See at:
IFLA Journal 
| Lirias | IFLA Journal 
| CNR IRIS | CNR IRIS | www.ifla.org
2009
Conference article
Restricted
Not (just) a repository, nor (just) a digital library, nor (just) a portal: a portrait of Europeana as an API
Concordia C, Gradmann S, Siebinga S
In the wide public Europeana is primarily perceived as a portal exposing a great amount of cultural heritage information. Even though this perception is not entirely misleading, the main goal of Europeana rather is to build an open services platform enabling users and cultural institutions to access and manage a large collection of surrogate objects representing digital and digitised content via an Application Program Interface (API). The paper covers some details of the overall data space schema, of the API description and of the Europeana Portal implementation; it also discusses use cases and the mental approach that users, in particular cultural institutions, should adopt to completely exploit the potential of the Europeana services platform together with a discussion of related risks.Source: IFLA PUBLICATIONS, pp. 1-13. Milan, Italy, 23-27 August 2009
Concordia C, Gradmann S, Siebinga S
In the wide public Europeana is primarily perceived as a portal exposing a great amount of cultural heritage information. Even though this perception is not entirely misleading, the main goal of Europeana rather is to build an open services platform enabling users and cultural institutions to access and manage a large collection of surrogate objects representing digital and digitised content via an Application Program Interface (API). The paper covers some details of the overall data space schema, of the API description and of the Europeana Portal implementation; it also discusses use cases and the mental approach that users, in particular cultural institutions, should adopt to completely exploit the potential of the Europeana services platform together with a discussion of related risks.Source: IFLA PUBLICATIONS, pp. 1-13. Milan, Italy, 23-27 August 2009
See at:
CNR IRIS | CNR IRIS | www.ifla.org
2009
Other
Open Access
Integration of heterogeneous metadata in Europeana
Concordia C
Issues and challenges in building the data space for the first Europeana prototype.
Concordia C
Issues and challenges in building the data space for the first Europeana prototype.
See at:
CNR IRIS | ISTI Repository | www.dublincore.org | CNR IRIS
2017
Other
Restricted
VRE4EIC Deliverable 5.2 Implications for the VRE end-users to handle security, privacy and trust issues - first version
Hollink L, Concordia C, Ashley K, Whyte A
For the e-VRE being developed by the VRE4EIC project, the security, privacy and trust requirements significantly vary amongst the potential end-users from various research domains and public. In deliverable D5.1, the VRE4EIC project has defined the strategies handling potential issues and risks regarding security, privacy and trust aspects. However, these strategies are mainly produced to help the technical developers better design the e-VRE and choose appropriate technologies for the implementation of the e-VRE. We assume that most of the potential end-users will have limited ICT knowledge so that they may have a different understanding or interpretation regarding these strategies to deal with security, privacy and trust related issues. In order to help our potential end- users understand the logic and consideration of the strategies developed in D5.1, this deliverable clarifies these strategies in the early stage of e-VRE development. The user is a global actor representing any user accessing the e-VRE (according to its definition, "VRE users" only concern people that want to access research data). This approach will also help the engagement of potential end-users. After implementing an e-VRE prototype that will be tested by user groups, a second version of this deliverable will be completed in Month 33 (D5.4). Upon acceptance of this strategy document, it will be made publicly available and especially distributed to target users of the existing e-RI initiatives and VRE-related initiatives.Project(s): VRE4EIC
Hollink L, Concordia C, Ashley K, Whyte A
For the e-VRE being developed by the VRE4EIC project, the security, privacy and trust requirements significantly vary amongst the potential end-users from various research domains and public. In deliverable D5.1, the VRE4EIC project has defined the strategies handling potential issues and risks regarding security, privacy and trust aspects. However, these strategies are mainly produced to help the technical developers better design the e-VRE and choose appropriate technologies for the implementation of the e-VRE. We assume that most of the potential end-users will have limited ICT knowledge so that they may have a different understanding or interpretation regarding these strategies to deal with security, privacy and trust related issues. In order to help our potential end- users understand the logic and consideration of the strategies developed in D5.1, this deliverable clarifies these strategies in the early stage of e-VRE development. The user is a global actor representing any user accessing the e-VRE (according to its definition, "VRE users" only concern people that want to access research data). This approach will also help the engagement of potential end-users. After implementing an e-VRE prototype that will be tested by user groups, a second version of this deliverable will be completed in Month 33 (D5.4). Upon acceptance of this strategy document, it will be made publicly available and especially distributed to target users of the existing e-RI initiatives and VRE-related initiatives.Project(s): VRE4EIC
See at:
CNR IRIS | CNR IRIS | www.vre4eic.eu
2016
Other
Open Access
Europeana Cloud - Deliverable 4.3 - A report and a plan on future directions for improving metadata in the Europeana Cloud
Lefferts M Ed, Concordia C, Anastasiou L, Jahnke A, Kittelmann M, Manguinhas H
The aim of the task reported in this Deliverable 4.3 was to explore how we could arrive at shared metadata enrichment, by making the most of the large amount of data already gathered in Europeana and the Cloud environment developed in the project. We explored whether we could enrich the data by comparing Europeana data with data from external sources (task 4.3.1). Secondly, we explored whether there was data internally in the large Europeana set that could meaningfully be connected to other data in the set (task 4.3.2). Both approaches would offer better contextualisation of Europeana data for the end user. In Task 4.3.1, ISTICNR demonstrated the use of image recognition techniques to explore possible overlap between the datasets of Europeana and the WikiArt data set. As a side effect, it showed that duplicates within the Europeana data set might also surface. The pilot showed how information from an external resource such as WikiArt can potentially be used to enrich the data that is already held in Europeana. A second test phase in February 2016 will increase the Europeana and WikiArt datasets, ensure a more precise selection and focus on paintings held in Europeana, improve matching against WikiArt, and enhance performance.Project(s): Access to cultural heritage networks for Europeana, Europeana Cloud: Unlocking Europe's Research via The Cloud
Lefferts M Ed, Concordia C, Anastasiou L, Jahnke A, Kittelmann M, Manguinhas H
The aim of the task reported in this Deliverable 4.3 was to explore how we could arrive at shared metadata enrichment, by making the most of the large amount of data already gathered in Europeana and the Cloud environment developed in the project. We explored whether we could enrich the data by comparing Europeana data with data from external sources (task 4.3.1). Secondly, we explored whether there was data internally in the large Europeana set that could meaningfully be connected to other data in the set (task 4.3.2). Both approaches would offer better contextualisation of Europeana data for the end user. In Task 4.3.1, ISTICNR demonstrated the use of image recognition techniques to explore possible overlap between the datasets of Europeana and the WikiArt data set. As a side effect, it showed that duplicates within the Europeana data set might also surface. The pilot showed how information from an external resource such as WikiArt can potentially be used to enrich the data that is already held in Europeana. A second test phase in February 2016 will increase the Europeana and WikiArt datasets, ensure a more precise selection and focus on paintings held in Europeana, improve matching against WikiArt, and enhance performance.Project(s): Access to cultural heritage networks for Europeana, Europeana Cloud: Unlocking Europe's Research via The Cloud
See at:
CNR IRIS | ISTI Repository | pro.europeana.eu | CNR IRIS
2019
Other
Open Access
SSHOC - D3.2 Inventory of SSH citation practices, and choice for SSHOC citation formats and implementation planning
Larrousse N, Broeder D, Brase J, Concordia C, Kalaitzi V
The SSHOC project aims to build the SSH (Social Science and Humanities) part of the EOSC (European Open Science Cloud). One of the main goals of the project is to ensure that SSH will be present in EOSC and that their specifics are taken into account. In this regard, an important point is to be able to give high visibility to the research data used in Social Science and Humanities following FAIR data principles. This can be achieved by fostering "Data Citation" through providing a common mechanism to cite SSH data and build stronger links between data and publications. An expected side effect would be to enhance the reproducibility of SSH research, which is not very common nowadays. In line with these goals, this report delivers an overview of existing data-citing mechanisms intended for citing data, that are currently used in different communities with a focus on the SSH. It then provides some guidelines describing what is relevant in the SSHOC context with respect to the technology to be implemented and also about the structuring of the content.Project(s): SSHOC
Larrousse N, Broeder D, Brase J, Concordia C, Kalaitzi V
The SSHOC project aims to build the SSH (Social Science and Humanities) part of the EOSC (European Open Science Cloud). One of the main goals of the project is to ensure that SSH will be present in EOSC and that their specifics are taken into account. In this regard, an important point is to be able to give high visibility to the research data used in Social Science and Humanities following FAIR data principles. This can be achieved by fostering "Data Citation" through providing a common mechanism to cite SSH data and build stronger links between data and publications. An expected side effect would be to enhance the reproducibility of SSH research, which is not very common nowadays. In line with these goals, this report delivers an overview of existing data-citing mechanisms intended for citing data, that are currently used in different communities with a focus on the SSH. It then provides some guidelines describing what is relevant in the SSHOC context with respect to the technology to be implemented and also about the structuring of the content.Project(s): SSHOC
See at:
CNR IRIS | ISTI Repository | zenodo.org | CNR IRIS
2022
Other
Open Access
SSHOC - D5.5 'Archive in a Box' repository software and proof of concept of centralised installation in the cloud
Wittenberg M, Tykhonov V, Indarto E, Steinhoff W, Huis In 't Veld L, Kasberger S, Conzett P, Concordia C, Kiraly P, Parkola T
Within task 5.2 (Hosting and sharing data repositories) of the SSHOC project, repository software is being developed based on Dataverse, for the sharing and publication of research data within the Social Science and Humanities (SSH) domain. Dataverse is open-source research data repository software developed by the Institute for Quantitative Social Science (IQSS), Harvard University. This document describes the work done by task 5.2, for the development of 'Archive in a Box' repository software and proof of concept of centralised installation in the cloud. The 'Archive in a Box' makes the installation of Dataverse repository software easier for institutes with a lack of technical staff. This document describes the advantages of such a package. Additionally, task 5.2 worked on a proof of concept of a centralised cloud installation of the Dataverse software at the Google cloud infrastructure of CESSDA ERIC. A cloud installation makes it possible to automate the installation and keep the application up and running, for instance by scaling up or down resources when needed. Another advantage of a cloud orchestrator is the ability to start a new component or part of the application, if it should fail for some reason. Furthermore, task 5.2 developed several additional functionalities to the Dataverse software to make the software more compliant to the needs of the SSH communities in Europe. This document describes the results of the accomplished work, and refers to technical details published in GitHub repositories. Already many of the results of task 5.2 are used by the European and Global Dataverse community and some functionalities are integrated in the new versions of the Dataverse master branch of Harvard.DOI: 10.5281/zenodo.6676391
Project(s): SSHOC
Metrics:
Wittenberg M, Tykhonov V, Indarto E, Steinhoff W, Huis In 't Veld L, Kasberger S, Conzett P, Concordia C, Kiraly P, Parkola T
Within task 5.2 (Hosting and sharing data repositories) of the SSHOC project, repository software is being developed based on Dataverse, for the sharing and publication of research data within the Social Science and Humanities (SSH) domain. Dataverse is open-source research data repository software developed by the Institute for Quantitative Social Science (IQSS), Harvard University. This document describes the work done by task 5.2, for the development of 'Archive in a Box' repository software and proof of concept of centralised installation in the cloud. The 'Archive in a Box' makes the installation of Dataverse repository software easier for institutes with a lack of technical staff. This document describes the advantages of such a package. Additionally, task 5.2 worked on a proof of concept of a centralised cloud installation of the Dataverse software at the Google cloud infrastructure of CESSDA ERIC. A cloud installation makes it possible to automate the installation and keep the application up and running, for instance by scaling up or down resources when needed. Another advantage of a cloud orchestrator is the ability to start a new component or part of the application, if it should fail for some reason. Furthermore, task 5.2 developed several additional functionalities to the Dataverse software to make the software more compliant to the needs of the SSH communities in Europe. This document describes the results of the accomplished work, and refers to technical details published in GitHub repositories. Already many of the results of task 5.2 are used by the European and Global Dataverse community and some functionalities are integrated in the new versions of the Dataverse master branch of Harvard.DOI: 10.5281/zenodo.6676391
Project(s): SSHOC
Metrics:
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2021
Other
Open Access
SSHOC - D3.5 Report on citation enabled SSH catalogues and SSH citation exploitation
Larrousse N, Gray E, Broeder D, Concordia C, Brase J, Papadopoulou A
Citation is a pillar for the construction of knowledge. By creating proper citations in a standardized way researchers can constitute a mesh of linked information for various purposes (from credit to reuse). This becomes increasingly important as the SSHOC Task 3.4 team confronts the realities of Social Sciences and Humanities Research in a digital age, when machine actionability takes on a renewed and vital importance. After conducting an inventory of data citation practices (SSHOC D3.2 "Inventory of SSH citation practices, and choice for SSHOC citation formats and implementation planning") and analysing the citation of data in DH1 2019 conference abstracts in order to build specifications for the citation prototype, the team discovered a very diverse landscape of data repositories. As a result, the team developed recommendations for citation in coordination with SSHOC Work Package 2 (Communication, Dissemination, and Impact), validated by external reviewers. These recommendations were used to guide a deeper analysis of citation practices in various SSH repositories and how they correspond to these recommendations in order to have a better idea of the current situation. This analysis was carried out in both a quantitative and qualitative fashion. For the qualitative part, the main goal was to describe, in detail, a selection of repositories representative of the SSH domain. The choice of repositories was made in collaboration with the SSHOC network in order to have a good representation of the very diverse contexts in SSH. This qualitative analysis focused on how these repositories were constructed to provide data citation services in detail. For the quantitative part, a list of repositories was already established by SSHOC Task 8.2 "Trust & Quality Assurance" and the team took this opportunity to establish synergies and extract a list of repositories to be checked according to defined criteria regarding data citation. The analysis checked 85 repositories from a list of 125 against a set of 7 criteria. In order to facilitate the work, the team used the citation viewer which is part of the prototype mentioned above. The main result of this quick study is that while there are positive signs, especially with respect to the use of landing pages and Persistent Identifiers (PIDs), there is quite a bit of room for improvement as a lot of repositories do not provide machine actionable information. This makes the prototype the Task 3.4 team is currently developing to create actionable citations all the more useful. It also appears from this work that it will be necessary to manually curate some citations in order to enrich them and make them actionable as the information is not always directly available (e.g., a landing page provides a link to a page which contains metadata expressed in another format). The result of this study will feed the development of the citation prototype developed in Task 3.4 and also liaise with SSHOC WP7 "Creating the SSH Open Marketplace" to integrate citations in SSH Open Marketplace2 with a "Cite As" property in the backend and Cite As box in the frontend interface. Another link exists with the very similar work currently being carried out in CLARIN for the Digital Object Gateway.DOI: 10.5281/zenodo.5603306
DOI: 10.5281/zenodo.5603305
Project(s): SSHOC
Metrics:
Larrousse N, Gray E, Broeder D, Concordia C, Brase J, Papadopoulou A
Citation is a pillar for the construction of knowledge. By creating proper citations in a standardized way researchers can constitute a mesh of linked information for various purposes (from credit to reuse). This becomes increasingly important as the SSHOC Task 3.4 team confronts the realities of Social Sciences and Humanities Research in a digital age, when machine actionability takes on a renewed and vital importance. After conducting an inventory of data citation practices (SSHOC D3.2 "Inventory of SSH citation practices, and choice for SSHOC citation formats and implementation planning") and analysing the citation of data in DH1 2019 conference abstracts in order to build specifications for the citation prototype, the team discovered a very diverse landscape of data repositories. As a result, the team developed recommendations for citation in coordination with SSHOC Work Package 2 (Communication, Dissemination, and Impact), validated by external reviewers. These recommendations were used to guide a deeper analysis of citation practices in various SSH repositories and how they correspond to these recommendations in order to have a better idea of the current situation. This analysis was carried out in both a quantitative and qualitative fashion. For the qualitative part, the main goal was to describe, in detail, a selection of repositories representative of the SSH domain. The choice of repositories was made in collaboration with the SSHOC network in order to have a good representation of the very diverse contexts in SSH. This qualitative analysis focused on how these repositories were constructed to provide data citation services in detail. For the quantitative part, a list of repositories was already established by SSHOC Task 8.2 "Trust & Quality Assurance" and the team took this opportunity to establish synergies and extract a list of repositories to be checked according to defined criteria regarding data citation. The analysis checked 85 repositories from a list of 125 against a set of 7 criteria. In order to facilitate the work, the team used the citation viewer which is part of the prototype mentioned above. The main result of this quick study is that while there are positive signs, especially with respect to the use of landing pages and Persistent Identifiers (PIDs), there is quite a bit of room for improvement as a lot of repositories do not provide machine actionable information. This makes the prototype the Task 3.4 team is currently developing to create actionable citations all the more useful. It also appears from this work that it will be necessary to manually curate some citations in order to enrich them and make them actionable as the information is not always directly available (e.g., a landing page provides a link to a page which contains metadata expressed in another format). The result of this study will feed the development of the citation prototype developed in Task 3.4 and also liaise with SSHOC WP7 "Creating the SSH Open Marketplace" to integrate citations in SSH Open Marketplace2 with a "Cite As" property in the backend and Cite As box in the frontend interface. Another link exists with the very similar work currently being carried out in CLARIN for the Digital Object Gateway.DOI: 10.5281/zenodo.5603306
DOI: 10.5281/zenodo.5603305
Project(s): SSHOC
Metrics:
See at:
ZENODO | ZENODO | CNR IRIS | ISTI Repository | CNR IRIS
2021
Other
Open Access
Dataverse: switchboard plugin
Concordia C
Overall description of the 'dataverse-lrs' plugin, a plugin enabling the integration of Dataverse repositories with the CLARIN Language Resource Switchboard (LRS) software, developed in the "Social Sciences and Humanities Open Cloud (SSHOC)" project. The software is available in the SSHOC GitHub repository: https://github.com/SSHOC/dataverse-lrsProject(s): SSHOC
Concordia C
Overall description of the 'dataverse-lrs' plugin, a plugin enabling the integration of Dataverse repositories with the CLARIN Language Resource Switchboard (LRS) software, developed in the "Social Sciences and Humanities Open Cloud (SSHOC)" project. The software is available in the SSHOC GitHub repository: https://github.com/SSHOC/dataverse-lrsProject(s): SSHOC
See at:
CNR IRIS | ISTI Repository | www.clarin.eu | CNR IRIS
2021
Software
Open Access
Dataverse-LRS: integrating Dataverse with the CLARIN Language Resource Switchboard
Concordia C
The "dataverse-lrs" software is a plugin that can be installed in a Dataverse repository to enable the integration in the Dataverse GUI of the CLARIN Language Resource Switchboard (LRS). A Dataverse repository is implemented using an open-source software platform, developed and maintained by the Harvard Institute for Quantitative Social Science (IQSS) (https://dataverse.harvard.edu/), the CLARIN LRS (https://switchboard.clarin.eu) can be seen as a Virtual Tool Registry: for a given resource, it identifies all tools that can process the resource, sorts the tools in terms of the tasks they perform, and presents a task-oriented list of those tools, each tool of the list can be invoked and the resource is automatically processed. The 'dataverse-lrs' software has been developed in the Social Sciences & Humanities Open Cloud (SSHOC) project and is described in the deliverable "3.8 Implementation report and available SSHOC Switchboard and VCR services". The software has been also presented during the CLARIN Centre Meeting 2021 (https://www.clarin.eu/event/2021/centre-meeting-2021).Project(s): SSHOC
Concordia C
The "dataverse-lrs" software is a plugin that can be installed in a Dataverse repository to enable the integration in the Dataverse GUI of the CLARIN Language Resource Switchboard (LRS). A Dataverse repository is implemented using an open-source software platform, developed and maintained by the Harvard Institute for Quantitative Social Science (IQSS) (https://dataverse.harvard.edu/), the CLARIN LRS (https://switchboard.clarin.eu) can be seen as a Virtual Tool Registry: for a given resource, it identifies all tools that can process the resource, sorts the tools in terms of the tasks they perform, and presents a task-oriented list of those tools, each tool of the list can be invoked and the resource is automatically processed. The 'dataverse-lrs' software has been developed in the Social Sciences & Humanities Open Cloud (SSHOC) project and is described in the deliverable "3.8 Implementation report and available SSHOC Switchboard and VCR services". The software has been also presented during the CLARIN Centre Meeting 2021 (https://www.clarin.eu/event/2021/centre-meeting-2021).Project(s): SSHOC
See at:
github.com | CNR IRIS | ISTI Repository | CNR IRIS
2021
Other
Open Access
SSHOC - D7.4 Marketplace - Data population & curation
Gray E, Larrousse N, Petitfils C, Barbot L, Fischer F, Durco M, Illmayer K, Concordia C, Konig A, Van Uytvanck D, Buddenbohm S
The SSH Open Marketplace is a discovery portal for digital tools, services, and methods in the Social Sciences and Humanities (SSH), with an emphasis placed on placing these resources in their research context. It is the SSH component of the EOSC Marketplace. Previous initiatives have shown that curation of content is the key element to maintain the attractiveness and the utility of a discovery portal like the SSH Open Marketplace.1 Thus at each stage of the development of the Marketplace, from the first ingestion of existing catalogues to the curation sprint, curation has been at the heart of conception. This emphasis, based on previous examples and the work done throughout the SSHOC project, has led to profound changes in the data model, definition of quality criteria, standardization of the content as the team adapts the machinery of the Marketplace based on lessons learned. This continuous work has laid the foundation of the development of Editorial Guidelines which will be used by future curation actors as well as the definition of their different curation roles and the organisation of their relationship.DOI: 10.5281/zenodo.5783358
Project(s): SSHOC
Metrics:
Gray E, Larrousse N, Petitfils C, Barbot L, Fischer F, Durco M, Illmayer K, Concordia C, Konig A, Van Uytvanck D, Buddenbohm S
The SSH Open Marketplace is a discovery portal for digital tools, services, and methods in the Social Sciences and Humanities (SSH), with an emphasis placed on placing these resources in their research context. It is the SSH component of the EOSC Marketplace. Previous initiatives have shown that curation of content is the key element to maintain the attractiveness and the utility of a discovery portal like the SSH Open Marketplace.1 Thus at each stage of the development of the Marketplace, from the first ingestion of existing catalogues to the curation sprint, curation has been at the heart of conception. This emphasis, based on previous examples and the work done throughout the SSHOC project, has led to profound changes in the data model, definition of quality criteria, standardization of the content as the team adapts the machinery of the Marketplace based on lessons learned. This continuous work has laid the foundation of the development of Editorial Guidelines which will be used by future curation actors as well as the definition of their different curation roles and the organisation of their relationship.DOI: 10.5281/zenodo.5783358
Project(s): SSHOC
Metrics:
See at:
ZENODO | CNR IRIS | ISTI Repository | CNR IRIS
2022
Other
Open Access
Diary of our initiatory journey on the continent of data citation in SSH
Larrousse N, Gray Ej, Concordia C
If citation is a common practice for publications, it is relatively new for data especially in SSH. This paper will present the work carried out during the SSHOC project about data citation in general and more precisely how to make them actionable. The metaphor of a travel journal of an expedition seemed appropriate to us to present this work carried out during the SSHOC project.DOI: 10.5281/zenodo.6921457
Project(s): SSHOC
Metrics:
Larrousse N, Gray Ej, Concordia C
If citation is a common practice for publications, it is relatively new for data especially in SSH. This paper will present the work carried out during the SSHOC project about data citation in general and more precisely how to make them actionable. The metaphor of a travel journal of an expedition seemed appropriate to us to present this work carried out during the SSHOC project.DOI: 10.5281/zenodo.6921457
Project(s): SSHOC
Metrics:
See at:
CNR IRIS | ISTI Repository | zenodo.org | CNR IRIS
2022
Conference article
Open Access
The SSH Data Citation Service, a tool to explore and collect citation metadata
Concordia C, Larrousse N, Gray E
This paper presents the SSH Data Citation Service (DCS), a software tool that provides functionalities to find, collect and analyse metadata related to digital objects, in particular datasets, referred to in citation strings. Starting from the citation string of a dataset, the DCS aggregates metadata related to the data from different sources: the repository hosting the dataset, PID Registration Agencies and Knowledge Graphs and gives a unified view of information about datasets coming from these sources. The DCS has been designed and developed in the Social Sciences & Humanities Open Cloud (SSHOC) project. It has been used in a project activity as a tool to help investigate approaches adopted for data citation by Social Sciences and Humanities organisations managing data repositories, and as an utility to help data managers to create citation metadata. The paper presents motivations underlying the creation of the tool, the design principles adopted, an overall description of the functionalities of the current release and a summary of ongoing activities.DOI: 10.1007/978-3-031-16802-4_32
Project(s): SSHOC
Metrics:
Concordia C, Larrousse N, Gray E
This paper presents the SSH Data Citation Service (DCS), a software tool that provides functionalities to find, collect and analyse metadata related to digital objects, in particular datasets, referred to in citation strings. Starting from the citation string of a dataset, the DCS aggregates metadata related to the data from different sources: the repository hosting the dataset, PID Registration Agencies and Knowledge Graphs and gives a unified view of information about datasets coming from these sources. The DCS has been designed and developed in the Social Sciences & Humanities Open Cloud (SSHOC) project. It has been used in a project activity as a tool to help investigate approaches adopted for data citation by Social Sciences and Humanities organisations managing data repositories, and as an utility to help data managers to create citation metadata. The paper presents motivations underlying the creation of the tool, the design principles adopted, an overall description of the functionalities of the current release and a summary of ongoing activities.DOI: 10.1007/978-3-031-16802-4_32
Project(s): SSHOC
Metrics:
See at:
CNR IRIS | link.springer.com | ISTI Repository | CNR IRIS | CNR IRIS
2022
Conference article
Open Access
Towards FAIR data access
Broeder D, Elbers W, Gawor M, Concordia C, Larrousse N, Van Uytvanck D
Background In the past decade many different national, EU and global projects have been successful in raising awareness about Open Science and the importance of making data findable and accessible such as stated in the FAIR principles (Wilkinson et al. 2016).In this respect, there have been many advances with respect to options for discovering data. A multitude of either thematic or general catalogues are providing faceted browsing interfaces for humans and Application Programming Interfaces (APIs) for use by machines and similarly, data-citations in publications offer references to resources hosted by repositories. However, using such catalogues and data-citations, researchers are not guaranteed to obtain access to the data itself. Mostly the resource link in the catalogue (and also in the metadata) or citation is a "landing-page", a description of the resource meant for human consumption. The landing-page may contain instructions how to access or download the resource itself but usually it is difficult to parse by machines.FAIR data accessThus the approach sketched above does not meet the requirements in scenarios where applications need assured and quick access to data. Also the FAIR principles interpretation from GO FAIR states*1 that these "emphasise machine-actionability (i.e., the capacity of computational systems to find, access, interoperate, and reuse data with none or minimal human intervention) because humans increasingly rely on computational support to deal with data as a result of the increase in volume, complexity, and creation speed of data." The requirement for providing a Persistent Identifier (PID) for a resource*2, is mostly interpreted as meaning a PID for the resource's metadata or landing-page only. Note that we ignore the need for user authentication and authorization prior to accessing data, here we will only consider data that is 'freely' accessible.To improve the situation with respect to machine data accessibility a number of technologies and approaches that have been discussed in the CLARIN and Social Sciences and Humanities (SSH) infrastructure domain can be useful. We present some and comment on their suitability.SignpostingSignposting*3 is a technology proposed by van de Sompel (Sompel and Nelson 2015) to release relevant technical and bibliographical attributes from a resource URI. It's well described, and uses the HTTP protocol to provide additional information via HTTP Link Headers*4. Alternatively, for HTML type resources, the information may also be provided in HTML Link elements. In the CLARIN community the signposting concept was accepted, but its proposed implementation deviated from van de Sompel and made it less dependent on the HTTP protocol (Arnold et al. 2021). However on the downside, the signposting information is embedded in the CLARIN specific Component Metadata (CMDI) (Broeder et al. 2012), and so makes it CLARIN specific, or at least requires clients to have specific knowledge about CMDI.CLARIN Digital Object Gateway (DOG)One approach that is currently worked on for the CLARIN research infrastructure is the creation of a DOG library*5 and (later) a service that provides a proxy gateway from the resource PID to the actual data. DOG uses implicit knowledge about the different repository solutions that are used by the CLARIN B-type centres*6 and some repositories outside the CLARIN infrastructure. DOG works in two steps: first obtaining metadata from the resource PID and secondly extracting resource links from the metadata. Each of the repositories registered within DOG has a minimal configuration specifying how to parse fields of interest from the resource's metadata. For B-type CLARIN centres DOG uses content negotiation as the primary way of obtaining the metadata in CMDI format. For repositories outside the CLARIN infrastructure, DOG primarily relies on the API provided by the repository in order to access metadata and data resources. The DOG solution does have scalability problems, but within the limited domain of CLARIN centres, it can offer a solution until a better one becomes available.Limited PID kernel informationThe (limited) PID kernel information approach assumes that for every Digital Object (DO) (Berg-Cross et al. 2015) and its metadata a Handle type PID (CNRI 2020) is issued and that the Handle information record can be used to store and associate additional important information with the (meta) data PID using handle value types such as for example a checksum and references to the data or metadata. This is a simplification of the architecture proposed in the work done in RDA context: PID Kernel Info recommendations (Weigel et al. 2018). Consistent use of Handle information records could solve the data access problem, but just as for the signposting strategy, it requires strong discipline to maintain the additional information source. Examples from smaller projects and repositories exist that do manage this information in the Handle record eg. the DARIAH-DE repository*7. FAIR Digital Objects (FDO)FDOs*8 attempt to overcome the data management challenges posed by the heterogeneity and complexity of data using a combination of abstraction, virtualization and encapsulation (Schwardmann 2020). In practice, in the context of our access to data problem, the FDO solution can be seen as both a generalization and upgrade of the PID kernel information approach. The key characteristics here are the (conceptual) encapsulation of data objects with data structure and services that allow aware applications to recognize the data objects metadata and bitstream format, and process as intended by the programmer. Eligible data processing services, either general ones from communities, can be found through the FDO typing mechanism, or can be directly linked from the FDO.A rich set of FDO attributes permit signaling machines processing FDOs where and how to access bitstream data including for instance additional information about supported protocols and APIs.What to do?For our community and in our collaboration with others, we need solutions now but would prefer not to invest and get closed in unscalable technologies.We would propose to combine the DOG approach with signposting. First testing URIs (obtained by resolving the Handle PID) for the presence of HTTP Link Headers. If these are missing, (extended) DOG could use its idiosyncratic workflow. Long term we see advantages of the general, scalable and protocol independent approach that FDOs offer. Hybrid solutions are conceivable where FDO proxies can sit between the FDO machinery and data hosted by signposting compliant repositories.DOI: 10.3897/rio.8.e94386
Metrics:
Broeder D, Elbers W, Gawor M, Concordia C, Larrousse N, Van Uytvanck D
Background In the past decade many different national, EU and global projects have been successful in raising awareness about Open Science and the importance of making data findable and accessible such as stated in the FAIR principles (Wilkinson et al. 2016).In this respect, there have been many advances with respect to options for discovering data. A multitude of either thematic or general catalogues are providing faceted browsing interfaces for humans and Application Programming Interfaces (APIs) for use by machines and similarly, data-citations in publications offer references to resources hosted by repositories. However, using such catalogues and data-citations, researchers are not guaranteed to obtain access to the data itself. Mostly the resource link in the catalogue (and also in the metadata) or citation is a "landing-page", a description of the resource meant for human consumption. The landing-page may contain instructions how to access or download the resource itself but usually it is difficult to parse by machines.FAIR data accessThus the approach sketched above does not meet the requirements in scenarios where applications need assured and quick access to data. Also the FAIR principles interpretation from GO FAIR states*1 that these "emphasise machine-actionability (i.e., the capacity of computational systems to find, access, interoperate, and reuse data with none or minimal human intervention) because humans increasingly rely on computational support to deal with data as a result of the increase in volume, complexity, and creation speed of data." The requirement for providing a Persistent Identifier (PID) for a resource*2, is mostly interpreted as meaning a PID for the resource's metadata or landing-page only. Note that we ignore the need for user authentication and authorization prior to accessing data, here we will only consider data that is 'freely' accessible.To improve the situation with respect to machine data accessibility a number of technologies and approaches that have been discussed in the CLARIN and Social Sciences and Humanities (SSH) infrastructure domain can be useful. We present some and comment on their suitability.SignpostingSignposting*3 is a technology proposed by van de Sompel (Sompel and Nelson 2015) to release relevant technical and bibliographical attributes from a resource URI. It's well described, and uses the HTTP protocol to provide additional information via HTTP Link Headers*4. Alternatively, for HTML type resources, the information may also be provided in HTML Link elements. In the CLARIN community the signposting concept was accepted, but its proposed implementation deviated from van de Sompel and made it less dependent on the HTTP protocol (Arnold et al. 2021). However on the downside, the signposting information is embedded in the CLARIN specific Component Metadata (CMDI) (Broeder et al. 2012), and so makes it CLARIN specific, or at least requires clients to have specific knowledge about CMDI.CLARIN Digital Object Gateway (DOG)One approach that is currently worked on for the CLARIN research infrastructure is the creation of a DOG library*5 and (later) a service that provides a proxy gateway from the resource PID to the actual data. DOG uses implicit knowledge about the different repository solutions that are used by the CLARIN B-type centres*6 and some repositories outside the CLARIN infrastructure. DOG works in two steps: first obtaining metadata from the resource PID and secondly extracting resource links from the metadata. Each of the repositories registered within DOG has a minimal configuration specifying how to parse fields of interest from the resource's metadata. For B-type CLARIN centres DOG uses content negotiation as the primary way of obtaining the metadata in CMDI format. For repositories outside the CLARIN infrastructure, DOG primarily relies on the API provided by the repository in order to access metadata and data resources. The DOG solution does have scalability problems, but within the limited domain of CLARIN centres, it can offer a solution until a better one becomes available.Limited PID kernel informationThe (limited) PID kernel information approach assumes that for every Digital Object (DO) (Berg-Cross et al. 2015) and its metadata a Handle type PID (CNRI 2020) is issued and that the Handle information record can be used to store and associate additional important information with the (meta) data PID using handle value types such as for example a checksum and references to the data or metadata. This is a simplification of the architecture proposed in the work done in RDA context: PID Kernel Info recommendations (Weigel et al. 2018). Consistent use of Handle information records could solve the data access problem, but just as for the signposting strategy, it requires strong discipline to maintain the additional information source. Examples from smaller projects and repositories exist that do manage this information in the Handle record eg. the DARIAH-DE repository*7. FAIR Digital Objects (FDO)FDOs*8 attempt to overcome the data management challenges posed by the heterogeneity and complexity of data using a combination of abstraction, virtualization and encapsulation (Schwardmann 2020). In practice, in the context of our access to data problem, the FDO solution can be seen as both a generalization and upgrade of the PID kernel information approach. The key characteristics here are the (conceptual) encapsulation of data objects with data structure and services that allow aware applications to recognize the data objects metadata and bitstream format, and process as intended by the programmer. Eligible data processing services, either general ones from communities, can be found through the FDO typing mechanism, or can be directly linked from the FDO.A rich set of FDO attributes permit signaling machines processing FDOs where and how to access bitstream data including for instance additional information about supported protocols and APIs.What to do?For our community and in our collaboration with others, we need solutions now but would prefer not to invest and get closed in unscalable technologies.We would propose to combine the DOG approach with signposting. First testing URIs (obtained by resolving the Handle PID) for the presence of HTTP Link Headers. If these are missing, (extended) DOG could use its idiosyncratic workflow. Long term we see advantages of the general, scalable and protocol independent approach that FDOs offer. Hybrid solutions are conceivable where FDO proxies can sit between the FDO machinery and data hosted by signposting compliant repositories.DOI: 10.3897/rio.8.e94386
Metrics:
See at:
CNR IRIS | ISTI Repository | CNR IRIS
2023
Contribution to conference
Open Access
The Social Sciences and Humanities Open Marketplace: contextualising digital resources in a registry
Barbot L, Battaner Moro E, Buddenbohm S, Concordia C, Dolinar M, Durco M, Gray E, Grisot C, Illmayer K, Kirnbauer M, Kleemola M, König A, Kurzmeier M, Mcgillivray B, Parente Boavida C, Schuster C, Vipavc Brvar I, Wnuk M
The SSH Open Marketplace is a discovery portal which pools and contextualises resources for Social Sciences and Humanities research communities: tools, services, training materials, datasets, publications and workflows. This poster presents how this service can provide insights into the use of tools, methods and standards in the DH research communities.DOI: 10.5281/zenodo.8107637
Metrics:
Barbot L, Battaner Moro E, Buddenbohm S, Concordia C, Dolinar M, Durco M, Gray E, Grisot C, Illmayer K, Kirnbauer M, Kleemola M, König A, Kurzmeier M, Mcgillivray B, Parente Boavida C, Schuster C, Vipavc Brvar I, Wnuk M
The SSH Open Marketplace is a discovery portal which pools and contextualises resources for Social Sciences and Humanities research communities: tools, services, training materials, datasets, publications and workflows. This poster presents how this service can provide insights into the use of tools, methods and standards in the DH research communities.DOI: 10.5281/zenodo.8107637
Metrics:
See at:
CNR IRIS | ISTI Repository | www.conftool.pro | ZENODO | CNR IRIS
2015
Other
Restricted
Enriching Europeana: new EuropeanaTech task force report
Isaac A, Manguinhas H, Stiller J, Charles V, Soroa A, Devarenne C, Concordia C, Vila Suero D, Haskiya D, Gavrilis D, Mäkelä E, Brinkerink M, Dangerfield Mc, Simou N, Freire N, Simon R, Bailly R, Wyns R, Verborgh R, Van Hooland S, Gornostaja T, Petras V, Alexiev V, Mamakis Y
The report presents the work carried out over seven months in 2015, during which our group has: - inventoried relevant semantic enrichment work in the Europeana Network in the past years. We have tried to do this in a way that we hope will facilitate identification and use of services relevant to the application that needs them. This includes general considerations on the diversity of the processes at hand and a focus on interoperability issues. - further developed criteria to select datasets for semantic enrichment and illustrate with a thorough analysis of selected examples - explored methodological issues for the evaluation of semantic enrichment services - performed a quantitative and qualitative evaluation of seven enrichment services on a same subset of the Europeana dataset, containing 17.300 records. This report, together with its two companion documents and a data space on the Europeana Assembla, presents all this. We have also included, as a conclusion, a number of lessons learned we think should be considered for the design and enhancement of enrichment services as well as for their evaluation.Project(s): Europeana v3.0
Isaac A, Manguinhas H, Stiller J, Charles V, Soroa A, Devarenne C, Concordia C, Vila Suero D, Haskiya D, Gavrilis D, Mäkelä E, Brinkerink M, Dangerfield Mc, Simou N, Freire N, Simon R, Bailly R, Wyns R, Verborgh R, Van Hooland S, Gornostaja T, Petras V, Alexiev V, Mamakis Y
The report presents the work carried out over seven months in 2015, during which our group has: - inventoried relevant semantic enrichment work in the Europeana Network in the past years. We have tried to do this in a way that we hope will facilitate identification and use of services relevant to the application that needs them. This includes general considerations on the diversity of the processes at hand and a focus on interoperability issues. - further developed criteria to select datasets for semantic enrichment and illustrate with a thorough analysis of selected examples - explored methodological issues for the evaluation of semantic enrichment services - performed a quantitative and qualitative evaluation of seven enrichment services on a same subset of the Europeana dataset, containing 17.300 records. This report, together with its two companion documents and a data space on the Europeana Assembla, presents all this. We have also included, as a conclusion, a number of lessons learned we think should be considered for the design and enhancement of enrichment services as well as for their evaluation.Project(s): Europeana v3.0
See at:
CNR IRIS | CNR IRIS | pro.europeana.eu
2023
Other
Open Access
Publishing SSHOC multilingual terminologies
Concordia C
The SSHOC Multilingual Terminologies consist of a set of multilingual metadata concepts and an automatically extracted multilingual Data Stewardship terminology. They have been created in the context of the SSHOC project as case studies, during an activity of investigation on how Language Technologies can help in promoting and facilitating multilingualism in the Social Sciences and Humanities. The SSHOC Multilingual terminologies has been created to evaluate performances of state-of-the-art tools and to derive a set of recommendations as to how best apply them. The talk will present the main recommendations derived from the investigation and the workflow and tools adopted to publish the Terminologies as SKOS resources.DOI: 10.5281/zenodo.7828486
Metrics:
Concordia C
The SSHOC Multilingual Terminologies consist of a set of multilingual metadata concepts and an automatically extracted multilingual Data Stewardship terminology. They have been created in the context of the SSHOC project as case studies, during an activity of investigation on how Language Technologies can help in promoting and facilitating multilingualism in the Social Sciences and Humanities. The SSHOC Multilingual terminologies has been created to evaluate performances of state-of-the-art tools and to derive a set of recommendations as to how best apply them. The talk will present the main recommendations derived from the investigation and the workflow and tools adopted to publish the Terminologies as SKOS resources.DOI: 10.5281/zenodo.7828486
Metrics:
See at:
CNR IRIS | ISTI Repository | zenodo.org | CNR IRIS | CNR IRIS | CNR IRIS
2014
Other
Open Access
The Digital Library Europeana and the Europeana Data Model (EDM)
Concordia C
Slides of two presentations held while on secondment in the Pontifícia Universidade Católica do Rio de Janeiro, in cooperation with prof. A. Casanova. Presentation topics are: the Europeana Data Model (EDM) and the Europeana Linked Data (LD). Secondment funded by project SEEK (PIRSES-GA-2011-295179)Project(s): SEEK
Concordia C
Slides of two presentations held while on secondment in the Pontifícia Universidade Católica do Rio de Janeiro, in cooperation with prof. A. Casanova. Presentation topics are: the Europeana Data Model (EDM) and the Europeana Linked Data (LD). Secondment funded by project SEEK (PIRSES-GA-2011-295179)Project(s): SEEK
See at:
CNR IRIS | ISTI Repository | ISTI Repository | CNR IRIS | CNR IRIS | CNR IRIS
2004
Conference article
Restricted
Using EAI to build public access web-based information System
Aloia N, Concordia C, Tardelli S
Enterprise Application Integration (EAI) techniques are today widely adopted to build Enterprise Information Systems. Moreover the increasing reliability of tools and techniques stemming from the 'Internet revolution' is rendering ever more convenient to base the development of new applications on Web technology, especially because of the great advantages it affords in terms of scalability and distribution. These two approaches can be used together to develop highly integrated and flexible computer systems for powerful Web-based Information Systems (WIS). In the paper we'll discuss the fundamental architectures in Enterprise Application Integration (EAI) and present issues that need to be tackled in using EAI technologies for building Public Access WIS.
Aloia N, Concordia C, Tardelli S
Enterprise Application Integration (EAI) techniques are today widely adopted to build Enterprise Information Systems. Moreover the increasing reliability of tools and techniques stemming from the 'Internet revolution' is rendering ever more convenient to base the development of new applications on Web technology, especially because of the great advantages it affords in terms of scalability and distribution. These two approaches can be used together to develop highly integrated and flexible computer systems for powerful Web-based Information Systems (WIS). In the paper we'll discuss the fundamental architectures in Enterprise Application Integration (EAI) and present issues that need to be tackled in using EAI technologies for building Public Access WIS.
2002
Conference article
Open Access