Slides used to introduce the technical aspects of DSpace-CRIS to the technical staff of the Hamburg University of Technology.
Main topics:
The DSpace-CRIS data model: additional entities, interactions with the DSpace data model (authority framework), enhanced metadata, inverse relationship
ORCID integration & technical details: available features & use cases (authentication, authorization, profile claiming, profile synchronization push & pull, registry lookup), configuration, API-KEY, use of the sandbox, metadata mapping
Bollini, Andrea, Ballarini, Emanuele, Buso, Irene, Boychuk, Mykhaylo, Cortese, Claudio, Digilio, Giuseppe, Fazio, Riccardo, Fiorenza, Damiano, Giamminonni, Luca, Lombardi, Corrado, Maffei, Stefano, Negretti, Davide, Orlandi, Sara, Pascarelli, Luigi Andrea, Perelli, Matteo, Scancarello, Immacolata, Scognamiglio, Francesco Pio, & Mornati, Susanna. (2022, June 8). DSpace-CRIS, anticipating innovation. Open Repositories 2022 (OR2022), Denver, Colorado. Zenodo. https://doi.org/10.5281/zenodo.6733234
DSpace-CRIS is the first open source CRIS/RIMS platform in the world. In 2022 the project will reach is 10th anniversary since the first open-source release of the version 1.8.2 alfa took place in November 2012.
Technically it is a fork of the DSpace platform, but the two communities have always walked together with the aim of bringing all the general purposes features of DSpace-CRIS to the main community. With version 7 and, especially, with the introduction of configurable entities in DSpace, the gap between these two "cousin" projects has been drastically reduced. However, thanks to the DSpace-CRIS community's increased experience in dealing with very complex use cases that have only recently found their way into “simple” DSpace, there are still many areas where DSpace-CRIS provides more advanced and still unique functionalities.
The presentation will summarize unique features and characteristics of DSpace-CRIS over DSpace in 7 minutes.
DSpace-CRIS: new features and contribution to the DSpace mainstream4Science
The presentation focus on the latest releases of DSpace-CRIS, compatible with DSpace 5 and 6, with new exciting features. Particularly interesting is the recent integration between DSpace-CRIS and CKAN released as an independent module. The DSpace-CKAN Integration Module has already been released in open source (same license than DSpace) and it can easily adopted also by standard DSpace installations, both JSPUI or XMLUI.
Starting with DSpace-CRIS 5.6.1, along with the security fixes of DSpace JSPUI 5.6, the following features have been introduced: an extendible UI to deliver the bitstreams with dedicated viewers, a simple metadata editing of any DSpace object; the editing of archived items using the submission UI; a deduplication and duplicate-alert tool; improved ORCiD synchronization; improved submission form; improved security model for CRIS entities; creation of CRIS object as part of the submission process, automatic calculation of metrics; advanced import framework; on-demand DOI registration; template services.
DSpace-CKAN Integration Module allows users to directly preview the dataset content deposited in a CKAN instance from DSpace via a “curation task”. DSpace-CRIS and DSpace-CKAN will be supported by 4Science also for the future major versions of the platform and the roadmap to the DSpace 7 compatibility will be also presented.
Extending DSpace 7: DSpace-CRIS and DSpace-GLAM for empowered repositories an...4Science
Presentation given at OR2019 in Hamburg, Germany
In recent years there has been an increasing need to position institutional repositories in a broader context that enhances research opportunities and facilitates the discovery of resources. This presentation is about DSpace-CRIS and DSpace-GLAM, in their new version compatible with DSpace 7, with renewed features built with the updated technology stack of DSpace 7: Angular and REST API, their characteristics and novelties, and how their adoption can empower the role of repositories within academic, research, and cultural heritage institutions. The migration process for both DSpace-CRIS/GLAM and DSpace users that want to enhance their repository with the additional features and capabilities provided by version 7 will be presented. DSpace-CRIS and GLAM are continuously being aligned with DSpace versions and support is provided through the same community channels. Finally, the future roadmap of the project will be discussed, in the same way as in the last ten years when ideas and features blossomed in DSpace-CRIS were later adopted by the standard DSpace distribution. The community is numerous and growing and the exchange of experiences is beneficial for all organizations.
Workshop held at Open Repository 2018, Bozeman, Montana
As of late 2016, a DSpace 7 UI Working Group has begun developing an Angular User Interface which will replace the existing UIs in DSpace 7. This effort also includes the development of a new REST API for DSpace, designed to follow the principles of a RESTful webservice and adopt emerging standards and formats. The goals of the REST API are twofold: (1) to fully support the new Angular UI, and (2) to provide a rich, RESTful integration point for third-party services and tools.
This workshop will allow developers to become more familiar with the new REST API framework before DSpace 7 is released.
This hands-on developers workshop will provide attendees with an overview of the DSpace 7 REST framework:
- standards / best practices that the API is based on (HAL, JSON+PATCH, JWT)
- DSpace 7 REST Contract (documentation of all endpoints)
- interacting with the REST API (via HAL browser, curl and/or postman)
- how to build new endpoints into the REST API
- where to look when issues arise
- how to document and test existing/new endpoints
Attendees will be expected to setup a virtual machine (or install the DSpace 7 codebase locally) to get more familiar with the codebase/development tools.
DSpace-CRIS slides presented at ORCID's Better Together webinar on 19.09.2019, full slide deck with ORCID introduction at https://doi.org/10.23640/07243.9884033.v2.
Video Recording available at https://vimeo.com/361523018
Bollini, Andrea, Cortese, Claudio, & Spalti, Michael. (2022, June 8). Bringing IIIF to the DSpace community. Open Repositories 2022 (OR2022), Denver, Colorado. Zenodo. https://doi.org/10.5281/zenodo.6733046
Starting with version 7.1, DSpace, provides basic support for IIIF out of box. This result was achieved thanks to the joint work of Willamette University and 4Science.
Now the DSpace 7 IIIF support allows institutions to upload images in DSpace, getting automatically a IIIF manifest for the item, based on item and bitstream (images) level metadata; in this way the TOC can be easily managed. Ideally, any IIIF compliant image server can be used, although instructions and full configuration examples are provided for Cantaloupe. Experimental support for the IIIF Search API is also available and it is expected to be refined in future releases.
Implementing IIIF is a fundamental achievement in DSpace history, since it is going to promote its use in contexts such those related to digital cultural heritage management, who were hitherto reluctant to use this Digital Asset Management System, not least because of the lack of tools for digital images management, navigation and sharing.
The presentation will introduce the available features, the architecture, the tools and strategies that can help institutions to deal with large collections using bulk imports.
Bollini, Andrea, Lombardi, Corrado, Digilio, Giuseppe, Giamminonni, Luca, & Mornati, Susanna. (2022, June 7). DSpace 7 ORCID Integration. Open Repositories 2022 (OR2022), Denver, Colorado. Zenodo. https://doi.org/10.5281/zenodo.6733036
The relevance and benefits of the ORCID persistent identifiers in the research ecosystem are increasingly evident. Nowadays users expect a good integration between the repository platform and ORCID with a bidirectional exchange of information. Unfortunately, up to now DSpace was lacking in this regard except for a very minor and limited integration allowing the submitter to query the ORCID public registry during the deposit. On the other hand, the cousin project DSpace-CRIS has featured a full integration [3] since 2014 at the time of the ORCID v1.2 API and based on a version 4 of DSpace.
Since the release of DSpace 7, the DSpace governance has been encouraging a progressive merge of these projects, backporting from DSpace-CRIS the most user-demanded features.
As a result, the DSpace 7.3 release plan includes the porting of the core ORCID integration [2], enabling DSpace users to finally connect their local DSpace profiles with ORCID, showing an authenticated ORCID badge where appropriate and pushing DSpace records to their ORCID profiles.
The presentation will show in detail the functionalities now available, the requirements to enable them in terms of ORCID membership and DSpace configuration, and the plans to bring more ORCID-related features to DSpace.
Bollini, Andrea, Ballarini, Emanuele, Buso, Irene, Boychuk, Mykhaylo, Cortese, Claudio, Digilio, Giuseppe, Fazio, Riccardo, Fiorenza, Damiano, Giamminonni, Luca, Lombardi, Corrado, Maffei, Stefano, Negretti, Davide, Orlandi, Sara, Pascarelli, Luigi Andrea, Perelli, Matteo, Scancarello, Immacolata, Scognamiglio, Francesco Pio, & Mornati, Susanna. (2022, June 8). DSpace-CRIS, anticipating innovation. Open Repositories 2022 (OR2022), Denver, Colorado. Zenodo. https://doi.org/10.5281/zenodo.6733234
DSpace-CRIS is the first open source CRIS/RIMS platform in the world. In 2022 the project will reach is 10th anniversary since the first open-source release of the version 1.8.2 alfa took place in November 2012.
Technically it is a fork of the DSpace platform, but the two communities have always walked together with the aim of bringing all the general purposes features of DSpace-CRIS to the main community. With version 7 and, especially, with the introduction of configurable entities in DSpace, the gap between these two "cousin" projects has been drastically reduced. However, thanks to the DSpace-CRIS community's increased experience in dealing with very complex use cases that have only recently found their way into “simple” DSpace, there are still many areas where DSpace-CRIS provides more advanced and still unique functionalities.
The presentation will summarize unique features and characteristics of DSpace-CRIS over DSpace in 7 minutes.
DSpace-CRIS: new features and contribution to the DSpace mainstream4Science
The presentation focus on the latest releases of DSpace-CRIS, compatible with DSpace 5 and 6, with new exciting features. Particularly interesting is the recent integration between DSpace-CRIS and CKAN released as an independent module. The DSpace-CKAN Integration Module has already been released in open source (same license than DSpace) and it can easily adopted also by standard DSpace installations, both JSPUI or XMLUI.
Starting with DSpace-CRIS 5.6.1, along with the security fixes of DSpace JSPUI 5.6, the following features have been introduced: an extendible UI to deliver the bitstreams with dedicated viewers, a simple metadata editing of any DSpace object; the editing of archived items using the submission UI; a deduplication and duplicate-alert tool; improved ORCiD synchronization; improved submission form; improved security model for CRIS entities; creation of CRIS object as part of the submission process, automatic calculation of metrics; advanced import framework; on-demand DOI registration; template services.
DSpace-CKAN Integration Module allows users to directly preview the dataset content deposited in a CKAN instance from DSpace via a “curation task”. DSpace-CRIS and DSpace-CKAN will be supported by 4Science also for the future major versions of the platform and the roadmap to the DSpace 7 compatibility will be also presented.
Extending DSpace 7: DSpace-CRIS and DSpace-GLAM for empowered repositories an...4Science
Presentation given at OR2019 in Hamburg, Germany
In recent years there has been an increasing need to position institutional repositories in a broader context that enhances research opportunities and facilitates the discovery of resources. This presentation is about DSpace-CRIS and DSpace-GLAM, in their new version compatible with DSpace 7, with renewed features built with the updated technology stack of DSpace 7: Angular and REST API, their characteristics and novelties, and how their adoption can empower the role of repositories within academic, research, and cultural heritage institutions. The migration process for both DSpace-CRIS/GLAM and DSpace users that want to enhance their repository with the additional features and capabilities provided by version 7 will be presented. DSpace-CRIS and GLAM are continuously being aligned with DSpace versions and support is provided through the same community channels. Finally, the future roadmap of the project will be discussed, in the same way as in the last ten years when ideas and features blossomed in DSpace-CRIS were later adopted by the standard DSpace distribution. The community is numerous and growing and the exchange of experiences is beneficial for all organizations.
Workshop held at Open Repository 2018, Bozeman, Montana
As of late 2016, a DSpace 7 UI Working Group has begun developing an Angular User Interface which will replace the existing UIs in DSpace 7. This effort also includes the development of a new REST API for DSpace, designed to follow the principles of a RESTful webservice and adopt emerging standards and formats. The goals of the REST API are twofold: (1) to fully support the new Angular UI, and (2) to provide a rich, RESTful integration point for third-party services and tools.
This workshop will allow developers to become more familiar with the new REST API framework before DSpace 7 is released.
This hands-on developers workshop will provide attendees with an overview of the DSpace 7 REST framework:
- standards / best practices that the API is based on (HAL, JSON+PATCH, JWT)
- DSpace 7 REST Contract (documentation of all endpoints)
- interacting with the REST API (via HAL browser, curl and/or postman)
- how to build new endpoints into the REST API
- where to look when issues arise
- how to document and test existing/new endpoints
Attendees will be expected to setup a virtual machine (or install the DSpace 7 codebase locally) to get more familiar with the codebase/development tools.
DSpace-CRIS slides presented at ORCID's Better Together webinar on 19.09.2019, full slide deck with ORCID introduction at https://doi.org/10.23640/07243.9884033.v2.
Video Recording available at https://vimeo.com/361523018
Bollini, Andrea, Cortese, Claudio, & Spalti, Michael. (2022, June 8). Bringing IIIF to the DSpace community. Open Repositories 2022 (OR2022), Denver, Colorado. Zenodo. https://doi.org/10.5281/zenodo.6733046
Starting with version 7.1, DSpace, provides basic support for IIIF out of box. This result was achieved thanks to the joint work of Willamette University and 4Science.
Now the DSpace 7 IIIF support allows institutions to upload images in DSpace, getting automatically a IIIF manifest for the item, based on item and bitstream (images) level metadata; in this way the TOC can be easily managed. Ideally, any IIIF compliant image server can be used, although instructions and full configuration examples are provided for Cantaloupe. Experimental support for the IIIF Search API is also available and it is expected to be refined in future releases.
Implementing IIIF is a fundamental achievement in DSpace history, since it is going to promote its use in contexts such those related to digital cultural heritage management, who were hitherto reluctant to use this Digital Asset Management System, not least because of the lack of tools for digital images management, navigation and sharing.
The presentation will introduce the available features, the architecture, the tools and strategies that can help institutions to deal with large collections using bulk imports.
Bollini, Andrea, Lombardi, Corrado, Digilio, Giuseppe, Giamminonni, Luca, & Mornati, Susanna. (2022, June 7). DSpace 7 ORCID Integration. Open Repositories 2022 (OR2022), Denver, Colorado. Zenodo. https://doi.org/10.5281/zenodo.6733036
The relevance and benefits of the ORCID persistent identifiers in the research ecosystem are increasingly evident. Nowadays users expect a good integration between the repository platform and ORCID with a bidirectional exchange of information. Unfortunately, up to now DSpace was lacking in this regard except for a very minor and limited integration allowing the submitter to query the ORCID public registry during the deposit. On the other hand, the cousin project DSpace-CRIS has featured a full integration [3] since 2014 at the time of the ORCID v1.2 API and based on a version 4 of DSpace.
Since the release of DSpace 7, the DSpace governance has been encouraging a progressive merge of these projects, backporting from DSpace-CRIS the most user-demanded features.
As a result, the DSpace 7.3 release plan includes the porting of the core ORCID integration [2], enabling DSpace users to finally connect their local DSpace profiles with ORCID, showing an authenticated ORCID badge where appropriate and pushing DSpace records to their ORCID profiles.
The presentation will show in detail the functionalities now available, the requirements to enable them in terms of ORCID membership and DSpace configuration, and the plans to bring more ORCID-related features to DSpace.
Or2019 DSpace 7 Enhanced submission & workflow4Science
The last two years have been very intense for the DSpace community. A great effort has been put into finalizing the development of a DSpace release, 7.0, which has many changes from previous releases, particularly with regard to UI technology.
As part of the activities related to the creation of DSpace 7, particularly innovative is the submission and workflow process that can be associated with the different collections.
The presentation will provide a deep dive into the new Enhanced Submission and Workflow features of DSpace 7, including how to configure, customize & use this feature (and differences with DSpace 6 and below)
DSpace 7 - The Power of Configurable EntitiesAtmire
Presented at the Open Repositories 2019 conference in Hamburg.
"DSpace 7 has been extended with “Configurable Entities” in response to a growing need for describing more types of objects and relations between objects as well as compound objects; examples include: authors, projects, datasets, grants, lecture series, ... .
This talk will do a deeper dive into the new Configurable Entities feature, including how to configure your DSpace to support different object models and how users can create the relations between items. New concepts in DSpace 7 such as relations between items, virtual metadata, display options per object type, … will be introduced.
Defining an object model through configuration in DSpace 7 is made possible without using specific hardcoded Java classes for the specific objects. To achieve this the concept starts from the current DSpace Item object and extends it, also allowing institutions to keep using DSpace out-of-the-box with its familiar object model. The entities in a custom object model are items that can be typed, and relations between items of different types can be created. Several different object models can be defined and can exist alongside one another in the same repository."
DSpace-CRIS: a CRIS enhanced repository platformAndrea Bollini
International Conference on Economics and Business Information 19 to 20 April 2016 in Berlin
This presentation introduces you to the version 5.5.0 of the DSpace-CRIS extension. With such extension you can capture the full picture of the research activities conduct in your institution and their context. It enables to showcase the experts, the facilities, the services and much more to attract funding, facilitate collaborations and curate the scientific reputation of your Institution.
DSpace implementation of the COAR Notify Project - status update4Science
This presentation was given to the COAR Notify WG on the 26th Jan 2022 to provide an update about the 4Science implementation in DSpace version 5 and version 6 of the identified MVP
The DSpace infrastructure for logging page-views and downloads has been limited to aggregations on communities, collections and items. While this already provides a wealth of aggregated information that is impossible to retrieve using Google Analytics, it still does not assist a repository manager in addressing questions such as:
“How many downloads did Professor X get through Google Scholar last month?”
Because authors are represented as metadata on items, tackling this challenge effectively means opening the potential to aggregate pageview and download statistics on any metadata field in the repository.
By the time of the conference, functionality that addresses this need will be available as part of @mire’s Content and Usage analysis module. The metadata based usage statistics were realized in co-development with the World Bank.
Presentation created by Lieven Droogmans, Art Lowel and Ignace Deroost.
Presented at Open Repositories 2015 by Ignace Deroost.
Learn how your DSpace repository submissions can be easier for you and your content contributors. By modifying your submission configuration you can use these not-so-obvious hints to improve the quality of information in your repository as well as minimizing the time it takes to complete a submission. Topics:
Collection templates: pre-filling certain metadata fields on a per collection basis.
Reviewer only fields: option to qualify fields in input forms to have them only visible for reviewers in the workflow
Type based submission: inclusion of certain metadata fields in the form, based on a selected submission type
Modifying your lists of dropdown values (the lists that are included at the bottom of input-forms.xml)
Working with hierarchical controlled vocabularies (the XML based subject categories)
Enabling LC Name authority control for author values
Collection based Input forms: duplicating an input-forms configuration & showing the match between an input-forms config and a collection
Simple embargo & private item state
How to enhance your DSpace repository: use cases for DSpace-CRIS, DSpace-RDM,...4Science
Presented by Susanna Mornati at the 2019 DSpace North American User Group Meeting September 23 & 24, 2019 at the University of Minnesota in Minneapolis.
Abstract: DSpace-CRIS is a free open-source platform based on DSpace for Research Data and Information Management, adopted by a wide international community of universities and research centers: DSpace-CRIS Home. It complies with recommendations, open standards and technologies such as the OAI-PMH, SignPosting, and ResourceSync (recommended by the COAR Next Generation Repositories WG), it features complete ORCID integration, compliance with the CERIF model, the IIIF framework, and with the OpenAIRE Guidelines for Literature Repositories, Data Archives, CRIS Managers, to improve findability, accessibility, interoperability, and reuse of digital assets for research and cultural heritage. DSpace-CRIS collects and disseminates information about researchers' profiles, organizations, publications, patents, grants, awards, and all entities that populate the research domain and their relationships, besides storing and exposing full-text publications, datasets, and other relevant digital objects, providing persistent identifiers and long-term preservation capabilities. DSpace-RDM exposes datasets to visual exploration and M2M streaming for analysis thanks to the integration with CKAN. DSpace-GLAM enhances the fruition of the cultural heritage through the (crowd-funded) IIIF image viewer, providing remote fruition of cultural heritage and offering a great user experience. These flavors of DSpace allow to expose and share open data, open information, and open digital objects in a collaborative, interoperable, and sustainable way. The use cases of a variety of institutions in different countries and continents will be shared to show the use of this powerful technology.
This presentation as been used to start the pilot phase of the OpenAIRE Advance' funded implementation project in DSpace-CRIS.
DSpace-CRIS now provide support for the OpenAIRE guidelines for CRIS manager in addition to the previous already supported guidelines for Literature Repository and DataArchive
IIIF and DSpace 7 - IIIF Conference 2023.pdf4Science
In the last years IIIF became the “de facto” standard for presenting, navigating and delivering digital images on the web all over the world. It defines several APIs for providing a standard method for describing, analysing and sharing images over the web, as well as "presentation-based metadata" about structured sequences of images. However, images and, in particular, cultural heritage images, to be fully analysed, interpreted and enjoyed should be inserted in a “virtual ecosystem” in which they can be related with entities such as people, places, events, fonds, etc., according to different visions and interpretations.
Therefore, since 2017, we have been working at integrating IIIF in a Digital Library environment based on DSpace, the most used Open source Digital Asset Management System, developing a dedicated addon (starting from version 5), easily integrated with a set of external Image Servers, such as Cantaloupe or Digilib, and at extending DSpace data model as well, to structure contextual relationships among cultural heritage entities at different levels.
After DSpace 7 release, we worked with the community at integrating IIIF support in the official DSpace codebase. Now the DSpace REST API implements the IIIF Presentation API version 2.1.1, the IIIF Image API version 2.1.1, and the IIIF Search API version 1.0 (experimental). Any IIIF compliant image server can be integrated. The DSpace Angular frontend uses the Mirador 3.0 viewer.
However, Digital Library requirements are getting complex and complex. Therefore, to fulfil the needs of the cultural heritage domain, we enhanced our solutions based on DSpace 7, developing two further add-ons to integrate and enrich the “IIIF experience” within DSpace: the Document Viewer (for visualizing PDF files within Mirador) and the OCR module (for extracting text from images and indexing it).
Integrating IIIF and DSpace 7 and enriching the platform with new features, it has been possible to go beyond the traditional boundaries of the Digital libraries, structuring a complex system of relationships, building new narratives thanks to interdisciplinarity and the coexistence of different domains.
The proposed 2 hours workshop, addressed to librarians, archivists, historians, archaeologists, researchers and to all those who want to build their own digital library with DSpace 7 and IIIF, will introduce the attendees to the IIIF integration in DSpace both from the backend and from the frontend side.
We will analyze and share our approach and standard workflows for managing cultural heritage documents in DSpace using IIIF, starting with images submission and describing the operations required to make images available to the Mirador Image Viewer, the ones for extracting the text via OCR and for visualizing PDFs through the Image Viewer. Moreover, we will show how to relate items to each other, in order to build a complex system of relationships between entities, to be explored through network graphs.
Azure Data Explorer deep dive - review 04.2020Riccardo Zamana
Full review 04.2020 about Azure Data Explorer service. Slide Desk is a sort of review od Kusto, in terms of usage, ingestion techniques, querying and exporting data, using anomaly detection and clustering methods.
This presentation mainly intends to explain how to gather the author name, title, submission year, keywords, subjects, department, university, language, and the number of pages of every thesis document in Theseus and then reuse the gathered data for building a Web portal.
DSP3B: DSpace Interest Group 3B: DSpace-CRIS Workshop · 11/Jun/2015: 3:30pm-5:00pm · Location: Regency E
DSpace-CRIS Workshop
Andrea Bollini, Luigi Andrea Pascarelli, Michele Mennielli, David Palmer
Cineca, Italy; Hong Kong University
The 90-minute workshop will introduce attendees to the latest version of the DSpace-CRIS module, covering its functional and technical aspects.
DSpace-CRIS is an additional open-source module for the DSpace platform. It extends the DSpace data model providing the ability to manage, collect and expose data about any entities of the research domain, such as people, organizational units, projects, grants, awards, patents, publications, and so on. Before OR2015 a new version of the system will be released to follow the new DSpace 5.0 version. The new version contains, among other things, important enhancements of its integration with ORCID.
The DSpace-CRIS extensible data model will be explained in depth, through examples and discussion with participants.
Other main topics are DSpace-CRIS "components", management of relationships and network analysis functionalities.
At the end of the workshop, participants will be able to:
- understand the DSpace-CRIS data model
- evaluate if DSpace-CRIS fits the requirements of their institution
- use the DSpace-CRIS User Interface
- change the default configuration, adapting it to a specific data model.
Or2019 DSpace 7 Enhanced submission & workflow4Science
The last two years have been very intense for the DSpace community. A great effort has been put into finalizing the development of a DSpace release, 7.0, which has many changes from previous releases, particularly with regard to UI technology.
As part of the activities related to the creation of DSpace 7, particularly innovative is the submission and workflow process that can be associated with the different collections.
The presentation will provide a deep dive into the new Enhanced Submission and Workflow features of DSpace 7, including how to configure, customize & use this feature (and differences with DSpace 6 and below)
DSpace 7 - The Power of Configurable EntitiesAtmire
Presented at the Open Repositories 2019 conference in Hamburg.
"DSpace 7 has been extended with “Configurable Entities” in response to a growing need for describing more types of objects and relations between objects as well as compound objects; examples include: authors, projects, datasets, grants, lecture series, ... .
This talk will do a deeper dive into the new Configurable Entities feature, including how to configure your DSpace to support different object models and how users can create the relations between items. New concepts in DSpace 7 such as relations between items, virtual metadata, display options per object type, … will be introduced.
Defining an object model through configuration in DSpace 7 is made possible without using specific hardcoded Java classes for the specific objects. To achieve this the concept starts from the current DSpace Item object and extends it, also allowing institutions to keep using DSpace out-of-the-box with its familiar object model. The entities in a custom object model are items that can be typed, and relations between items of different types can be created. Several different object models can be defined and can exist alongside one another in the same repository."
DSpace-CRIS: a CRIS enhanced repository platformAndrea Bollini
International Conference on Economics and Business Information 19 to 20 April 2016 in Berlin
This presentation introduces you to the version 5.5.0 of the DSpace-CRIS extension. With such extension you can capture the full picture of the research activities conduct in your institution and their context. It enables to showcase the experts, the facilities, the services and much more to attract funding, facilitate collaborations and curate the scientific reputation of your Institution.
DSpace implementation of the COAR Notify Project - status update4Science
This presentation was given to the COAR Notify WG on the 26th Jan 2022 to provide an update about the 4Science implementation in DSpace version 5 and version 6 of the identified MVP
The DSpace infrastructure for logging page-views and downloads has been limited to aggregations on communities, collections and items. While this already provides a wealth of aggregated information that is impossible to retrieve using Google Analytics, it still does not assist a repository manager in addressing questions such as:
“How many downloads did Professor X get through Google Scholar last month?”
Because authors are represented as metadata on items, tackling this challenge effectively means opening the potential to aggregate pageview and download statistics on any metadata field in the repository.
By the time of the conference, functionality that addresses this need will be available as part of @mire’s Content and Usage analysis module. The metadata based usage statistics were realized in co-development with the World Bank.
Presentation created by Lieven Droogmans, Art Lowel and Ignace Deroost.
Presented at Open Repositories 2015 by Ignace Deroost.
Learn how your DSpace repository submissions can be easier for you and your content contributors. By modifying your submission configuration you can use these not-so-obvious hints to improve the quality of information in your repository as well as minimizing the time it takes to complete a submission. Topics:
Collection templates: pre-filling certain metadata fields on a per collection basis.
Reviewer only fields: option to qualify fields in input forms to have them only visible for reviewers in the workflow
Type based submission: inclusion of certain metadata fields in the form, based on a selected submission type
Modifying your lists of dropdown values (the lists that are included at the bottom of input-forms.xml)
Working with hierarchical controlled vocabularies (the XML based subject categories)
Enabling LC Name authority control for author values
Collection based Input forms: duplicating an input-forms configuration & showing the match between an input-forms config and a collection
Simple embargo & private item state
How to enhance your DSpace repository: use cases for DSpace-CRIS, DSpace-RDM,...4Science
Presented by Susanna Mornati at the 2019 DSpace North American User Group Meeting September 23 & 24, 2019 at the University of Minnesota in Minneapolis.
Abstract: DSpace-CRIS is a free open-source platform based on DSpace for Research Data and Information Management, adopted by a wide international community of universities and research centers: DSpace-CRIS Home. It complies with recommendations, open standards and technologies such as the OAI-PMH, SignPosting, and ResourceSync (recommended by the COAR Next Generation Repositories WG), it features complete ORCID integration, compliance with the CERIF model, the IIIF framework, and with the OpenAIRE Guidelines for Literature Repositories, Data Archives, CRIS Managers, to improve findability, accessibility, interoperability, and reuse of digital assets for research and cultural heritage. DSpace-CRIS collects and disseminates information about researchers' profiles, organizations, publications, patents, grants, awards, and all entities that populate the research domain and their relationships, besides storing and exposing full-text publications, datasets, and other relevant digital objects, providing persistent identifiers and long-term preservation capabilities. DSpace-RDM exposes datasets to visual exploration and M2M streaming for analysis thanks to the integration with CKAN. DSpace-GLAM enhances the fruition of the cultural heritage through the (crowd-funded) IIIF image viewer, providing remote fruition of cultural heritage and offering a great user experience. These flavors of DSpace allow to expose and share open data, open information, and open digital objects in a collaborative, interoperable, and sustainable way. The use cases of a variety of institutions in different countries and continents will be shared to show the use of this powerful technology.
This presentation as been used to start the pilot phase of the OpenAIRE Advance' funded implementation project in DSpace-CRIS.
DSpace-CRIS now provide support for the OpenAIRE guidelines for CRIS manager in addition to the previous already supported guidelines for Literature Repository and DataArchive
IIIF and DSpace 7 - IIIF Conference 2023.pdf4Science
In the last years IIIF became the “de facto” standard for presenting, navigating and delivering digital images on the web all over the world. It defines several APIs for providing a standard method for describing, analysing and sharing images over the web, as well as "presentation-based metadata" about structured sequences of images. However, images and, in particular, cultural heritage images, to be fully analysed, interpreted and enjoyed should be inserted in a “virtual ecosystem” in which they can be related with entities such as people, places, events, fonds, etc., according to different visions and interpretations.
Therefore, since 2017, we have been working at integrating IIIF in a Digital Library environment based on DSpace, the most used Open source Digital Asset Management System, developing a dedicated addon (starting from version 5), easily integrated with a set of external Image Servers, such as Cantaloupe or Digilib, and at extending DSpace data model as well, to structure contextual relationships among cultural heritage entities at different levels.
After DSpace 7 release, we worked with the community at integrating IIIF support in the official DSpace codebase. Now the DSpace REST API implements the IIIF Presentation API version 2.1.1, the IIIF Image API version 2.1.1, and the IIIF Search API version 1.0 (experimental). Any IIIF compliant image server can be integrated. The DSpace Angular frontend uses the Mirador 3.0 viewer.
However, Digital Library requirements are getting complex and complex. Therefore, to fulfil the needs of the cultural heritage domain, we enhanced our solutions based on DSpace 7, developing two further add-ons to integrate and enrich the “IIIF experience” within DSpace: the Document Viewer (for visualizing PDF files within Mirador) and the OCR module (for extracting text from images and indexing it).
Integrating IIIF and DSpace 7 and enriching the platform with new features, it has been possible to go beyond the traditional boundaries of the Digital libraries, structuring a complex system of relationships, building new narratives thanks to interdisciplinarity and the coexistence of different domains.
The proposed 2 hours workshop, addressed to librarians, archivists, historians, archaeologists, researchers and to all those who want to build their own digital library with DSpace 7 and IIIF, will introduce the attendees to the IIIF integration in DSpace both from the backend and from the frontend side.
We will analyze and share our approach and standard workflows for managing cultural heritage documents in DSpace using IIIF, starting with images submission and describing the operations required to make images available to the Mirador Image Viewer, the ones for extracting the text via OCR and for visualizing PDFs through the Image Viewer. Moreover, we will show how to relate items to each other, in order to build a complex system of relationships between entities, to be explored through network graphs.
Azure Data Explorer deep dive - review 04.2020Riccardo Zamana
Full review 04.2020 about Azure Data Explorer service. Slide Desk is a sort of review od Kusto, in terms of usage, ingestion techniques, querying and exporting data, using anomaly detection and clustering methods.
This presentation mainly intends to explain how to gather the author name, title, submission year, keywords, subjects, department, university, language, and the number of pages of every thesis document in Theseus and then reuse the gathered data for building a Web portal.
DSP3B: DSpace Interest Group 3B: DSpace-CRIS Workshop · 11/Jun/2015: 3:30pm-5:00pm · Location: Regency E
DSpace-CRIS Workshop
Andrea Bollini, Luigi Andrea Pascarelli, Michele Mennielli, David Palmer
Cineca, Italy; Hong Kong University
The 90-minute workshop will introduce attendees to the latest version of the DSpace-CRIS module, covering its functional and technical aspects.
DSpace-CRIS is an additional open-source module for the DSpace platform. It extends the DSpace data model providing the ability to manage, collect and expose data about any entities of the research domain, such as people, organizational units, projects, grants, awards, patents, publications, and so on. Before OR2015 a new version of the system will be released to follow the new DSpace 5.0 version. The new version contains, among other things, important enhancements of its integration with ORCID.
The DSpace-CRIS extensible data model will be explained in depth, through examples and discussion with participants.
Other main topics are DSpace-CRIS "components", management of relationships and network analysis functionalities.
At the end of the workshop, participants will be able to:
- understand the DSpace-CRIS data model
- evaluate if DSpace-CRIS fits the requirements of their institution
- use the DSpace-CRIS User Interface
- change the default configuration, adapting it to a specific data model.
How to describe a dataset. Interoperability issuesValeria Pesce
Presented by Valeria Pesce during the pre-meeting of the Agricultural Data Interoperability Interest Group (IGAD) of the Research Data Alliance (RDA), held on 21 and 22 September 2015 in Paris at INRA.
by Darin Briskman, Technical Evangelist, AWS
SQL is a powerful tool to query data, but it doesn't cover everything you might need. Sometimes, the precision of SQL is a limitation, that can be overcome by using the flexibility and inherent ranking of search. Learn how to use AWS servcies to create fully managed solutions using Amazon Aurora and Amazon Elasticsearch Service to combine the power of query and search. Level: 200
Common Data Service – A Business Database!Pedro Azevedo
In this session I tried to explain to SQL Community what is Common Data Service, it's a new Database or only a service to allow Power Users to create applications.
Part 4 of tutorials at DC2008, Berlin. (International Conference on Dublin Core and Metadata Applications). See also part 1-3 by Jane Greenberg, Pete Johnston, and Mikael Nilsson on DC history, concepts, and other schemas. This part focuses on practical issues.
SQL is a powerful tool to query data, but it doesn't cover everything you might need. Sometimes, the precision of SQL is a limitation, that can be overcome by using the flexibility and inherent ranking of search. Learn how to use AWS servcies to create fully managed solutions using Amazon Aurora and Amazon Elasticsearch Service to combine the power of query and search.
An architecture for federated data discovery and lineage over on-prem datasou...DataWorks Summit
Comcast's Streaming Data platform comprises a variety of ingest, transformation, and storage services in the public cloud. Peer-reviewed Apache Avro schemas support end-to-end data governance. We have previously reported (DataWorks Summit 2017) on how we extended Atlas with custom entity and process types for discovery and lineage in the AWS public cloud. Custom lambda functions notify Atlas of creation of new entities and new lineage links via asynchronous kafka messaging.
Recently we were presented the challenge of providing integrated data discovery and lineage across our public cloud datasources and on-prem datasources, both Hadoop-based and traditional data warehouses and RDBMSs. Can Apache Atlas meet this challenge? A resounding yes! This talk will present our federated architecture, with Atlas providing SQL-like, free-text, and graph search across select metadata from all on-prem and public cloud data sources in our purview. Lightweight, custom connectors/bridges identify metadata/lineage changes in underlying sources and publish them to Atlas via the asynchronous API. A portal layer provides Atlas query access and a federation of UIs. Once data of interest is identified via Atlas queries, interfaces specific to underlying sources may be used for special-purpose metadata mining.
While metadata repositories for data discovery and lineage abound, none of them have built-in connectors and listeners for the entire complement of data sources that Comcast and many other large enterprises use to support their business needs. In-house-built solutions typically underestimate the cost of development and maintenance and often suffer from architecture-by-accretion. Atlas' commitment to extensibility, built-in provision of typed, free-text, and graph search, and REST and asynchronous APIs, position it uniquely in the build-vs-buy sweet spot.
10-15-13 “Metadata and Repository Services for Research Data Curation” Presen...DuraSpace
“Hot Topics: The DuraSpace Community Webinar Series," Series Six: Research Data in Repositories” Curated by David Minor, Research Data Curation Program, UC San Diego Library. Webinar 2: “Metadata and Repository Services for Research Data Curation”
Presented by Declan Fleming, Chief Technology Strategist, Arwen Hutt, Metadata Librarian & Matt Critchlow, Manager of Development and Web ServicesUC, San Diego Library.
Common Data Model - A Business Database!Pedro Azevedo
In this session I presented how Common Data Service will be the future of Business Application Platform and how this platform will help the Dynamics 365 to grow.
Expressing Concept Schemes & Competency Frameworks in CTDLCredential Engine
This presentation is focused on how the Credential Engine can access 3rd party resource data stores and recipes for mapping and publishing competency frameworks as Linked Data.
High Performance JSON Search and Relational Faceted Browsing with Lucenelucenerevolution
Presented by Renaud Delbru, Co-Founder, SindiceTech
In this presentation, we will discuss how Lucene and Solr can be used for very efficient search of tree-shaped schemaless document, e.g. JSON or XML, and can be then made to address both graph and relational data search. We will discuss the capabilities of SIREn, a Lucene/Solr plugin we have developed to deal with huge collections of tree-shaped schemaless documents, and how SIREn is built using Lucene extensibility capabilities (Analysis, Codec, Flexible Query Parser). We will compare it with Lucene's BlockJoin Query API in nested schemaless data intensive scenarios. We will then go through use cases that show how relational or graph data can be turned into JSON documents using Hadoop and Pig, and how this can be used in conjunction with SIREn to create relational faceting systems with unprecedented performance. Take-away lessons from this session will be awareness about using Lucene/Solr and Hadoop for relational and graph data search, as well as the awareness that it is now possible to have relational faceted browsers with sub-second response time on commodity hardware.
Similar to DSpace-CRIS technical level introduction (20)
From Digital Records to Digital Cultural Landscapes. Beyond Digital Library b...4Science
In a Digital Library environment, we can define Digital cultural landscapes as “virtual ecosystems” in which digital cultural heritage subsets are related with entities such as people, places, events, fonds, etc., according to different visions and interpretations, in a pluralism generating new knowledge and opening up new perspectives. These virtual ecosystems today can be easily structured by cultural institutions, using a popular application such as DSpace, the world's most widely used open source Digital Asset Management System.
Extending the DSpace data model and enriching the platform with new features allows, indeed, to go beyond the traditional boundaries of the Digital libraries, structuring a complex system of relationships between entities, to be explored through networks, structured paths and viewers, building new narratives thanks to interdisciplinarity and the coexistence of different domains (Galleries, Libraries, Archives, Museums and even more).
Digital Libraries represent today, at least in the Humanities, the main tools not only for recomposing cultural information, but also for producing new knowledge, provided, however, that they are not mere lists of items grouped into collections, but become tools allowing the definition of relationships on different scales and according to different variability dimensions, in order to reconstruct real digital cultural landscapes within which, for example, a document can be explored and analyzed in relation to other documents and to all the information helping to define its context, or rather its different contexts (historical, geographical, cultural, etc.).
Moreover, since Digital Library requirements are getting complex and complex, to fulfil the needs of the cultural heritage domain, we enhanced our solutions based on DSpace, developing a IIIF ecosystem built on top of three add-ons, the IIIF Image Viewer Mirador, the Document Viewer (for visualizing PDF files within
Mirador) and the OCR module (for extracting text from images and indexing it).
Nowadays a Digital Library should be able to tell its content in different ways to different audiences. Therefore, we will illustrate what we implemented in DSpace, in order to enhance the storytelling and communication capabilities of the Digital Library.
“Adoption DSpace 7 and 8 Challenges and Solutions from Real Migration Experie...4Science
In this insightful presentation we will provide a profound analysis of the complexities institutions face during the migration process. With a focus on real-world examples, the presentation will explore challenges encountered when transitioning from older DSpace versions and diverse platforms such as EPrints and Invenio. The session will also offer a sneak peek into DSpace 8, anticipated to reshape the landscape of digital repositories.
Implementing the Notify protocol and standard practices in DSpace4Science
Bollini, Andrea, Lombardi, Corrado, Maffei, Stefano, Welling, William, & Carvalho, José. (2022, June 8). Implementing the Notify protocol and standard practices in DSpace. Open Repositories 2022 (OR2022), Denver, Colorado. Zenodo. https://doi.org/10.5281/zenodo.6671781
We will present the Notify implementation that is currently proposed for the official adoption in DSpace.
A technical introduction about the COAR Notify project [1] will be provided, showing how the use of the Linked Data Notification protocol [2], standard messages and patterns allow to integrate the repository with relevant services in a distributed, resilient and web-native architecture.
The implementation has been made available as a patch for DSpace 5 and 6 in February 2022 and it is proposed for official inclusion in DSpace 7 [4, 5, 6]. This first implementation is based on the definition of a Minimum Viable Product reviewed with the COAR Notify Working Group, funded by U. Minho and developed by 4Science focused on the open peer-review scenarios. The Harvard University is currently updating their digital services and has adopted the Notify protocol to better integrate their DSpace Institution Repository with their Dataverse Data Repository.
The Open Peer-review and IR – Data Repository integration scenarios will be demonstrated.
Bollini, Andrea, Buso, Irene, Mornati, Susanna, Digilio, Giuseppe, Giamminonni, Luca, & Pavlidou, Androniki. (2022). The EOSC DIH "ELD Advance" project. Open Repositories 2022 (OR2022), Denver, Colorado. Zenodo. https://doi.org/10.5281/zenodo.6733599
The poster will provide an overview of the ELD ADVANCE project supported by the European Open Science Cloud Digital Innovation HUB (EOSC DIH).
In spring 2021, as part of the OpenAIRE ELD project 4Science released two new services: the Data Correction (based on the OpenAIRE Notification Broker), to enrich repository data by exploiting the vast amount of information made available by OpenAIRE, and the Publication Claim (based on the OpenAIRE Graph), to ensure that the repository stays up to date by automatically discovering new content produced by the institution’s researchers in the OpenAIRE Graph, thus reducing the manual input from researchers.
This new project aims to achieve full impact extending these services to plain DSpace repositories making them available out-of-box in the latest releases of DSpace as it was already done in DSpace-CRIS.
Moreover, additional technical improvements will be introduced to streamline the adoption and set the basis for future extensions of the services.
The presentation is about the new version of DSpace-CRIS 7, the enhanced, free, open-source extensions of DSpace adopted by more than one hundred institutions around the world to better collect, manage and disseminate information on their research activities and outputs. DSpace-CRIS has always anticipated the cutting edge innovation and technologies later included in the DSpace mainstream, and version 7 includes functionalities not available in DSpace 7.
Digital library: riflessioni su scelte e obiettivi. Visibilità delle collezio...4Science
I webinar di 4Science
Abstract
Come Alberto Salarelli scrive nel suo recente contributo in Bibliotecae.it, la storia delle biblioteche digitali è una “storia complessa”. Sono “uno strumento che ha visto mutare il proprio pubblico di riferimento, prima identificabile sostanzialmente con la platea dei professionisti della ricerca per poi aprirsi progressivamente verso le istanze di un’utenza meno specialistica ma, non di rado, particolarmente ansiosa di usufruire degli immensi patrimoni custoditi negli istituti della memoria collettiva, finalmente accessibili dal proprio computer”. Questo mutamento ci deve far riflettere sulle scelte dei contenuti, sugli obiettivi e su nuove modalità (e approcci) di valorizzazione.
Enhancing Interoperability: The Implementation of OpenAIRE Guidelines and COA...4Science
ABSTRACT: The continuous work of the OpenAIRE community on guidelines for CRIS managers, literature repositories, and data archives, together with the publication of the “Behaviours and Technical Recommendations of the COAR Next Generation Repositories Working Group”, are raising important challenges for the CRIS and the repository communities, working together to make research information more an more interoperable, and, hopefully, open. The recommendations of the Open Science Policy Platform, published by the European Commission, identify FAIR (Findable-Accessible-Interoperable-Reusable) data among its priorities. In an interoperable world, all these indications lead toward a common direction, where implementers are encouraged to use open protocols, such as the OAI-PMH and ResourceSync, open standards such as CERIF, persistent identifiers such as DOIs and ORCiDs, to make this happen. The presentation will go through these challenges, illustrating how CRIS and repository managers should work together toward a successful information exchange, and exemplifying how a single free open platform, DSpace-CRIS, can implement both a CRIS and a repository and fulfill requirements for a FAIR environment for research information and research objects.
DSpace 7 - Creating High-Quality Software: Update to Development Practices4Science
Presentation given at OR2019 in Hamburg
DSpace 7 has offered the opportunity to enforce and improve practices introduced in previous years in the DSpace development process [1] moving forward to a Test-Driven Development (TDD) process. The presentation will provide an overview of the current practices and processes used from DSpace 7 on with regard to the test, development and documentation of the software: concrete examples about how to report a bug, solve a bug, propose and develop a new feature will be presented.
The use of the git branch and github PRs [2] will be shown to illustrate how automatic testing helps to quickly validate changes, discover impact on unexpected points in the software and collaboratively improve the proposed solution. This will demonstrate the value of new requirements about code styling [3], code documentation, raising the test coverage and recommendation to provide automatic test to uncover found bugs. The introduction of community development sprints [4] provides community developers the opportunity to learn the new development processes in a hands-on fashion, with the help of fellow developers and coaches.
The introduction of new DSpace docker images [5] (for each published branch) helps to simplify the development process by allowing developers to more easily test, validate and manage code changes against multiple versions of DSpace..
Finally, the REST contract [6] and the use of wireframes [7] will be presented as best practices to support early sharing of ideas and development proposals, and to drive uniformity in the implementation both on the REST and on the Angular side.
Presentation given at OR2019 Hamburg
DSpace 7 is a major update of the DSpace platform with a new substantial different architecture than previous DSpace versions. The need to provide a fully-fledged REST API layer on top of which the new Angular (javascript) UI has been built was the opportunity to move to updated technologies, standards and best practice for the REST layer previously quickly introduced in the DSpace landscape to meet urgent needs of interoperability.
Indeed, the goal of the new REST API is to meet the level 3 of the famous Richardson Maturity Model [1] allowing a client application or its developer to potentially learn how to use the API without pre-knowledge or need to consult external information. The adoption of uniform, consistent and self-documented behaviour will drastically reduce the effort for developers to interact with DSpace.
Moreover, each operation that can be performed from the UI as an anonymous user or a user with whatever privilege, including repository managers and administrators, can now be done via a standard REST API. To offer a strong interoperability layer is crucial to provide a stable, well documented and fully tested solution so that integration will not easily break from one version to another: for this reason the REST development adopted a Test-Driven Development and Contract [2] first approach.
The presentation will illustrate the adopted standards HATEOAS [3], HAL [4], JWT [5], ALPS [6] showing how to interact with the new REST API to get and manipulate information.
Different integration scenarios will be presented explaining how the new REST API can be used to implement them. This will include reuse of the information available in DSpace in other contexts such as personal, departmental or institutional websites. Integration of DSpace in research workflows for data acquisition, embedding of the repository in wide institutional processes like ETD preparation triggering workflow automation in response of external events. Quickly prototyping end users functionalities such as notification services, reporting tools, batch processing in the language of preference of developers.
The development processes and technologies [7] will also be quickly introduced as a reference to provide direction to those interested in customizing the new REST API or to participate in its future development.
IIIF Authentication API: access control and sustainability of open digital li...4Science
Presented at Open Repository 2018, Bozeman, Montana
As said in the IIIF Authentication API Documentation, “Open access to content is desirable, but internal policies, legal regulations, business models, and other constraints can require users to authenticate and be authorized to interact with some resources”. In this context IIIF Authentication API has been developed to start an interaction with an access control system to acquire the credentials needed to see restricted content. The proposed presentation will illustrate how we implemented the Authentication API within our IIIF add-on module for DSpace and moreover how it can interact not only with access control systems but also with e-commerce modules. This is very important because, mainly in the cultural heritage domain, the selling of digitized documents for research purposes is one of the few ways for institutions to maintain and increase the content of their Digital Library beyond grants. Therefore, 4Science developed an e-commerce add-on module for DSpace, based on the open source plug-in for Wordpress, Woocommerce, also interoperable with the IIIF Authentication API.
Migrating the National Library of Naples’ Digital Heritage to DSpace-GLAM4Science
Presented at Open Repository 2018, Bozeman, Montana
The National Library of Naples is the third largest library in Italy. In 2007 a digital library system was created in order to enhance the immense cultural heritage stored in its warehouses. Today, after 10 years, the Library chose to move its Digital Library Management System to DSpace-GLAM. DSpace-GLAM is a specific DSpace-CRIS configuration for the description, management, analysis and preservation of digital cultural heritage. The choice of a solution built upon DSpace, the most used open source Digital Asset Management System in the world, supported by a large community and by the Duraspace foundation, is mainly related to sustainability issues.
During the first half of 2018, digital contents will be migrated into the new system. The presentation will illustrate the migration workflow and the expected results.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
top nidhi software solution freedownloadvrstrong314
This presentation emphasizes the importance of data security and legal compliance for Nidhi companies in India. It highlights how online Nidhi software solutions, like Vector Nidhi Software, offer advanced features tailored to these needs. Key aspects include encryption, access controls, and audit trails to ensure data security. The software complies with regulatory guidelines from the MCA and RBI and adheres to Nidhi Rules, 2014. With customizable, user-friendly interfaces and real-time features, these Nidhi software solutions enhance efficiency, support growth, and provide exceptional member services. The presentation concludes with contact information for further inquiries.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns
Unlocking Business Potential: Tailored Technology Solutions by Prosigns
Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support.
Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth.
Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices.
AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making.
Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency.
DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration.
Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly.
Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business.
Join us on a journey of innovation and growth. Let's partner for success with Prosigns.
Enhancing Project Management Efficiency_ Leveraging AI Tools like ChatGPT.pdfJay Das
With the advent of artificial intelligence or AI tools, project management processes are undergoing a transformative shift. By using tools like ChatGPT, and Bard organizations can empower their leaders and managers to plan, execute, and monitor projects more effectively.
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...informapgpstrackings
Keep tabs on your field staff effortlessly with Informap Technology Centre LLC. Real-time tracking, task assignment, and smart features for efficient management. Request a live demo today!
For more details, visit us : https://informapuae.com/field-staff-tracking/
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...Globus
Large Language Models (LLMs) are currently the center of attention in the tech world, particularly for their potential to advance research. In this presentation, we'll explore a straightforward and effective method for quickly initiating inference runs on supercomputers using the vLLM tool with Globus Compute, specifically on the Polaris system at ALCF. We'll begin by briefly discussing the popularity and applications of LLMs in various fields. Following this, we will introduce the vLLM tool, and explain how it integrates with Globus Compute to efficiently manage LLM operations on Polaris. Attendees will learn the practical aspects of setting up and remotely triggering LLMs from local machines, focusing on ease of use and efficiency. This talk is ideal for researchers and practitioners looking to leverage the power of LLMs in their work, offering a clear guide to harnessing supercomputing resources for quick and effective LLM inference.
Innovating Inference - Remote Triggering of Large Language Models on HPC Clus...
DSpace-CRIS technical level introduction
1. DSpace-CRIS @ TUHH
A technical level introduction to the DSpace-CRIS concepts
and the ORCID integration
2. • The DSpace-CRIS data model: additional entities,
interactions with the DSpace data model (authority
framework), enhanced metadata, inverse relations
• ORCID integration & technical details: available
features & use cases (authentication, authorization,
profile claiming, profile synchronization push &
pull, registry lookup), configuration, API-KEY, use of
the sandbox, metadata mapping
• 4Science support: service desk portal
Summary
3. The DSpace-CRIS data model
Additional entities, interactions with the DSpace data model
(authority framework), enhanced metadata, inverse relations,
metrics, statistics
6. • The set of managed entities:
• ResearchOutputs: Publications, Datasets (DSpace ITEM
with “a profile”)
• Researchers, Organisations, Project (1st class citizen
DSpace-CRIS)
• Any other entity: DSpace-CRIS ResearcherObject with “a
profile”
• The relations between them:
• Semantics
• multiplicity
What define a data model?
7. • Communities and collections are entities useful to
aggregate DSpace Items by
• A common profile (metadata)
• Provenience and responsibility (license, workflow,
curation)
• They own the items, are often related to an
organisation by the mean that the community or
collection is maintained by it but are different
conceptually things!
What about communities & collections?
8. DSpace-CRIS doesn’t bind you to a predefined
datamodel. It provides support out-of-box for three
additional entities (researchers, organisations and
projects) but you are not required to use all of them.
you can define additional entities
you can define your own relations between
entities including the ones that you have defined
A flexible data model
13. • It can be performed via UI and exported to xls
• It can be imported from XLS files
Data model configuration
Default configuration
Documentation
14. • Flat metadata model
• All information are stored as string at the database
level with minimal support (and validation) for data
entry in the UI
DSpace-CRIS improves the metadata at the item level
providing:
- Additional input types for data entry (number, year
and regex validation)
- Partial support for nested metadata
Weakness of the DSpace Metadata model
15. New values for the <input-type> element
• year
• year_noinprint shows a In press label stored as 9999
The configuration properties submission.date.min-year
(default 1950) and submission.date.new-years (default 0,
additive from the current year) are used to define the range
• number allows input of only digit values. The form element
use the html5 type number and js to assist the user in the
input. Validation is done on the server side using regex
(default d+)
<validation> can be used to validate the input in onebox,
textarea, number against any regex
Additional input types for data entry
16. A metadata value in dspace has a
• Text-value: the textual value of the
metadata
• Authority: an identifier from an authority
file that uniquely identify the linked
authority term
• Confidence: the level of confidence of the
authority value (-1 unset, 600 certain)
• Place: the order 1-based of the value
• Lang: the iso language code of the
text-value
Authority framework
Only for
configured
metadata
Mostly ignored
17. • It is activated in the dspace.cfg
• Defining the plugin that talk with each authority file
• Defining which metadata (ie. dc.contributor.author uses
which plugin/authority file)
• It is the bridge between DSpace and DSpace-CRIS
objects (DSpace-CRIS is the authority file)
See
https://wiki.duraspace.org/display/DSPACECRIS/Inte
gration+with+the+basic+DSpace+data+model
Authority framework - 2
18. Example: a publication has been fund by two
different grants and we want to store in the
publication metadata the projects names, funders
and grant numbers. This is the scenario from which
dspace-cris is started
Nested metadata: lack of data modelling
Project title#1
Funder: European Commision…
GrantNo: xxxx
Project title#2
Funder: Mellon Foundation…
GrantNo: yyyy
You need a linked entity
DSpace-CRIS: project
authority = pj00001
authority = pj00002
19. Example: a publication have two authors and we
want to store their ORCIDs for retrieval purpose and
affiliations to show the publication in the list of both
departments
Nested metadata: lack of data modelling
Researcher#1
ORCID: 0000-0000-0000-0001
Affiliation: xxxxx
Researcher#2
ORCID: 0000-0000-0000-0002
Affiliation: yyyyy
You need a linked entity
DSpace-CRIS: researcher profile
authority = rp00001
authority = rp00002
20. Example: a publication have two authors and we
want to store their affiliations to record the
attribution expressed by the authors in the
publication header
Nested metadata: a real need – solved in
DSpace-CRIS 5.7
Researcher #1
Researcher #2
Affiliation: xxxxx
Affiliation: yyyyy
You need to store such information because it is not enough to know
the affiliation of a research at a given time to reconstruct. You don’t
know the exact date to use, also when you know it you can have
multiple choices
dc.contributor.affiliation
dc.contributor.author
place = 1
place = 2
21. It can be use also to couple several metadata
Nested metadata: a real need – solved in
DSpace-CRIS 5.7 (2)
Project title #1
Project title #2
Funder: xxxxx
Funder: yyyyy
Nice! we don’t need linked entities anymore!?
NO. This solution doesn’t provide data normalization (same
project could have different description in different items), you
are not able to list all the project with a specific funder, etc.
dc.relation.projectfunder
dc.relation.project
place = 1
place = 2
dc.relation.grantno
grantno: 123
grantno: ABC
22. It is configured in the input-form, a new <parent>
element has been introduced. See
https://wiki.duraspace.org/display/DSPACECRIS/Nested+
metadata+in+DSpace+items
Known limitations:
1. Children metadata supports only the “onetext” input
(limitation to be removed soon)
2. There is not yet support for “coupled” visualization of
these metadata in the item splash page
3. Nested metadata cannot be repeatable but you can
create an arbitrary number of metadata to store
reasonable prelimited-multiple values (affiliation1,
affiliation2, affiliation3)
Nested metadata: a real need – solved in
DSpace-CRIS 5.7 (3)
23. • We don’t embrace a specific metadata schema / format
as many standards are equally valid for different
communities we prefer to support easy crosswalk to all
the needed formats
• Data are stored in typed columns: number, date, string,
reference to other entities – ready for further
characterization of the value (semantics, date-range
validity), not currently implemented in the UI
• Nesting is managed natively with the support for
children objects. No limitation about repeatable nested
metadata
• Data structure is keep in the database instead than in
an external configuration file (input-form) to enforce
data integrity
DSpace-CRIS entities: metadata aka
properties
24. • Each DSpace-CRIS entity instance has a status flag
• Public: the details page is visible to anyone and it will be
linked where appropriate. The record is included in
public search results
• Private: only administrators can access the details page.
The entity is indexed only for use as authority entry
• Each property value has an edit mode:
• Editable
• Visibility flag only
• Only Administrators
• Read only
• A property become visible when included in a
public visible tab/box
DSpace-CRIS visibility and security
This only apply to non-admin users
allowed to edit DSpace-CRIS entities.
Out-of-box only RP supports editing by
non-admin, the RP owner
25. • Visibility of a tab or box can be restricted to
System administrators
Only RP owner
Admins and RP Owner
specific users and groups related to the entity instance
• To restrict the visibility of a box or tab to specific
groups or users one or more properties must be
indicated containing the users and/or groups that
have access to the protected box / tab
• In this way it is possible to make visible a box of a
department only to the department director and
secretary or a project box only to the investigators
DSpace-CRIS visibility and security - 2
26. • DSpace-CRIS objects can be exposed to the DSpace
functionalities as normal DSpace objects with metadata
• Each property is exposed as a metadata with
schema = default value depending on the CRIS entity type
element = shortname of the property
• The value is the string representation of the property value.
For pointer (link to other entities)
• <schema>.<element> has the “display value” of the pointer as value
and the CRIS ID as authority
• <schema>.<element>.<qualifier> is automatically mapped to the
property with shortname = qualifier in the linked dspace-cris entity
• For nested objects (or combo) the qualifier gives access to
the specific property in the nested
• The last two “expansion” mechanisms don’t work for *
wildcard metadata access (crisrp.*.* or crisrp.dept.*)
Addressing dspace-cris entities in the
dspace “way”
27. The schema used are as follow
• ResearcherPage crisrp
• Project crispj
• Organisation crisou
• ResearcherObject cris<shortname> (crisjournal, crisevent,
etc.)
Some examples
• crisrp.fullName is the name of a researcher
• crisrp.dept contains the name of the department as value and
the ID of the CRIS OrgUnit as authority
• crisrp.dept.description is the description of the department
where the researcher is affiliated
• crisrp.affiliation.affiliationorgunit are the organisation listed
in the nested affiliation objects (with value and authority)
Addressing dspace-cris entities in the
dspace “way” - 2
28. • The Item object has been wrapped to add support
for virtual metadata
• The wrapper is defined in the cris-metadata-
enhancers.xml spring file
• Using AOP (intercept calls to getMetadata*
methods) it adds virtual metadata calculated using
logic from a
• CrisItemEnhancer: to expose as crisitem.<alias>
information from linked CRIS entities
• ItemEnhancer: to expose as item.<alias> information
generated from an item metadata
(placeholder.placeholder.placeholder allows the
generation of values regardless of existent metadata)
Exposing dspace-cris info to dspace items
29. Examples include
• use researcher metadata (project, journal, etc.) to
index linked publications
• expose researcher (project, journal, etc.) metadata
over OAI-PMH as item metadata
crisitem.author.dept exposes the mainAffiliation
of the linked researcher profiles
crisitem.project.grantno exposes the
projectNumber recorded in the linked project
(dc.relation)
Exposing dspace-cris info to dspace items
30. • Information from nested objects or linked cris
object are available on cris object only when
directly accessed using the getMetadata (no *
wildcard support)
• In many cases it is needed to access all the
“metadata” of a CRIS object (search, browse, etc.)
• A CrisEnhancher infrastructure is available for that.
It is recommended to use where possible the same
syntax of the natural traversing to expose the
information i.e. crisrp.dept.description etc.
Expose nested cris informations
31. • DSpace-CRIS can use the SOLR indexes to reverse a
relation
• Publications are linked to the researcher profile
• But you can also list the publications under a
specific researcher profile
• Relations are defined in the configuration spring file
cris-relationpreference.xml and characterized by
• A name
• The target entity (a CRIS Entity or a DSpace Item)
• The SOLR query with {0}, {1} placeholders to be replaced
with the CRIS-ID or the uuid of the source CRIS instance
Navigate the inverse relations
32. • Inverse relations can be
• Visualized
• Used to show aggregated statistics (discussed later)
• To be visualized, relations are embedded in
components (see cris-components.xml)
• Components are pluggable JAVA logic to be
executed at the time that a CRIS object is visualized
• They typically provides information (i.e. act a
Controller in the MVC pattern) to be visualized by a
custom JSP fragment (V). Each box can declare to
use a custom JSP
Navigate the inverse relations - 2
33. • Out-of-box are available components
implementations to allow configurable rendering of
inverse relation for each entities (dspace items or
dspace-cris entities)
• It is possible
• to configure which facets show in the component
• to apply filters to the relation
• It is possible to enable a clustering using custom
categories defined by facet queries
• It is aware of the preference expressed for the
relation
Clustering of related objects
34. • An object can be hidden in the list of linked objects
from a CRIS object because it is not “so relevant”
(for instance old publications, old versions or
different edition of the same publication in a
researcher profile)
• An object can be promoted to be part of a selected
(ordered) list of linked objects for a specific CRIS
object (primary publications of a researcher)
• An object could be wrongly linked to a CRIS object
so it should be unlinked by the CRIS object owner
• This actions can be performed using the Manage
relation preference tool
Hidden, unlinked and selected objects
35. • Support to collect metrics information about all the
entities in the system (both dspace objects than
dspace-cris objects). Data are stored in the database
(cris_metrics), other than the ref to the object
• metrictype: A short alias of the metric (scopuscitation, etc.)
• metriccount: The recorded value for the metric (double)
• remark: custom details (JSON String)
• startdate – enddate: observed period
• timestamp[created|modified] Data acquisition time/update
• Scripts to
• automatically capture bibliometrics from Scopus, Web of
Science and PubMed Central
• freeze statistics data from the SOLR core as usage metrics
• calculate derivative metrics (percentile, growth, cumulative)
DSpace-CRIS Metrics framework
36. 5
Rank as percentile compared to
the other objects in the
repository
Grown tracked locally
Metric value (citation number)
linked to an external detail page
when provided
37. org.dspace.app.cris.metrics.[scopus|wos].script.
ScriptRetrieveCitation
• Get citation count for DSpace items that have an
identifier suitable for the provider ( DOI, PMID, EID, UT)
• Cumulate citation and number of items as metric on the
researcher profile
• Work on a configurable number of items, skipping
recent processed items and sleeping between requests
to meet API usage limit
• Can save the provider identifier to the item metadata
• PMC Script has an additional structure to store fine-
grain information about citing item including
mining of cross-reference between DSpace items
DSpace-CRIS Metrics framework - 2
38. • The current value of each metric (last = true) is
exposed as dynamic field crismetrics_<metrictype>
in the SOLR search document for sorting and
projection
• SOLR server accesses the DSpace database using the
credentials configured in the database.properties file
• Data are cached in memory by SOLR and updated
when a new searcher is opened (something write
to the disk), new metrics are collected from the
built-in scripts or a refresh metric cache is manually
trigged
${solr.url}/search/select?q=*:*&fl=clearcache-crismetrics
DSpace-CRIS Metrics framework - 3
39. Internal and derivative metrics are build by
configurable providers defined as spring beans
• usage data from the statistics core (view &
download)
• variation of a metric over predefined period
(_period1, _period2)
• percentile positioning of the object compared to
the other objects in the repository by the metric
value
• many other computed metrics can be configured
reading from an item or cris object metadata
DSpace-CRIS Metrics framework - 4
40.
41. • The absolute link to the detailed statistic page is
stored in the remark of the metric. Pay attention if
you clone existent database
• Last week (_period1) and last month (_period2) are
calculated from the recorded metrics. Need manual
fix if you withdrawn/fix usage data between run
• The cris_metric table grows unlimited a
purge/archive strategy for old/unused data should
be setup
DSpace-CRIS Metrics framework - 4
42. • Served by Spring two configurable controller (one
for DSpace objects one for DSpace-CRIS objects)
• For each entity it is possible to define the statistics
components to show (tabs)
• For instance a collection show
• View of the collection
• View of items in the collection
• Download of items in the collection (view of item’s bitstreams)
• Upload of item in the collection
• For DSpace-CRIS entities the default is to use the same
components used for the visualization
Statistics: DSpace-CRIS enhancements
43. • It uses SOLR Join queries to aggregate statistics of
related objects including bitstream view under a
specific item.
• There are some consequences:
• Use of SOLR shards is not possible as you will need to join
over distributed SOLR cores
• It is unnecessary to rebuild statistics indexes, a very very
expensive operation, if the repository structure change
(merge of collections, change of item metadata, etc.)
• An additional field is stored in the SOLR statistics document
with the unique id of the corresponding object in the search
core (the uuid or the resourcetype-resourceid)
Please note that DSpace-CRIS statistics data remain
compatible with a standard DSpace as they only include
an additional field
Statistics: DSpace-CRIS enhancements
47. • Authority to provide lookup over (a subset of) the
repository items
• Consumer to automatically add the inverse relation
to the target item once the linking item is published
(approved)
Relations between items
48. • 4Science has released, free and open source, an
integration with CKAN, the world's leading open-
source data management platform
• Using an extendible viewer framework you can now
offer data discovery, exploration, preview, sampling
and visualization from your DSpace-CRIS repository
• CKAN makes open webservices for tabular data
available: https://ckan.org/
• DSpace-CRIS & DSpace-CKAN add-on:
https://github.com/4Science/dspace-ckan
DSpace-CRIS use cases: Research Data
53. CKAN Integration Add-On: architecture
backend
proxing
• Open access
• Embargo
• Restricted
Can be integrated
with LTP strategy
Open Source, get it from GitHub!
54. Image files (medical, astrophysics, cultural
heritage: digitalized manuscript, rare books,
etc.) need to be consulted online, discussed
and commented / annotated
IIIF protocols and formats allow you to meet
these requirements in a standard and
understandable way (for both humans and
machine)
DSpace-CRIS use cases: beyond publications
55. • An astrophysics image can be over 5GB!
• High-quality scanned books have images
typically over 100MB for each page
• Medical images can also be very large
• The structure of image sequences are
complex and relevant (page sequences,
evolution of phenomena in medical images,
etc.)
DSpace-CRIS use cases: Images
56. The same requirements apply to audio and
video content
- Streaming
- Internal structure
- Annotation / commenting / transcript
Adopt an open standard: the MPEG-DASH
format allows adaptive streaming over simple
html client with full support for multiple
tracks, ToC, subtitles
DSpace-CRIS use cases: beyond publications
57. • You can add viewers simply implementing the JSPViewer
interface and exposing them as spring beans in your DSpace
Spring context
• You can mark a bitstream to be used with one or more
viewers using the metadata bitstream.viewer.provider. The
metadata value must match the viewer bean id
• You can avoid direct download of the bitstream adding the
value nodownload to the previous metadata
• The UI as been extended to provide edit capabilities for
metadata on all the DSpace objects. You can edit bundle and
bitstream using the button provided in the administrative
edit-item or you can build your own link following the syntax
below
${dspace.url}/tools/edit-dso?resource_id=xxx&resource_type=yyy
(use the uuid parameter in DSpace-CRIS 6.x)
DSpace-CRIS Viewers framework
58. The IIIF Image Viewer, Document Viewer,
OCR & Transcription, Video/Audio Streaming
are add-on modules presently distributed by
4Science with an innovative business model:
contribute to make them open source soon!
http://www.4science.it/en/dspace-add-ons/
DSpace-CRIS add-ons
59. • Versioning was broken in DSpace-CRIS 5.7, it is now
solved in the maintenance and master branches
• The UnityFVG project has a customization that expose
(RP, PJ, OU, Journal) over OAI-PMH in the CERIF XML
format. We have recently take over the project, we are
reviewing the implementation to make it suitable for
general inclusion in DSpace-CRIS
• DSpace-CRIS provides an additional strategy to mint
DOI for items that meet specific conditions in a
controlled, semi-automatic process. It is possible to
specify set of items and associate to each set a different
algorithm to generate the DOI and the metadata to
register (using dedicated schemas for theses, datasets,
etc). It works using a queue processed by batch scripts
(the CrossRef and Datacite agencies are supported)
DSpace-CRIS: other functionalities
60. • System prompts potential duplicate during
submission and workflow
Duplication alert
63. • Two items are flagged as potential matches if they
share at least one signature (this is largely inspired by
the SOLR official de-duplication approach)
• A signature is a value that summarize the information in the
item using a pluggable transformation (case insensitive, ascii
transcription, identifier normalisation, etc)
• Feedback on potential matches (reject or duplicate
flag) are stored in the database table dedup_reject
• Signatures and matched groups are stored on a
dedicated SOLR core that is maintained using
DedupEventConsumer
• Use DedupClient to rebuild the index or build it the first time
if you are migrating from a previous version
Deduplication technical details
64. • Scripts are provided to query periodically the
following bibliographic databases for publication of
the institution
• PubMed Europe
• Scopus
• Web of Science
• Records are mapped to the DSpace internal
metadata schema and queue in the DBMS Border
tables to be imported
• Deduplication can be used to merge records found
in multiple sources or previously entered
Scanning of external databases
66. • Signposting is an approach to make the scholarly
web more friendly to machines, exposing relations
as Typed Links in HTTP Link headers
• The following patterns are supported in DSpace-
CRIS:
• Author: links to authors ORCID or VIAF records
• Identifier: link to ORCID from DSpace-CRIS researcher
pages, link to the Handle/DOI from the landing page or
fulltext (PDF, etc.)
• Publication Boundary: links to the actual fulltext from
the landing page
• See https://wiki.duraspace.org/display/DSPACECRIS/Signposting
New features in DSpace-CRIS 5.7 & 6
67. ORCID integration &
technical details
Available features & use cases (authentication, authorization,
profile claiming, profile synchronization push & pull, registry
lookup); configuration, API-KEY, use of the sandbox, metadata
mapping
68. Login via ORCID iD
also for external
co-authors (if liked)
Lookup the registry
Transfer information from the repository
to the ORCID Registry and viceversa
Connect local profile with the ORCID registry
Create new record - facilitate the creation
of new ORCID records for researchers
69. ORCiD login
By default a new Researcher Profile can be
immediately created capturing information
from ORCID
70. The following options are available
• ORCID Login embedded in the “Password Login”
screen
• ORCID Login offered as an independent
authentication method
• ORCID Login disabled (only connect to ORCID and
claim existent researchers profiles)
config/modules/authentication-oauth.cfg#L85
ORCID login
74. • An ORCIDAuthority plugin allows to search the local
Researchers Profiles and the ORCID Registry
• Results from the two registries are concatenated
without deduplication; use the local entry or the ORCID
entry at the end will lead to the same association
• Entry selected from the ORCID Registry get a temporary
authority key
will be generated::orcid::<orcid-id>
• A DSpace consumer watches for deposited items
transforming all the temporary keys in an actual CRIS
Object. The item will be updated to refer to the real
CRIS-ID
ORCIDAuthority
75. will be generated::<ext-auth>::<ext-id>
• The consumer provides a general infrastructure to
create CRIS objects as part of an item submission that
go beyond the simple ORCID use case
• Depending on the involved external authority a Filler
implementation is invoked and the generated CRIS
object or its metrics are filled with one or more
information extracted from other item metadata or
dynamically retrieved from the authority or any other
custom logic
• ORCIDImportFiller is responsible to PULL biography
data from ORCID when a new ResearcherProfile is
created
Pull information from ORCID
76. Connect existent profiles to ORCiD
From his Researcher Page, via the specific
“tab” ORCiD preferences it is possible to check
and connect the local profile to ORCiD
79. • The system can automatically synchronize changes
from DSpace-CRIS to ORCID (batch mode) or left the
user to manually synchronize one or more changes to
ORCID
• The batch mode requires the execution of a CRON Script
• User that opt for manual synch will receive an email inviting
them to login in the system to check and synchronize
• Sometime a PUT operation is required, this happen
when an item is deleted or withdrawn from the system
or when the user change his preference. This is due to a
limitation of the ORCID v1 API that doesn’t allow to
delete a single publication or project
• Batch mode execute PUT requests by default when
required but this can be prevent.
Synchronization mode
80. Projects or publications preferences
• All projects mean any projects
that is linked to the researcher
page also if not displayed
• Selected projects are only the
projects that were pickup by
the researcher in the
management projects tool
• My projects are all the projects
linked to the researcher except
the ones that were hided
81. Biography preferences
• The researcher choices which
properties can be synch with
ORCID
• Preference properties are prefixed
with orcid-profile-pref- followed
by the name of the source
properties in DSpace-CRIS. The
label is the target property name
in the ORCID model
https://wiki.duraspace.org/display/DSPACECRIS/ORCID+Integration#ORCIDIntegratio
n-MappinglocalpropertiestoORCID
83. • The ORCID queue (cris_orcid_queue table) is populated
using a
• dspace consumer that observe all changes to DSpace Items
(org.dspace.app.cris.integration.authority.CrisOrcidQueueConsumer)
• Hibernate listener that observe all changes to DSpace-CRIS
objects (org.dspace.app.cris.model.listener.OrcidQueueListener)
• The queue is processed by the batch script or by the UI
when the user hit the send button
• The need for a PUT request is a tracked with a special
placeholder
• The cris_orcid_history table contain the response
message and code for any push action to ORCID. The
PUT code assigned to the “generated” object in the
ORCID registry is stored here
ORCID Sync queue & history
84.
85. ORCID Mapping
• Mapping between the Researcher Page properties
and the ORCID profile is implicitly managed by the
biography preference properties configuration
• Mapping from the DSpace Item metadata to the
ORCID Work is done in orcid-work-metadata.properties
• The orcid.citation_crosswalk configuration properties
defines the dissemination crosswalk to use to create the
citation record (BibTeX, etc)
• Mapping from the CRIS Project properties and the
ORCID Funding is done in orcid-funding-metadata.properties
86. • An access token, valid for all the scopes configured
in authentication-oauth.cfg#L71, is obtained when
an user login with ORCID or connect his ORCID
profile
• The access token is stored in the
eperson.orcid.accesstoken of the loggedin EPerson
and copied, for each granted scope, in the following
RP properties (system-orcid-token-authenticate, system-orcid-token-
orcid-profile-read-limited, system-orcid-token-orcid-bio-update, system-orcid-
token-orcid-works-create, system-orcid-token-orcid-works-update, system-orcid-
token-funding-create, system-orcid-token-funding-update)
ORCID Access tokens
88. • If a researcher profile is not linked to a DSpace
EPerson there are two potential way to claim the
profile
• If the profile has an email, you can guess the email
address to get an email with a forget password link and
a new account with such email will be created and
linked to the researcher profile
• If the profile has an ORCID, you can simply login via
ORCID to prove that you are the owner of the profile
• Automatic claiming of existent profiles is performed
by the system at login time using the ORCID ID and
the email address as a “post login action”
Claim a researcher profile
89. External identifiers can be used to directly address the profile page
without knowing the internal CRIS identifier
/cris/rp/details.htm?lt=orcid&lv=0000-0002-2312-0318
Any type of identifier is allowed (including the ones created locally
by the institution – e.g.: staff #)
/cris/rp/details.htm?lt=<ext_id>&lv=<ext_value>
This permits an easy and direct integration with other
institutional sites (staff directory, etc.)
90. • DSpace-CRIS doesn’t use the SOLR Authority index.
Generally speaking the DynamicObject offer a much
complete solution to manage any other local or locally
cached authority but technically, once enabled, nothing
prevent to use the SOLR Authority Index if needed.
• ORCID and AccessToken available in the EPerson
metadata as eperson.orcid and
eperson.orcid.accesstoken are automatically reused
during RP creation to PULL richer information from
ORCID
• Via API is it possible to fill a ResearcherProfile from a
specific ORCID supplying an accesstoken (or the public
access)
Additional questions on the ORCID
integration
91. • Public or Member API?
• Public: login, claim, search of ORCID registry, pull of
public information during researcher profile creation
• Member API: write to the ORCID registry, access to
limited information on single researcher
• Production or sandbox environment?
• Sandbox: you can test member API also if you are not
yet a member, including Premium services (webhooks
reserved to national agreements – not used by DSpace-
CRIS so far). You can create multiple “user” accounts to
facilitate testing
• Production: you can conduct limited test involving
volunteer real users
Configuration of the ORCID API-KEY
92. All is set in the authentication-oaut.cfg (via build.properties /
local.cfg)
• API endpoints
• orcid-api-url
• application-authorize-url
• application-token-url
• Authorized Scopes (application-client-scope)
• /authenticate /orcid-profile/read-limited /orcid-bio/update /orcid-works/create /orcid-
works/update /funding/create /funding/update /activities/update
• Client credentials
• application-client-id
• application-client-secret
• application-redirect-uri (you can use fake hosts entry to simulate
production URL)
• application-client-name (only required for v1.2)
Environment configuration