DRYD-2117: Procedure/Object > Ability to set Priority Image#356
Open
spirosdi wants to merge 1 commit into
Open
DRYD-2117: Procedure/Object > Ability to set Priority Image#356spirosdi wants to merge 1 commit into
spirosdi wants to merge 1 commit into
Conversation
This was referenced Jul 2, 2026
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
1 participant
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?
It adds the repeatable field
priorityImageList/priorityImage. The field doesn't haveautocomplete="true" ui-type="enum"attributes because it is being prepopulated in the UI. Theservices-type-anonymous="false"is necessary so that Nuxeo creates a named join table, allowing the denorm writer to address the list by name. This is the same pattern for any repeating field that needs to be addressed by name.Why are we doing this? (with JIRA link)
This is part of the https://collectionspace.atlassian.net/browse/DRYD-2117. The new repeating field stores the already related media handling records of an object sorted.
How should this be tested? Do these changes have associated tests?
Please follow the steps in the cspace-ui PR: collectionspace/cspace-ui.js#360
Dependencies for merging? Releasing to production?
It should be released along the:
collectionspace/services#548
collectionspace/cspace-ui.js#360
collectionspace/cspace-public-browser.js#57
Has the application documentation been updated for these changes?
Changelog has been updated
Did someone actually run this code to verify it works?
@spirosdi tested locally