Jan 19 : Discussion of which new entities should be in out-of-the-box =
DSpace (possibly People, Orgs?). Will begin a technical analysis of entitie=
s to add, compare to the work of DSpace-CRIS
Discussio=
n Topics
If you have a topic you'd like to have added to the agenda, please j=
ust add it.
(Ongoing Topic) DSpace 7 Status Updates for this week
Currently, we are looking for individual(s) interested in leading / con=
tributing to getting a 6.3 release out the door. Many "usual suspects" are =
busy with 7.x efforts.=20
Some discussion that this might be plausible to do via a 1-2 week sprin=
t, but still needs a Sprint Coordinator.
Tickets, Pull Requests or Email threads/discussions requiring more a=
ttention? (Please feel free to add any you wish to discuss under t=
his topic)
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
JNDI tickets: =
Unable to locate Jira server for this macro. It may be due to Application =
Link configuration. and Unable to locate Jira server for this macro. It may be=
due to Application Link configuration.
These topics are ones we've touched on in the past and likely need to re=
visit (with other interested parties). If a topic below is of interest to y=
ou, say something and we'll promote it to an agenda topic!
Management of database connections for DSpace going forward (7.0 and be=
yond). What behavior is ideal? Also see notes at DSpace Database Access
In DSpace 5, each "Context" established a new DB connection. Context th=
en committed or aborted the connection after it was done (based on results =
of that request). Context could also be shared between methods if a s=
ingle 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 t=
wo Context objects could use the same Connection (if they are in the same t=
hread). In other words, code can no longer assume each new Conte=
xt() is treated as a new database transaction.