This Confluence wiki site, maintained by DuraSpace prior to the recent merger with LYRASIS, will transition from the duraspace.org domain to the lyrasis.org domain on Saturday, Nov 16 beginning at approximately 7pm ET. A period of downtime of 2-3 hours is expected. After the transition, this wiki will be available at https://wiki.lyrasis.org/. All links to duraspace.org wiki pages will be redirected to the correct lyrasis.org URL. If you have questions prior to or following the transition please contact: wikihelp@lyrasis.org.

Page tree
Skip to end of metadata
Go to start of metadata

Developers Meeting on Weds, Oct 4, 2017

 

Today's Meeting Times

Agenda

Quick Notes / Reminders

  • NEXT DSpace 7 UI MEETING: TOMORROW, Oct 5 at 15:00 UTC (11:00am EDT) in Google Hangouts

Discussion Topics

  1. (Ongoing Topic) DSpace 7 Status Updates for this week

    1. Tim will be attending DSpace 7 Marketing Working Group (every two weeks) to bridge discussions between this group and tech team. This group will help provide a RepoMgr point of view to DSpace 7 efforts. (Join the #outreach channel on slack for more info)
    2. DSpace 7 UI Mockups is where we've been adding in new UI mockups. These mockups are discussed in detail with DSpace 7 team and also with Outreach. But external feedback also welcome!
    3. Currently team is concentrating on building out search functionality & submission functionality
  2. New DSpace Entities Working Group being established. If interested, there's a Doodle poll for the first meeting

  3. DOI field discussion. Where do we store DOIs going forward? (dc.identifier.doi?) 

    1. See this #dev Slack discussion on Sept 20: https://dspace-org.slack.com/archives/C3SG47SGY/p1505923323000280

  4. DSpace High Priority Tickets

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

       Click here to expand...

      Key Summary T Created Updated Assignee Reporter P Status Fix Version/s
      Loading...
      Refresh

    2. Need Code Review, Flagged for Release

       Click here to expand...

      Key Summary T Created Updated Assignee Reporter P Status Fix Version/s
      Loading...
      Refresh

  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: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/core/HibernateDBConnection.java
  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:

     Click here to expand...

    Key Summary T Created Updated Assignee Reporter P Status Fix Version/s
    Loading...
    Refresh

  2. Newly created tickets this week:

     Click here to expand...

    Key Summary T Created Assignee Reporter P Status
    Loading...
    Refresh

  3. Old, unresolved tickets with activity this week:

     Click here to expand...

    Key Summary T Created Updated Assignee Reporter P Status
    Loading...
    Refresh

  4. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Assignee Reporter P Status Resolution
    Loading...
    Refresh

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

     Click here to expand...

    Key Summary T Created Updated Assignee Reporter P
    Loading...
    Refresh

Meeting Notes

Meeting Transcript