Page History

...

• Improving performance / scalability in general
  • High CPU usage for server-side rendering, https://github.com/DSpace/dspace-angular/issues/3110
  • Serve configuration more efficiently: https://github.com/DSpace/DSpace/issues/9056
  • User permissions should be obtained in fewer requests: https://github.com/DSpace/dspace-angular/issues/3161
• 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? 
• Easier Installation and Upgrades - Can we simplify the installation/upgrade process of DSpace, especially now that there's a frontend & backend to manage?
• Modularization
  • 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.
• 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/9083
• Replace Submission Form library (as the one we use is unmaintained): https://github.com/DSpace/dspace-angular/issues/2216
• Permissions
  • Possibility of granting granular permission to individuals and groups to edit / see only some metadata
• Shall we automatically change metadata in flyway migrations?
  •  DOIs
    • Changing the field a DOI is using (dc.identifier.uri vs. dc.identifier.doi)
    • Changing the resolver (https://doi.org vs. http://dx.doi.org)

...