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

Developers Meeting on Weds, April 18, 2018


Today's Meeting Times


Quick Reminders

Friendly reminders of upcoming meetings, discussions etc

Discussion Topics

If you have a topic you'd like to have added to the agenda, please just add it.

Note: Tim will be unavailable for next week's meeting (April 25 at 20UTC).

  1. DSpace 7 Community Sprints : First sprint will be two weeks, May 7-18.  Signup if interested
    1. Sprint goals documented at DSpace 7 Community Sprint 1
  2. Updates from the DuraSpace Member Summit

    1. Three DSpace breakouts at Summit: (1) minor updates to Governance Model, (2) Discussions of Entities WG output & Steering Group Recommendation, (3) Getting more contributions / feedback on Community Sprints
      1. Notes on all breakouts at:
    2. Also a public google doc of notes on everything that went on at Summit (not just DSpace specific):
    3. Summit attendees tend to be Library directors, Library IT directors, other managers
    4. Key highlights for DSpace developers
      1. DSpace Entities
        1. DSpace Steering Group publicized a new statement on their proposal for moving forward with DSpace Entities effort:
        2. Proposal is to move forward with option #3, but turn it into an open, community developed project (similar to DSpace 7 WG efforts currently)
        3. Summit attendees are in favor of adding new Entities to DSpace 7, but resources are the main question.
        4. Summit attendees proposed developing a small MVP (minimum viable product) to make this more tangible and perhaps help garner more support (via funding or resources).
        5. Key question now is finding resources and/or scoping tightly for DSpace 7.
      2. Sprint details were enhanced/improved based on feedback from Summit attendees
  3. (Ongoing Topic) DSpace 7 Status Updates for this week (no major updates)

    1. DSpace 7 Working Group is currently concentrating on building out search, submission, authentication and MyDSpace functionality. 4Science submission/workflow UI (see  video, slides) to be submitted as series of PRs in coming weeks.
    2. DSpace 7 Dev Status spreadsheet:
  4. (Ongoing Topic) DSpace 6.x Status Updates for this week

    1. DSpace 6.3 Release Planning is ongoing. Thanks to those who have been helping out with tests and reviews over the last week.

    2. As we approach the proposed deadline of May 1, more open PRs will be shifted to 6.4 as we don't have enough resource to get through them all. By April 25th, if we can get to a 'soft freeze' on 6.x merges, we can start testing a 6.3 release more thoroughly. More info at:!topic/dspace-devel/RbHhnhaFOto

  5. Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)

    1. ORCID support broken:   DS-3447 - Getting issue details... STATUS
    2. DSpace 6 performance issues with items containing a lot of bitstreams?!topic/dspace-tech/VIofW7EwEXY
    3. DS-3649 - Getting issue details... STATUS

Tabled Topics

These topics are ones we've touched on in the past and likely need to revisit (with other interested parties). If a topic below is of interest to you, say something and we'll promote it to an agenda topic!

  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:

Ticket Summaries

  1. Help us test / code review! These are tickets needing code review/testing and flagged for a future release (ordered by release & priority)

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

  2. Newly created tickets this week:

    Key Summary T Created Assignee Reporter P Status

  3. Old, unresolved tickets with activity this week:

    Key Summary T Created Updated Assignee Reporter P Status

  4. Tickets resolved this week:

    Key Summary T Created Assignee Reporter P Status Resolution

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

    Key Summary T Created Updated Assignee Reporter P

Meeting Notes

Meeting Transcript