You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After deleting a work in a sipity workflow from a hyrax 3 or 4 instance the work will continue to appear in the sipity_entities table (and probably the other sipity tables as well). The record is cleaned out of solr, and becomes a fcr:tombstone in fedora, but lives on in the relational database forever.
For example, in my .dassie environment I deleted the work with id vt150j246, but if I check the database I still see:
This is an issue since some pages are directly populated from queries of the database. For example, the Review Submissions page queries for sipity entities, and then looks those ids up in solr to return pages of results. The result is fewer than a full page of results will be returned, since the deleted items are returned from the DB but not found in solr.
Expected behavior
Sipity tables clear out entries related to deleted works.
Actual behavior
Sipity tables are unchanged when a work is deleted
Steps to reproduce the behavior
Create a work in a workflow (such as the default Mediated workflow)
connect to the database and query for the work (see query above)
In the UI, delete the work
Query the database again, you will see the entry still there
Related work
Relates to #5999 since this PR enables serverside paging for the Review Submissions page, which makes it visible when there are leftover deleted items in the sipity_entities table, since you can end up with pages of results that contain significantly fewer results than the page size.
The text was updated successfully, but these errors were encountered:
Descriptive summary
After deleting a work in a sipity workflow from a hyrax 3 or 4 instance the work will continue to appear in the sipity_entities table (and probably the other sipity tables as well). The record is cleaned out of solr, and becomes a fcr:tombstone in fedora, but lives on in the relational database forever.
For example, in my .dassie environment I deleted the work with id vt150j246, but if I check the database I still see:
Rationale
This is an issue since some pages are directly populated from queries of the database. For example, the Review Submissions page queries for sipity entities, and then looks those ids up in solr to return pages of results. The result is fewer than a full page of results will be returned, since the deleted items are returned from the DB but not found in solr.
Expected behavior
Sipity tables clear out entries related to deleted works.
Actual behavior
Sipity tables are unchanged when a work is deleted
Steps to reproduce the behavior
Related work
Relates to #5999 since this PR enables serverside paging for the Review Submissions page, which makes it visible when there are leftover deleted items in the sipity_entities table, since you can end up with pages of results that contain significantly fewer results than the page size.
The text was updated successfully, but these errors were encountered: