Page History

...

Assigned: Richard Rodgers

[summary of goal]   DSpace can be extended. Easy API, etc  There will obviously be limitations to what DSpace can and should do, so we need to have ways to support plugins/addons/extensions to that core functionality. Not all users of DSpace will need to achieve the same set of Use Cases, so we will need to define which are "core" and which would be better implemented as plugins/extensions (either centrally supported or third-party supported).

• Action 3A: (Streamline the core functionality, and provide a better "plugin" model for third-party plugins)
• Action 3B:

...

• Action 5A: Investigate download, packaging, and installation tools for Java web applications to make it easier to build a working system; What do comparator systems use?
• Action 5B: Examine options for lightweight installation with setup tasks such as database population undertaken via the web interface upon first use, and creation of initial admin account;
• Action 5C: Move configuration of basic theme configuration options (colours, logo) into administrative interface;
• Action 5D: Move most configuration into the database, so that it can be updated via the administration screens;
• Action 5E: Document options for scaling and load-balancing DSpace;
• Action 5F: Consider developing a Simple Asset Store as the default asset store that uses a more logical naming structure for human traversal;
• Action 5G: Create a health check tool that can report on issues, of potential future issues (e.g. low disk space);
• 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)