Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

Developers Meeting on Weds, May 9, 2018

 

Today's Meeting Times

Agenda

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.

  1. (Ongoing Topic) DSpace 7 Status Updates for this week (no major updates - other than Sprint going on)

    1. DSpace 7 Working Group (2016-2023) 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: https://docs.google.com/spreadsheets/d/18brPF7cZy_UKyj97Ta44UJg5Z8OwJGi7PLoPJVz-g3g/edit#gid=0

  2. (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 noted previously, the target release date is May 21, and some PRs will be shifted to 6.4 as we don't have enough resource to get through them all.

    3. The highest priority is testing and improving the ORCID v2 API functionality (DS-3447). If you have time to help, please try out the newest pull request at https://github.com/DSpace/DSpace/pull/2039 and join the conversation / reviews in Github.

  3. 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:   Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    3. JIRA tickets / PRs waiting for final approval in 6.3
      DS-3447 https://github.com/DSpace/DSpace/pull/2039

      DS-3507 https://github.com/DSpace/DSpace/pull/2038

      DS-3783 https://github.com/DSpace/DSpace/pull/2053

      DS-3902 https://github.com/DSpace/DSpace/pull/2048

      DS-3377 https://github.com/DSpace/DSpace/pull/2045

      DS-3795 https://github.com/DSpace/DSpace/pull/2032 (master)

      DS-3768 https://github.com/DSpace/DSpace/pull/1890

      DS-3769 https://github.com/DSpace/DSpace/pull/1891 (dep on #1890)

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


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 type created updated assignee reporter priority status fixversions

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Newly created tickets this week:

    key summary type created assignee reporter priority status

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Old, unresolved tickets with activity this week:

    key summary type created updated assignee reporter priority status

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  4. Tickets resolved this week:

    key summary type created assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

    key summary type created updated assignee reporter priority

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Meeting Notes

Meeting Transcript

 

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.