Skip to content
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

In valkyrie/fedora deleting a work leaves orphan FileMetadata objects #6334

Closed
1 task
dlpierce opened this issue Sep 28, 2023 · 0 comments · Fixed by #6357
Closed
1 task

In valkyrie/fedora deleting a work leaves orphan FileMetadata objects #6334

dlpierce opened this issue Sep 28, 2023 · 0 comments · Fixed by #6357

Comments

@dlpierce
Copy link
Contributor

Descriptive summary

In valkyrie/fedora deleting a work leaves orphan FileMetadata objects

Steps to reproduce the behavior in User Interface (UI)

  1. Load sirenia (Add config for valkyrie fedora and "sirenia" compose file #6331)
  2. Create a monograph
  3. Delete the monograph (may produce error, see In valkyrie/fedora, deleting a work results in an error #6333)
  4. Observe FileMetadata objects in fedora and solr

Actual behavior (include screenshots if available)

FileMetadata objects left in fedora and solr after their associated objects were deleted

Acceptance Criteria/Expected Behavior

  • FileMetadata objects are deleted when their parent FileSet is deleted

Related work

#6331

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

2 participants