Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Improving performance / scalability in general
  • Enabling Configurable Entities (by default)
    • What do we need to achieve to enable Entities by default?
    • How can entities be made more usable?
    • Improving scalability/performance/functionality of Relationships
    • Nested/hierarchical metadata  (e.g. dates on a Person's affiliation with an OrgUnit)
    • If entities are enabled by default how could a migration look like? Shall we offer a script to add a field dspace.entity.type="Publication" to all items without an entity type? 
  • Convert a Relationship to a DSpaceObject - it will benefit of all the DSpaceObject has to offer, like: metadata, resource policies
  • Easier Installation and Upgrades
  • Modularization
  • Code Cleanup / Maintenance
    • Dependency upgrades: Upgrade to Angular 18 & Spring Boot 3.3
    Bitstream persistence URLs - As of DSpace 7, there are no persistent URLs for bitstreams. The URL is based on UUID, and if you replace or version a bitstream the URL will change: https://github.com/DSpace/DSpace/issues/9083Associate forms to collections in the UI -
    • All collections should have a workflow – a default noninteractive workflow would facilitate applying curation tasks (such as virus scanning) to all submissions:  https://github.com/DSpace/
    dspace-angular3194
  • Permissions
    • Possibility of granting granular permission to individuals and groups to edit / see only some metadata
    • 8820
    • Shall we automatically change metadata in flyway migrations?
  • Enabling Configurable Entities by default (Potential alignment with DSpace-CRIS?)
    • What do we need to achieve to enable Entities by default?
    • How can entities be made more usable?
    • Improving scalability/performance/functionality of Relationships
    • Basic Nested/hierarchical metadata  (e.g. dates on a Person's affiliation with an OrgUnit). Related also to https://github.com/DSpace/DSpace/issues/9736
    • If entities are enabled by default how could a migration look like? Shall we offer a script to add a field dspace.entity.type="Publication" to all items without an entity type? 
    • Convert a Relationship to a DSpaceObject - it will benefit of all the DSpaceObject has to offer, like: metadata, resource policies
  • ModularizationAll collections should have a workflow – a default noninteractive workflow would facilitate applying curation tasks (such as virus scanning) to all submissions:  
    • Angular : library-based architecture proposal - As of 8.0, we've already migrated to "standalone components". We can now consider whether to potentially migrate to using Nx.
    • Do we need a UI/UX guide to enable module developer to achieve a common "DSpace" look and feel?
    DSpace8820
  • Enhanced Statistics for DSpace (volunteer: Paulo Graça )
    • Paulo volunteered to perhaps start an interest group / working group around Statistics enhancements as his organization is interested in enhancing this for DSpace.
  • Features which existed in DSpace 6 (and earlier)
  • Administrative User Interface enhancements/improvements UX/UI
  • Results of DCAT UX Project Team Testing 

Priorities for 9.0

To be decided.  9.0 is still in very early planning phase. Priorities have not yet been established.

...