NO-JIRA: Bugfix/reindex media on relate#552
Open
spirosdi wants to merge 2 commits into
Open
Conversation
mikejritter
approved these changes
Jul 20, 2026
mikejritter
left a comment
Contributor
There was a problem hiding this comment.
For some reason the first media I relate isn't showing up. Once I have one media the rest will index as expected. I'm going to spend a little bit of time to debug and see if it's something with my setup because the changes are straightforward.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this do?
collectionspace_denorm:objectCsidfield stays in sync with its relations.Why are we doing this? (with JIRA link)
The public browser detail page image gallery finds media by querying
collectionspace_denorm:objectCsidon Media docs. That field is only written when the Media doc itself is indexed, but relation create/delete events previously only reindexed the Collection Object. As a result newly related medias do not appear in the public browser until the media record is saved which triggers a reindex. Similarly, unrelated/deleted media keep showing until edited.How should this be tested? Do these changes have associated tests?
Dependencies for merging? Releasing to production?
No dependencies
Has the application documentation been updated for these changes?
Changelog has been updated
Did someone actually run this code to verify it works?
@spirosdi ran it locally
Have any new security vulnerabilities been handled?
no new security vulns