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
Updating the index after deletion - I recommend adding code to the DeleteDataFile, DeleteDataset, and DeleteDataverse commands.
Another option, if possible, is to have a "start index of X" or "update index of X" command, and have these commands issue it after they are successful.
Related issue(s): #380
Redmine related issue(s): 3795
The text was updated successfully, but these errors were encountered:
Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-03-31T16:46:10Z
So far indexing has always been an add/replace. Individual Solr documents have never been targeted for deletion.
We need to figure this out for datasets anyway (more on this in a bit) so I'm bumping up the priority and target version.
For datasets, we want the following deletion to happen:
when a released dataset gets a new draft version, continue to index the dataset as id:dataset_42 but create a new Solr document (private to the group per Deaccession: Allow owner to update forwarding link #3464) called id:dataset_42_draft
when the draft dataset gets released, delete id:dataset_42_draft
Author Name: Michael Bar-Sinai (@michbarsinai)
Original Redmine Issue: 3787, https://redmine.hmdc.harvard.edu/issues/3787
Original Date: 2014-03-27
Original Assignee: Kevin Condon
Hello Phil,
Updating the index after deletion - I recommend adding code to the DeleteDataFile, DeleteDataset, and DeleteDataverse commands.
Another option, if possible, is to have a "start index of X" or "update index of X" command, and have these commands issue it after they are successful.
Related issue(s): #380
Redmine related issue(s): 3795
The text was updated successfully, but these errors were encountered: