-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preservation batch fails if media node ID does not exist as a Drupal node #19
Comments
… node ID but the Drupal node doesn't exist * address #19
The following is a list of Drupal IDs that are failing preservation. Best guess, the Drupal node was deleted however the associated Drupal media was not deleted thus are failing preservation because of the missing Drupal node component during the archival package creation
|
There are 10 media items that indicate they are associated with a Drupal Node but no Drupal Node with that ID exists. The following media items contain a "field_media_of" with a target id that is a Drupal Node however the specified Drupal Node doesn't exist thus causing the above preservation errors. Should a Drupal node exist? Or should I remove the "field_media_of" value? Note: the "field_media_of" is only visible in the json output (not the web UI).
|
The preservation run fails if there is a media item with a node ID and that node ID does not exist in the Drupal nodes. There might have been a bug that when a Drupal node was deleted the associated media items were not deleted. This causes the preservation run to fail with an exception.
Why do the following fail? Are the all the same reason as listed above?
Todo:
The text was updated successfully, but these errors were encountered: