Versions Compared

Old Version 17

changes.mady.by.user Stuart Lewis

Saved on

compared with

New Version 18

changes.mady.by.user Bram Luyten (Atmire)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: moving 5I to 4F

...

  • Action 4A: Metadata ingest from external services (complete records/items)

  • Action 4B: Consuming external authority control sources for enriching DSpace item metadata

  • Action 4C: Exposing metadata and content to external services

  • Action 4D: Exposing usage statistics to external services

  • Action 4E: Integration with Authentication and Single Sign on services

  • Action 4F: Integration with external services providing identifiers (handle, datacite, ...)

To integrate with parallel projects and initiatives (fedora, hydra, islandora) we first need to pin down the use cases of what those integrations will bring to DSpace, or what these will bring to the other platforms. They currently do not fit immediately in any of these five areas.

...

  • 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: Easier setup tool for CNRI handles;Action 5J: Create alerting tool for new upgrades to alert administrators within the admin user interface;
  • Action 5K5J: Investigate options to assist with upgrades (for example highlighting changes from core code or configurations)

...