Versions Compared

Old Version 40

changes.mady.by.user Jonathan Markow

Saved on

compared with

New Version 41

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

  • Action 5A: Improve and simplify the installation experience for DSpace. This may include, but is not limited to...
    • Investigate download, packaging and installation tools for Java web applications to make it easier to build a working system. (What do similar systems use?)
    • Examine options for lightweight installation, with most configuration taking place from the web interface upon first use (see for example WordPress, etc)
  • Action 5B: Improve and assist with the upgrade experience for DSpace, especially in terms of simplifying the management of local customizations (branding, custom themes, etc). This may include, but is not limited to...
    • Investigate options to assist with upgrades (for example highlighting changes from core code or configurations)
  • Action 5C: Make configuration and basic theming an easier experience for hosted or low-cost deployments by migrating most options to the administrative interface. Some examples include..
    • Move configuration of basic theme configuration options (colours, logo) into administrative interface;
    • Allow most configurations to be edited (and refreshed) from the administrative interface
  • Action 5D: Ensure data is never solely stored in "transient" technologies (e.g. Solr indexes or other such indexes) where it could be accidentally corrupted or lost. All DSpace data should be stored in a stable, persistent data storage system (e.g. database, filesystem), and then indexed from that location into tools like Solr, etc.
  • Action 5E: Provide recommendations around scaling and load-balancing large DSpace instances.
  • Action 5F: Provide administrators with additional system reporting features within the UI. Example use cases may include..Action 5F: Consider developing a Simple Asset Store as the default asset store that uses a more logical naming structure for human traversal;
    • Alert administrators when new upgrades are available
    • Alert administrators when common system issues or misconfigurations are encountered (e.g. "Solr is not accessible / working", "assetstore is unavailable / unattached", "space in assetstore is low");

Move to Use Cases: