Key

This line was added.

This line was removed.

Formatting was changed.

Version number of the DSpace-CRIS module will platform refers to the DSpace version against which it is buildbuilt. Support of all DSpace version versions accepted by the Community is provided. The first open source release of DSpace-CRIS was based on DSpace 1.8.2. Current release is DSpace-CRIS based on DSpace 5.5, DSpace-CRIS on DSpace 4.3 and DSpace 3.2 are still also available. DSpace-CRIS 6 is about to be released.

Below is a live detailed release plan that covers all the known features that will be contributed by 4Science or other community members that would like to be involved in projects supporting the enhancement of this open-source extension

Future plan

1st Quarter Semester 2017

DSpace-CRIS 6.x as stable branch

Work on REST webservice toward DSpace-CRIS 7 (angularjs2 Angularjs2 based)start, test site already available at http://dspace7.4science.it/)

Depending on result results from specific projects (not yet confirmed)

2016

The release includes the security fixes already available in DSpace JSPUI 5.6, making it easier to upgrade from a recent DSpace version to DSpace-CRIS (no more need to run sql scripts manuallyscripts manually) and brings a lot of new and exciting features:

UI Extendibility: the webapp can now use the servlet 3.0 specification, enabling the creation and plug-in of external modules with their specific web UI components and pages. An extension point has been introduced to plugin viewers dedicated to particular bitstreams.

Edit metadata for any DSpace Object via the UI: it is now possible to edit/add/remove metadata for Communities, Collections, Bundles and Bitstreams, to simplify the management of further functionalities based on custom metadata.

Edit archived Items with UI submission: administrators can now edit archived or withdrawn items using the same UI available for submissions, exploiting functionalities such as dropdown, autocomplete, ORCID lookup, validation, etc.

Deduplication tools (detect & merge): this administrative tool allows to check the database for potential duplicates and to merge the confirmed matches. During the submission, an alert is shown when a potential duplicate is detected. More information and screenshots available here https://wiki.duraspace.org/display/DSPACECRIS/deduplication+alert

Improved ORCiD synchronization: DSpace-CRIS now stores the internal identifier assigned by ORCiD to the publications in order to prevent record duplications when a local DSpace-CRIS update is pushed to ORCID ("put" code). In addition to that, DSpace-CRIS is now able to push to the ORCiD profiles educational and professional information of the researcher.

Improved submission forms: among the new functionalities we can list the regex validation support, a framework for complex validation support, new input type “number” for submission and new input type “year” for submission.

Improved security model for CRIS entities: every single CRIS object, object tab and object box can now be configured to be visible to specific users or user groups. An example of this would be when parts of a specific project description (such as costs) can be linked to the project participants, or the department director, or the research/contract office, etc.

Automatic calculation of derived metrics: examples are average, maximum, minimum, variance of publication citation counts shown as metrics at the level of researcher, organization, project, and so on.

Advanced import framework: border tables have been introduced to easily create ETL procedures to load and synchronize data, currently limited to publication, in the DSpace-CRIS installation.

On-demand DOI registration: an administrative UI allows to register DOIs via DataCite or CrossRef for items matching configured criteria (theses, dataset, etc.). For each group it is possible to define the template used to generate the DOI and the metadata to deposit. The precalculated DOI can be revised by the administrator to allow complete personalization.

Template service: the template item now supports the use of substitution variables bound to dynamic code plugged in as spring bean. The functionality allows the generation of default values dynamically generated in submission such as the timestamp, the details of the submitter, and so on.

Creation of CRIS objects as part of the submission process: it allows users to create new CRIS objects (persons, projects, organizations, events, etc.) on demand as needed during the submission of a DSpace item. It can be even used to provide a workflow around the collection of data, including metrics, about CRIS entities.

As first implementation of the UI Extendibility we provide native support in DSpace-CRIS of the DSpace-CKAN Integration module (https://github.com/4Science/dspace-ckan). DSpace-CKAN allows an in-depth integration between DSpace and CKAN. Tabular data (CSV, XLS, etc.) are deposited in a CKAN instance through a curation task. The preview of the dataset content is enabled proxing in DSpace the CKAN Datastore API so to enforce the access condition defined in DSpace (Open Access, embargo, etc.). The dataset preview allows filtering, pagination and sorting, all the operation are performed on server side to save bandwidth overload. An example is visible here: https://dspace-cris.4science.it/handle/123456789/31

Facets for dynamic components: publications list, projects list and any other dynamic component included in the researcher profiles or in other CRIS entity details page (project, organization, etc.) can now provide faceting capabilitieshttp://demo-dspace-cris.cineca.it/cris/rp/rp00006

Bibliographic export for publications: researcher's publication list can be exported in several format by the profile owner and search results can be exported by the repository administrators

Incremental Authority from previous value: to suggest terms from values already added into the system to keep metadata clean and to avoid misspelling. Common use cases include keywords, publishers, etc.

There is now a general infrastructure to support metrics about any DSpace/DSpace-CRIS objects, such as traditional bibliometrics for publications, authors, journals, alternative and local metrics.

DSpace-CRIS is now integrated out-of-box with Scopus, Web Of Science, and PubMed Central to collect, show and process citation data. The AltMetrics badge can be shown beside the other metrics.

For any defined metric DSpace-CRIS allows for calculating objects’ local ranking and percentile in order to provide the “most cited” component to different web pages (the home page or any other specific Department/Office pages).

Internal statistics have been elaborated as usage metrics to make them available for “Most viewed”, “Most downloaded” components and to calculate local percentile.

Metrics data can now be exposed in “listing” to make browsing and searching easier, and they can also be used as sorting criteria. This is done by extending the SOLR capability to load additional information from an external source. This feature enables future improvements such as support for “user rated content” to DSpace.

Another important new development is the ability to load and update CRIS’ objects into the system using XLS file, a similar approach to what is actually supported by DSpace for standard items. The feature allows a user to set any kind of field, including the relations between different objects (such as org.unit and researchers, projects and researchers, etc.), and custom fields.

The data model configuration has been simplified, indeed it is now possible to easily export and import the configuration also using XLS files.

There is now a better integration between DSpace-CRIS and ORCID. When a researcher creates her profile in the local DSpace-CRIS, the system automatically collects all the biographic information (such as biography, additional names, external URLs, additional identifiers) from ORCID, both when the researcher directly accesses the system, as well as when a new publication is added to the system that the researcher is co-authoring.

Additionally, the new version has improved the layout and navigation experience: the navigation menu invites the user to explore the repository contents by “Entity”, offering the appropriate tools for each specific type of content such as dedicated browse indexes, advanced search options and components to highlight recent or featured content.