Comparison: DSpace 7.x versus DSpace 6.x
This document is intended to provide a high-level comparison of certain features in the DSpace 7 User Interface with DSpace 6, and briefly note several new features in DSpace 7.
EXISTING DSPACE 6 FEATURES
Feature | DSpace 6.3-snapshot (currently hosted version) | DSpace 7.x |
Administrative Menu |
|
|
Single Item Submission |
|
|
Batch metadata editing |
|
|
Batch ingest |
|
|
Homepage |
|
|
Footer |
|
|
Editing items |
|
|
Metadata and format registries |
|
|
Curation Tasks |
|
|
Administrative search / Access to Withdrawn or Private Items | In DSpace 6, a Repository Administrator can search for items in several different places in the admin menu under Content Administration:
| DSpace 7 combines administrative Item Search with access to withdrawn and private items in a single user interface called “Admin Search.” Repository Administrators can use this interface to search across the repository, or within specific Collections, and perform actions on them (including withdrawing, deleting, or making private). The interface includes filters that allow you to drill down into search results by access status (e.g. Withdrawn, Private), author, subject, date, and whether the item has files.
Resource: DSpace 7 Administrative Search Lightning Tutorial by Atmire |
Statistics |
|
|
Creation of Communities and Collections |
|
|
Creating a collection |
|
|
Facets |
|
|
Simple Item View | File descriptions (if included in metadata) appear in the simple item view in place of file names. | As of DSpace 7.6, file descriptions do not appear in the simple item view, only file names. This may change in a future DSpace 7 release. |
|
|
|
NEW FEATURES IN DSPACE 7
IIIF SUPPORT
DSpace 7 supports IIIF with the Mirador viewer, and TDL has installed a IIIF server with the demo instance.
The IIIF viewer must be enabled at the item level. To do that, you must add the metadata field “dspace.iiif.enabled” to the item metadata with the value “true.”
IMPERSONATING A USER
A Repository Administrator can log in as any other user and take action (including viewing their workflow queue) as that user.
This feature was available in DSpace 6, but not enabled in TDL-hosted repositories. It will not be configured by default but can be requested via a Helpdesk ticket.
CONFIGURABLE ENTITIES
DSpace 7 includes a Configurable Entities object model, which allows for the creation of new item types, and storing relationships between Items. This feature will allow for tighter integration with external identifier systems (e.g. ORCID), current research information systems (CRIS), journal publishing systems, etc.
To understand Configurable Entities, it’s helpful to understand the DSpace Data Model (i.e. the way data is organized in DSpace):
Each DSpace site is divided into Communities, which can be further divided into Sub-communities reflecting the typical university structure of college, department, research center, or laboratory. Communities (or sub-communities) contain Collections, which are groupings of related content. Each Collection is composed of Items, which are the basic archival elements of the archive. The “Item” element is comprised of one or more files, descriptive and other metadata, a license, and can have a unique identifier (e.g. a handle or DOI).
In DSpace 6 (and previous versions)
The ITEM element is a generic entity. It is intended as a catch-all container for articles/images/papers or anything else you might archive in the repository. You cannot configure the structure of an item to do anything special, and it can’t be connected to other items in the repository, at least not through machine-readable means.
These generic Items are organized in Collections in DSpace.
In DSpace 7 (and beyond)
Different types of items, other than the generic Item can be configured. The configuration of “typed” items is what is meant by Configurable Entities.
For example: In addition to the generic Item entity, you might configure a PERSON entity type, a PROJECT entity type, a PUBLICATION entity type, etc. Each entity type can have its own descriptive metadata fields, identifier, etc. And machine-readable relationships can then be created between these “typed” items.
Just as in DSpace 6, items are organized within Collections. So PERSON items must be stored in a Collection configured to hold PERSON items.
DSpace 7 comes out-of-the-box with a few Entity types: PERSON, PUBLICATION, PROJECT and ORGANIZATIONAL UNIT.
To create a Collection for PERSON (or other type) items, a Repository Manager would create a Collection and then notify TDL that they wish the Collection to be configured for PERSON entities. When configured accordingly, the submission form for items that go into that Collection will include fields appropriate for a PERSON entity. Additionally, the fields in the submission form can be customized to your needs.
There are some limitations to how useful Configurable Entities can be immediately for repositories with existing content.
Existing Items from a DSpace 6 repository cannot easily or automatically be converted to “typed” Items at this time.
Generic items (i.e. all the items that currently are archived in your repository) cannot be linked to “typed” items.