Page History

• Lucene and old DB browse system are already deprecated. Just need removal. DB Browse is being removed by Services API
  

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2160

• We have two ways of managing embargos, when we only need one
  

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2588

• Move Elasticsearch Usage Statistics to external "module"?
• May be dependent on finding a better way to support optional add-ons/modules (which is on the RoadMap, but is unlikely to happen in time for 6.0)

• See the wiki page: DSpace Service based api
• Codebase is in this branch: https://github.com/KevinVdV/DSpace/tree/dspace-service-api
• The dspace-api refactor is essentially complete (just a few outstanding Unit Tests).  But additional support will be needed to refactor/fix the various other modules to properly utilize the newly refactored API
• If this is generally approved, @mire has promised to develop even more documentation & training materials to allow other developers to get up to speed quickly.
• Note: this work also looks like it will resolve the following tickets as "byproducts" of the refactor:

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2188

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1782

  • Allows for support of additional Database types (e.g. MySQL) via Hibernate. This comes up as an occasional request
  • Begins the development of a true "Business Logic Layer" (an often discussed topic in DSpace Developer Meetings)

A refactor of the Bitstream Storage Manager to allow different implementations for file/bitstream storage. The primary motivation is leverage a cloud service, such as Amazon S3, which offers easy management, infinite scalability, and low pricing. Other storage implementations could be built off of this work. This follows the DSpace 2.0 goal of having a Pluggable Assetstore.

There was some discussion about the Item Level Versioning since it was introduced. This let to disable it by default (

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1348

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1349

  (at least for JSPUI)

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1814

  (for JSPUI again)

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2490

• Jira
  server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2497

 Pubmed integration into XMLUI submission

Extensible Control Panel

(Would also need a resolution to 

Tim Donohue

As LNI is not in wide use anymore, and it was disabled by default in 5.0, it probably would be best to migrate it to a separate GitHub Project. Anyone who wishes to still use LNI can still install it separately. But, it would no longer be provided out-of-the-box.