Page History

...

• "JIRA Backlog Hour" : Every Weds at 19:00UTC in #dspace IRC we will be working together to tackle our JIRA Backlog of "Received" tickets. This regular meeting will continue until we've been able to catch up on our backlog.
  • Tim is unfortunately unavailable for JIRA Backlog Hour this week, but others are welcome to take part on your own.
    

Discussion Topics

1. DSpace 4.0 Status & Testathon progress

   1. Jira
      server DuraSpace JIRA key DS-1749

      - What to do about the "./dspace index" scripts?  Do we point them at Discovery now (the new default)?  Do we leave them pointing at Lucene?
      1. We already have one reported bug because of confusion about the "index" scripts no longer working "out-of-the-box" in 4.0:

         Jira
         server DuraSpace JIRA key DS-1762

   2. Specific tickets to follow up on? Issues? Questions?https://github.com/DSpace/DSpace/pull/379 : Would this qualify as a 4.0 "bug fix" for 

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

      issue?  This is another request from Google to improve indexing in Google Scholar.

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

      - Porting Do we want to port to JSPUI?What to do about the "./dspace index" scripts?  Do we point them at Discovery now (the new default)?  Do we leave them pointing at Lucene?We already have one reported bug because of confusion about the "index" scripts no longer working "out-of-the-box" in 4.0: JiraserverDuraSpace JIRAkeyDS-1762
   4. Other specific tickets to follow up on? Issues? Questions?
   5. DSpace 4.0 Tasks
2. Search Interfaces (possibly standardizing on Discovery as the interface, with multiple providers)
   
   1. In DSpace 4.0, Discovery is enabled by default
   2. What do we want to do about plain-Lucene support?
      
      1. Option 1: Deprecate it in 4.0, and remove entirely in 5.0
      2. Option 2: Rewrite it so that it can be another provider behind Discovery (alongside Solr and possibly ES)
   3. For 5.0, we could also tentatively plan to release a Discovery on Elastic Search option

...