Page tree
Skip to end of metadata
Go to start of metadata


Scope

The rising strategic importance of Current Research Information Systems (CRISs) and Institutional Repositories (IRs) for higher education and research institutions relates to the need to foster research and innovation and to provide a faster and broader technology transfer to industry and society.” (http://www.eunis.org/wp-content/uploads/2016/03/cris-report-ED.pdf)

... the researcher discovers that there is a large benefit (automated CV, bibliography, project participation list, institutional web page generation, part-completion of research proposals etc.) for a relatively small input effort since most input is automated or only required once and used many times”. (http://www.eurocris.org/why-does-one-need-cris)

In order to integrate IRs with CRIS,  we need more accurate information which would result in to provide metrics, reports, develop integrations and services. The only way that allows to relate different objects in the information space is using identifiers, as recognized by the scientific community. According to the conclusions of the COAR Working Group of Next Generation Repositories and the new OpenAIRE Guidelines (version 4), the use of identifiers, with common guidelines, are mandatory on the new generation of repositories.   

Each identified entity (Author, Project, Publication, ...) is managed and identifiable by an unique identifier. We consider Entity concept as an extension to DSpaceObject.

After some meetings with Tim Donohue and Andrea Bollini, and considering that this concept already exists within DSpace-CRIS, it was possible to identify two scenarios:

  • Top / Down scenario - Using DSpace-CRIS as a starting point, and add/remove and/or improve existing functionalities;

  • Bottom / Up scenario - Prepare DSpace core to be extendable and integrate/prepare  DSpace to support these new functionalities (like plugins)


It is expected that the work of this group will be completed within a ten-to-twelve week timespan.


Objectives

  • Create awareness on the need to manage entities and their relations in IR software

  • Propose a solution to enable DSpace to support, manage and relate entities;

  • Specify the global architecture and requirements needed to implement the solution in DSpace (possibly v7);

  • Propose a roadmap to implement the proposed solution.

In order to achieve these objectives, the working group should carefully consider the following:

  • Impact on DSpace roadmap (especially v7);

  • Solution’s flexibility;

  • Community involvement.

Deliverables

  • Requirements list for DSpace;

  • Technical model of the solution;

  • Webpage on DSpace wiki describing of this feature;

  • Implementation roadmap proposal. 

Members

4Science

Atmire

Duraspace

RCAAP

Next Meeting

  • TBA (it's going to be rescheduled)

Meeting Agenda

  • DSpace-CRIS hands-on (locally installed, review/discuss personal experiments)

    • The default data model of DSpace-CRIS is defined in this excel file: configuration-tool-demo.xls loaded in the system at the end of the installation process, see Installation#TheDSpace-CRISsampleconfiguration
    • Some documentation about the use of the excel file to change/create the data model is available here: configure the data model using an Excel file (please note that you can import/export the data model at any time combining changes done via the UI with changes done on the excel file. The excel file only add new configuration, to remove entities and attributes you need to use the UI and migrate by hand existent data.

Meeting Notes

  • No labels