Page History

DSpace currently maintains two user interfaces in parallel (JSPUI and XMLUI). To replace these two user interfaces, we are building a new, single, out-of-the-box user interface on Angular.io.

• Introducing the New DSpace User Interface (at OR16)
• DSpace UI Prototype Challenge
• Design - Single UI Project

For reference:

• End User Use Cases
• Admin UI Use Cases

Also see: DSpace 7 UI Project Plain Language Summary

DSpace's current REST API, while functional, is limited in features and does not follow current best practices for RESTful APIs.

To support the new, single user interface (on Angular.io), we are building / designing a new REST API that follows modern best practices such as: HATEOAS, ALPS, and using the HAL response format.

The new REST API is being built using Spring technologies (Boot, MVC, and HATEOAS).

Goal 3: Can be "extended"

and

Goal 4: Integration with external services

New REST Contract (work in progress):

• https://github.com/DSpace/Rest7Contract

• Remove Elasticsearch Usage Statistics, see DS-3455
• Disable/Remove Legacy (log based) Statistics, see DS-3454

• Dependent on / related to "Single User Interface"

DSpace needs a clear definition of what constitutes a "DSpace module", so that third-parties can create, maintain and distribute their own "modules" as add-ons to DSpace, and distribute them via a public "registry".

• Design - Module Framework and Registry

The DSpace deposit process should integrate more closely with external data sources, in order to automatically populate (or suggest) data on deposit. We should also investigate whether some integrations may allow opportunities for Administrator's to autopopulate DSpace from trusted, external content sources.

• Design - Lower effort to deposit

Goal 1: Fundamentals of IR

Goal 4: Integration with external services

• Integrations - Integrations that significantly lower the effort to fill DSpace with content, both from in house systems and third party content
• Integrations - Linking to other data sources search for available data
• Integrations - Importing data from discipline-specific systems into DSpace
• End User - Email Deposit of bitstream for automatically captured metadata

• Structure - Support for hierarchical metadata formats (e.g. METS / MODS)

DSpace should support defining relationships between objects (especially at the Item and Bitstream level). Some object relationships may be definable via metadata, but should be respected by the DSpace UI.  But, in other situations, it may also necessitate the creation of new types of Objects (e.g. Author objects as Authors of an Item rather than simply textual metadata)

• Primary use case description: Structure - Relationships between objects
• This feature should also investigate whether there are opportunities to better integrate or utilize the new RDF-based interface to describe / define object relationships within DSpace.

• Structure - Relationships between objects
• Structure - Apply licenses to bitstreams

DSpace's required hierarchy of Communities and Collections should be replaced with a more flexible module of supporting Collections & Sub-Collections.

• Design - Simplify Community and Collection Hierarchy
• Also see alignment with PCDM, which simply has hierarchical Collections

• Structure - Community and Collection hierarchy (or generic containers)

• Primary use case description: Basic Statistics (and all child pages)
• This would likely be depending on the "Single User Interface" project for much of the enhancements, as many of these reports are UI related.

• Stats/Metrics - Basic Statistics (and all child pages)

• See linked use cases for more details of possible enhancements to existing basic preservation functionality

• Admin UI - Basic Preservation - Fixity Checking
• Admin UI - Basic Preservation - Format identification
• Admin UI - Basic Preservation - Format validation
• Admin UI - Format reporting

• Dependent on / related to "Single User Interface"
• Primary use case description: Easy and Intuitive Deposit Interface
• May need further definition around what sorts of changes will make deposit easier?

Goal 1: Fundamentals of IR