Hi Marc, I could see this working.
You'd have to decide what to do in the event of multiple values for this
metadata field in a single collection (take first? throw error?), but as
this change would probably involve changing the Edit Collection form
anyway, you could probably enforce non-repeate
Hi all,
Has anyone noticed a connection between curation tasks and the "idle in
transaction" postgres sessions we sometimes see in DSpace (5.x and earlier,
at least) when a transaction/connection hasn't been closed or completed
properly?
There are a couple of methods (AuthorizeManager.removePo
