Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • "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.
    • NOTE: Tim may be late 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.  Status check on 4.0 issues (~3 weeks till our tentatively scheduled final release)
    1. Jira
      serverDuraSpace JIRA
      keyDS-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
        serverDuraSpace JIRA
        keyDS-1762
      2. Summary: DSpace 4.0 indexing commands
    2. Jira
      serverDuraSpace JIRA
      keyDS-1621
    3. https://github.com/DSpace/DSpace/pull/379 : Needs a review for 4.0, as it fixes
      Jira
      serverDuraSpace JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyDS-1483
      issue.  This is another request from Google to improve indexing in Google Scholar.
    4. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyDS-1709
      - Waiting on porting to JSPUI.
    5. Other specific tickets to follow up on? Issues? Questions?
    6. 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

...