Developers Meeting on Weds, Nov 8, 2017

...

• DSpace 7 Working Group: Next meeting is TOMORROW, Nov 9 at 15:00 UTC (11:00am EDT) in Google Hangouts. 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 Weds, Nov 22 at 15:00UTC (10:00am EST). See wiki page for meeting details and past meeting notes.
  
  

Discussion Topics

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

   1. Team is currently concentrating on building out search functionality & submission functionality
   2. Refactoring of submission configs notes at Configuration changes in the submission process

2. DSpace High Priority Tickets

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

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status,fixversions maximumIssues 20 jqlQuery filter = 13904 ORDER BY fixVersion DESC, priority DESC serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

   2. Need Code Review, Flagged for Release

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status,fixversions maximumIssues 20 jqlQuery filter=13905 ORDER BY fixVersion DESC, priority DESC serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

3. Other Tickets needing discussion / attention? (Please feel free to add any you wish to discuss under this topic)
4. Ongoing discussion topics:
   1. Updating code style & validating via CheckStyle : Code Style Guide (WIP)
   2. 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
5. 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

...