...
If you're affected by
| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
|---|
| key | DS-1536 |
|---|
|
, DSpace 4.1 fixes it, but you still need to fix the incorrect metadata generated by DSpace 4.0. To do so, execute the following SQL against the DSpace database.
PLEASE ensure you test these scripts on a non-Production server, and also backup you have backed up your database PRIOR PRIOR to running the scripts. Replace XXXXX with your handle prefix before the dot; e.g. if your prefix is "10123.1", replace "XXXXX" with "10123".
...
If you previously upgraded DSpace from 1.8.x to 3.0 and you use Oracle as your DBMS, you may be affected by
| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
|---|
| key | DS-2036 |
|---|
|
. The following SQL statement should correct the problem.
PLEASE ensure you test these scripts on a non-Production server, and also backup that you have backed up your database PRIOR to running the scripts....