Developers Meeting on Weds, Sept 27, 2017



Quick Notes / Reminders

Discussion Topics

  1. DSpace German User Group (Anwendertreffen) was a great success! Thanks to Pascal-Nicolas Becker and others involved in organizing. Presentations available at DSpace Anwendertreffen 2017

  2. (RESCHEDULED FOR OCTOBER 4) DOI field discussion. Where do we store DOIs going forward? (dc.identifier.doi?) 

    1. See this #dev Slack discussion on Sept 20:

  3. Terrence W Brady's work with DSpace 6 + Codenvy:

  4. DSpace High Priority Tickets

    1. High Priority (Blocker, Critical or Major) and flagged for release

    2. Need Code Review, Flagged for Release

  5. Other Tickets needing discussion / attention? (Please feel free to add any you wish to discuss under this topic)
  6. Ongoing discussion topics:
    1. Management of database connections for DSpace going forward (7.0 and beyond). What behavior is ideal? Also see notes at DSpace Database Access
      1. In DSpace 5, each "Context" established a new DB connection. Context then committed or aborted the connection after it was done (based on results of that request).  Context could also be shared between methods if a single transaction needed to perform actions across multiple methods.
      2. In DSpace 6, Hibernate manages the DB connection pool.  Each thread grabs a Connection from the pool. This means two Context objects could use the same Connection (if they are in the same thread). In other words, code can no longer assume each new Context() is treated as a new database transaction.
        1. Should we be making use of SessionFactory.openSession() for READ-ONLY Contexts (or any change of Context state) to ensure we are creating a new Connection (and not simply modifying the state of an existing one)?  Currently we always use SessionFactory.getCurrentSession() in HibernateDBConnection, which doesn't guarantee a new connection:
  7. Reviewing JIRA Tickets or PRs
    1. Please feel free to bring any that need eyes / immediate discussion
    2. JIRA Backlog of "Received" tickets
    3. All open PRs

Ticket Summaries

  1. Help us test / code review! These are tickets needing code review/testing and flagged for a future release:

  2. Newly created tickets this week:

  3. Old, unresolved tickets with activity this week:

  4. Tickets resolved this week:

  5. Tickets requiring review. This is the JIRA Backlog of "Received" tickets: 

Meeting Notes

Meeting Transcript