Page History

...

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

  In the Developers Meeting on Jan 30, 2013, those in attendance discussed a need to release an updated version of this "Metadata for All" pull request (#12).  However, we may need the following:
  
  • An updated version of the pull request based on current "master"
  • We like the suggestion to rename "schemas" to "namespaces"
  • We'd like it to use "metadatavalue" (and similar) tables rather than creating a new set of Metadata tables specific to other objects.   We understand this may be more disruptive, but it seems odd to have different metadata namespaces
  • If possible we'd want this change to be "backwards compatible" with existing UIs. The goal would be to perform this change in stages – first update the APIs to allow for metadata on all objects, then update each UI one-by-one.  Hopefully we can get all of the UIs done before 5.0
  • We also obviously could use some basic documentation / overview of the thinking behind it, so that we can vote this through sooner rather than later.
• REST API updates
• Audio/Video Streaming (RTMP, HLS, DASH) Support
• Replace Authentication and Authorization code in DSpace with a 3rd-party framework 

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

  (University of Missouri - @mire)

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

   (The World Bank - @mire)
  

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

   (The World Bank - @mire)
  

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

   (@mire)
  

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

   (pbecker)

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

   (Longsight)
  
  • The admin can batch import items through a ZIP file through the UI (XMLUI), that contains SimpleArchiveFormat package, the same as is valid for dspace import command launcher.

Solr upgrade (WIP)

Findings

Solr is distributed on Maven Central as a .war file, which includes the Lucene .jars. No Lucene version relevant to DSpace is available from Maven Central.

Solr is a wrapper for Lucene providing concurrency. Lucene can work with index files directly if we don't need concurrent access (i.e. before we start up Solr).

DSpace 1.6 was the first version to use Solr for statistics. In order to upgrade to DSpace 5, we need to upgrade the Solr index format in two steps. The second step is easy, upgrading from DSpace 3 (Solr 3.5) to DSpace 5 means just running the Solr 4.4 optimize command, which can be run even concurrently when the UIs are running. However, Solr 4.4 doesn't understand the legacy index formats used in Solr before 3.5. Therefore, in the first step, we need to use Solr 3.5 or Lucene 3.5 to upgrade from the older index versions to 3.5.

Suggested upgrade

We need to avoid the conflict of having both Solr 3.5 and 4.4 in the DSpace classpath. Therefore I suggest to run the first step before the Solr 4.4 webapp is started as part of DSpace 5.

To do that, we need to:

1. detect the index version using getCurrentVersion(index_dir)
2. for any version older than LUCENE_35 go to 3, otherwise go to 7
3. get the Solr 3.5 war from Maven Central
4. extract the lucene-core-3.5.0.jar from the Solr 3.5 war
5. run the IndexUpgrader class of Lucene 3.5 (or optimize())
6. start up DSpace in order to start up Solr 4
7. run the IndexUpgrader class of Lucene 4.4
   

DSpace/Solr/Lucene versions and compatibility

...