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, Jan 10, 2018
Today's Meeting Times
- DSpace Developers Meeting / Backlog Hour: 15:00 UTC in #duraspace IRC or #dev-mtg Slack channel (these two channels sync all conversations)
- Please note that all meetings are publicly logged
Agenda
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.
Discussion Topics
If you have a topic you'd like to have added to the agenda, please just add it.
(Ongoing Topic) DSpace 7 Status Updates for this week
- Team is currently concentrating on building out search, submission, authentication and MyDSpace functionality
- Refactoring of submission configs notes at Configuration changes in the submission process
(Ongoing Topic) DSpace 6.x Status Updates for this week
DSpace 6.3 Release Planning is ongoing. Looking for more contributors!
- DCAT approval for DOI field standardization:
Discussion on proposed DSpace Java code style: https://github.com/DSpace/DSpace/pull/1895
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!
- Management of database connections for DSpace going forward (7.0 and beyond). What behavior is ideal? Also see notes at DSpace Database Access
- 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.
- 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.- 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 useSessionFactory.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
- Should we be making use of
Ticket Summaries
Help us test / code review! These are tickets needing code review/testing and flagged for a future release (ordered by release & priority)
Newly created tickets this week:
Old, unresolved tickets with activity this week:
Tickets resolved this week:
Tickets requiring review. This is the JIRA Backlog of "Received" tickets:
Meeting Notes
Meeting Transcript
IRC Transcript is available at - http://irclogs.duraspace.org/index.php?date=2018-01-10
Overview
Content Tools
All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license
, unless otherwise noted.