dspace-angular
dspace-angular copied to clipboard
DSpace
Issues with claimed items in MyDSpace
When an item is claimed in the workflow, the counter in the sidebar filter facet is not updated.
Before and after claiming the first item:
If the filter is clicked, sometimes the newly claimed item is listed in the results as expected, and sometimes it is not. It may also happen that also the previously claimed items are not listed even if the REST request returns them:
If the page is refreshed, all items will be listed:
If the item is returned to the pool, if the filter is clicked it may happen that the newly returned item is still listed among the claimed ones. Trying to return it to the pool will result in an error.
Yes, this seems like a possible duplicate or closely related to #1610. I'll pull this over to the 7.4 board alongside #1610 and hopefully the same person can claim both. If anyone is interested, let me know.
Hello @tdonohue , we are interested in working this issue and #1610. Our estimation is 16 hours
Sounds good @corrad82-4s . I'll assign both tickets to you for 7.4. I'll put the 16 hour estimate on this one, and just link up the other to it.
Hi @tdonohue , we have spent so far about 10 hours in analysis. We tried to restore a behavior present in version 7.1, but it won't resolve problems here reported. We will have to review estimations. For what concerns facets counters update, we are stuck, any advice is welcome. Our proposal is to split work in two: first resolve and open a PR for problem affecting item status update (2nd ant 3rd point of what reported by Davide) and work separately problem affecting facet counters update reported also in #1610
@corrad82-4s : Unfortunately, I don't have immediate advice to offer here. But, if it makes sense to break this ticket down into separate stages, I'm OK with that. If you can fix a few of the issues, perhaps it'll help us better debug what is going on with the last issue.
So, your proposal sounds good to me (and feel free to provide an updated estimate as needed). Let's see if that helps clarify what is happening in #1610... if it doesn't, then we can always bring this up for discussion in a future meeting to see if anyone else has ideas as to what the cause may be.