Page History
...
| Advanced Tables - Table Plus | |||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||
Candidate Features for DSpace 7.0 - Priority 1An update on the DSpace 7 work was presented as part of the DuraSpace "hot topics" webinar series: The DSpace 7.0 release is under development and the latest status can be found at DSpace Release 7.0 Status. The below candidate features are ordered in terms of importance to the 7.0 release. As such, the goal is to achieve each feature in the order that they appear (and not all features are guaranteed to be completed in time for 7.0). However, if you or your institution would like to drive or lead the development of a specific feature, you are welcome to volunteer your time towards any of the candidate features listed, no matter where that feature ranks in the listing. For larger features/contributions, we recommend first forming a Working Group (anyone can chair or form a Working Group) to allow other institutions to contribute to your initiative\ Info | | ||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||
| Info | |||||||||||||||||||||||||||||||
|
| Priority 1 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use Cases | Work in Progress | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DSpace currently maintains two user interfaces in parallel (JSPUI and XMLUI). We want to "converge" on a single, out-of-the-box user interface for DSpace. | Goal 2: Lean and flexible | x | High | For reference: | and | |||||||||||||||||||||||||
| DSpace should support the modification of most configurations/settings from the Administrative User Interface, instead of requiring such configurations be tweaked from command line.
| Goal 5: Low cost, "just works" | x | High |
| ||||||||||||||||||||||||||
| DSpace currently has three built-in statistical engines, one based on Apache Solr (default), another based on Elasticsearch (optional), and a third Legacy statistics (which parses logs). DSpace should only provide one out-of-the-box, built-in statistical engine (Solr Statistics), and all others should be removed (and as necessary, their features merged into one).
| Goal 2: Lean and flexible | x | Medium | |||||||||||||||||||||||||||
| 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". | Goal 3: Can be "extended" | x | High | |||||||||||||||||||||||||||
| DSpace's required hierarchy of Communities and Collections should be replaced with a more flexible module of supporting Collections & Sub-Collections.
| Goal 2: Lean and flexible | x | High | |||||||||||||||||||||||||||
| 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. | Goal 1: Fundamentals of IR Goal 4: Integration with external services | x | Medium |
|
Short Term - Priority 2
As "priority 2" features, these features are not guaranteed for the next DSpace release, but are still seen as a priority in an upcoming release. Nonetheless, we'd encourage community members to volunteer to help achieve any of these features. If there is community interest in moving one or more of these features forward, that feature may be moved up to "priority 1" for the next release. These features are ordered in terms of importance, but are all considered to be lower importance than the "priority 1" features listed above.
| Priority 2 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use Cases | Work in Progress | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DSpace should support hierarchical metadata formats (e.g. MODS) | Goal 1: Fundamentals of IR | x | High | |||||||||||||||||||||||||||
| 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)
| Goal 1: Fundamentals of IR | x | High | |||||||||||||||||||||||||||
| DSpace's existing Statistical Reporting user interfaces are rudimentary and do not provide enough useful views/reports/exports of the underlying captured data. These should be enhanced based on modern use cases/needs.
| Goal 1: Fundamentals of IR | x | Medium |
| ||||||||||||||||||||||||||
| DSpace's existing basic preservation functions (format identification, checksum verification, etc) could use enhancement based on modern tools and services.
| Goal 1: Fundamentals of IR | x | Medium | |||||||||||||||||||||||||||
| DSpace's deposit interface could use enhancement for a better overall user experience with regards to usability and accessibility.
| Goal 1: Fundamentals of IR | x | Medium |
|
...
Overview
Content Tools