Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Complex Objects: child works are out of order in 'Contained In This Object' interface at bottom of show page #2945

Closed
petersec opened this issue Sep 20, 2023 · 3 comments · Fixed by #3255 · May be fixed by #3274
Closed

Complex Objects: child works are out of order in 'Contained In This Object' interface at bottom of show page #2945

petersec opened this issue Sep 20, 2023 · 3 comments · Fixed by #3255 · May be fixed by #3274
Assignees
@lsat12357
Labels
Features Issues related to building and enhancing features Priority - High Issues that should be prioritized ahead of others - early timing in the project

Comments

@petersec
Copy link

Descriptive summary

For complex objects, the child works rendering in the 'Contained In This Object' interface at the bottom of the show page are not in numerical order. See, for example, this work.

opera-varia

Expected behavior

The ordering of child works in the 'Contained In This Object' interface should match the ordering of child works as presented in Universal Viewer. Presumably, this will usually be numerical order beginning with child item 1.

Related work

#2786 addressed this problem for child works displaying in Universal Viewer.

Accessibility Concerns

None
@petersec petersec added the Features Issues related to building and enhancing features label Sep 20, 2023
@shieldsb shieldsb moved this to Backlog in Enhancement Workcycle 7 Dec 19, 2024
@CGillen CGillen removed their assignment Jan 6, 2025
@shieldsb shieldsb added the Priority - High Issues that should be prioritized ahead of others - early timing in the project label Jan 16, 2025
@lsat12357 lsat12357 moved this from Backlog to In Progress in Enhancement Workcycle 7 Jan 21, 2025
@lsat12357 lsat12357 self-assigned this Jan 21, 2025
@lsat12357 lsat12357 mentioned this issue Jan 29, 2025
Merged
@lsat12357
Copy link
Contributor

Tweak the first search builder response so that it always paginates acc. to the ordered_member_ids list (otherwise, may never see all of the viewable children if there are restricted/unreviewed/deleted items within the list)

@lsat12357 lsat12357 mentioned this issue Feb 6, 2025
Open
@lsat12357 lsat12357 moved this from In Progress to QA in Enhancement Workcycle 7 Feb 10, 2025
@lsat12357
Copy link
Contributor

QA: the asset that Chris linked to above should display the children correctly now. In addition, if staging solr has been fixed, the John Yeon compounds also are working (otherwise, they will be flipping between displaying correctly and not)

@petersec
Copy link
Author

QA pass

@shieldsb shieldsb moved this from QA to Ready for Production in Enhancement Workcycle 7 Feb 17, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@lsat12357 lsat12357

Labels
Features Issues related to building and enhancing features Priority - High Issues that should be prioritized ahead of others - early timing in the project
Projects
Enhancement Workcycle 7
Status: Ready for Production
Enhancement Workcycle 5
Status: Backlog
Enhancement Workcycle 6
Status: Backlog
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Show ordered children OregonDigital/OD2
use ordered count OregonDigital/OD2
4 participants
@lsat12357 @petersec @CGillen @shieldsb