Friendly reminders of upcoming meetings, discussions etc
If you have a topic you'd like to have added to the agenda, please just add it.
- Facilitator for next week (April 11 at 20UTC)? (Tim has a conflict – DuraSpace Summit meeting – and is unable to attend)
- DSpace Entities Working Group - quick updates
- Discussion in DSpace Entities WG meeting centering around option #3: https://docs.google.com/document/d/1exm_xLToxUMszOvX5itSMFTn5eiGCdggL0Mf522GjHU/edit#heading=h.bhq44wdzzis0
- DSpace Steering to discuss later today. Additional discussion at DuraSpace Summit next week (April 10-11)
- Final decision may not be to select a single proposal "as-is", but to create a community project inspired by one of these proposals. So, even once a selection is made, there will be opportunity for ongoing community feedback to enhance/improve the final result.
(Ongoing Topic) DSpace 7 Status Updates for this week
- DSpace 7 Community Sprints are in planning phase.
- DSpace 7 Working Group is currently concentrating on building out search, submission, authentication and MyDSpace functionality
- DSpace 7 Dev Status spreadsheet: https://docs.google.com/spreadsheets/d/18brPF7cZy_UKyj97Ta44UJg5Z8OwJGi7PLoPJVz-g3g/edit#gid=0
(Ongoing Topic) DSpace 6.x Status Updates for this week
(NEW) DSpace 6.3 Release Planning has begun (thanks to Kim Shepherd)
- We could use your support! See also the call for participation on all lists: https://groups.google.com/d/msg/dspace-tech/pBy714dGqU0/MGszGDCYAgAJ
Tickets, Pull Requests or Email threads/discussions requiring more attention? (Please feel free to add any you wish to discuss under this topic)
- ORCID support broken:
- DSpace 6 performance issues with items containing a lot of bitstreams? https://groups.google.com/forum/#!topic/dspace-tech/VIofW7EwEXY
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 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
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: