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

Developers Meeting on Weds, Dec 13, 2017


Today's Meeting Times


Quick Reminders

Friendly reminders of upcoming meetings, discussions etc

  • DSpace 7 Working Group: Next meeting is Dec 14 at 15:00 UTC in Google Hangouts (Last meeting of 2017!). See wiki page for meeting details and past meeting notes.
    • DSpace 7 UI Mockups - Watch this page for UI/UX mockups that are currently under discussion, etc.
  • DSpace Entities Working Group: Next meeting is TBD (January 2018). See wiki page for meeting details and past meeting notes.

Holiday meeting schedule: This will be our final, official meeting for 2017. Have a happy holidays / new year!

Note: Tim is out Dec 18-Jan 2, returning to office on Jan 3, 2018. Will not be responding to email during that period.

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

    1. Team is currently concentrating on building out search, submission, authentication and MyDSpace functionality
    2. Refactoring of submission configs notes at Configuration changes in the submission process
  2. (Ongoing Topic) DSpace 6.x Status Updates for this week

    1. DSpace 6.3 Release Planning is ongoing.  Looking for more contributors!

  3. DCAT approval for DOI field standardization:  DS-3708 - Getting issue details... STATUS
  4. Discussion on proposed DSpace Java code style:

  5. Tickets or Pull Requests requiring attention? (Please feel free to add any you wish to discuss under this topic)

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