Page History

...

DSpace should be easy to install without requiring Java development expertise, to configure without requiring server access, and to monitor from within the application. Basic configuration options, including the look and feel and selecting themes should be accessible from within the DSpace online administration area.

• 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
  comparator
  • similar systems use?)
  Action 5B:
  • Examine options for lightweight installation
  with setup tasks such as database population undertaken via
  • , with most configuration taking place from the web interface upon first use (see for example WordPress,
  and creation of initial admin account;
  • 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..Action 5C:
  • 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: Move most configuration into the database, so that it can be updated via the administration screens;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 Action 5E: Document options for scaling and load-balancing large DSpace ;instances.
  • Action 5F: Consider developing a Simple Asset Store as the default asset store that uses a more logical naming structure for human traversal;Provide administrators with additional system reporting features within the UI. Example use cases may include..
    • Alert administrators when new upgrades are available
    • Alert administrators when common system issues or misconfigurations are encountered
    Action 5G: DSpace should have an understanding of its requirements and dependencies and report on issues
    • (e.g. "
    solr webapp
    • Solr is not accessible / working
    ");
    • ", "assetstore is unavailable / unattached", "space in assetstore is low");

  Move to Use Cases:

  • Action 5F: Consider developing a Simple Asset Store as the default asset store that uses a more logical naming structure for human traversal;
  • Action 5H: Ensure no data is stored in transient technologies (for example solr statistics do not have persistent storage and can be easily lost or corrupted);
  • Action 5I: Create alerting tool for new upgrades to alert administrators within the admin user interface;
  • Action 5J: Investigate options to assist with upgrades (for example highlighting changes from core code or configurations