| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
|---|
| key | DS-4149 |
|---|
|
| https://github.com/DSpace/DSpace/pull/27092859 | Needs review | A larger improvement that has a +1 and some positive reviews, but also concerns. Needs another committer review | | Jira |
|---|
| server | DuraSpace JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
|---|
| key | DS-3945 |
|---|
|
| PR#2191
PR#2113
PR#1730 (merged)
PR#2464 | Competing PRs | A small bugfix, but there seem to be three PRs with similar solutions.
I think we prefer PR#2113 as it is a bit more robust, but...
I think PR#1730 might already fix the issue - needs testing. And PR#2464 is trying to fix a starts by issue and has a conflict with the changes merged from #1730.
In short: I think this issue might either be fixed already in 6.x, or just needs PR#2113 to merge. Would appreciate a second opinion.
I could not replicate the issue described in PR#2464 when using a build off 6_x. I tried browsing authors, titles and subjects, with RPP = 2 to compensate for the relatively little content on my test database.
I think we should merge PR#2113 and skip these other two. Having said that, I do not feel like I can be 100% about this. -- Hrafn MalmquistUpdate: Resubmitted PR that doesnt' include all the registry / schema additions, just the core functionality, to avoid side-effects and possible incompatibility with DSpace 7 |