Filesets receive different visibilities at time of upload

[eporter23]

Descriptive summary

In Sirenia, when uploading multiple FileSets to a single work whose visibility is set to Embargo, the FileSets receive different visibilities. This bug occurred while working through the Hyrax QA testing steps in W_1.1.

Steps to reproduce the behavior in User Interface (UI)

1. Login as [email protected] (or as a non-Admin level user)
2. Create a new work (Generic Work) and assign it to the Default Admin Set
3. Add all required metadata
4. Upload 2 files
5. Change the work's visibility to Embargo, with a public release
6. Save the work
7. Refresh the work to see the Filesets are attached
8. Observe that one is Private, and one is Embargo
9. Click on a FileSet to view it
10. see "unauthorized" error

Actual behavior (include screenshots if available)

Include what version of Hyrax relates to this issue (3.x, 4.x, main branch, etc.) if appropriate, and any relevant error messages/tracebacks if you're reporting a bug.

Hyrax 5.x main; Sirenia docker image

Acceptance Criteria/Expected Behavior

• Both FileSets should receive the same Visibility as the work
• Non-admin depositors should be able to view the FileSets attached to their work

Rationale (for feature request only)

Provide the rationale or user story that describes "why" this issue should be addressed. Especially if this is a new feature or significant change to the existing implementation.

Related work

Link to related issues or prior related work here.

[rjkati]

This issue does not occur on dev.samvera or pg.samvera, just sirenia

[eporter23]

This issue partially recurs as of 9/10/24 related to the Visibility issue. One FileSet is embargoed and the second is Private. However, the non-Admin user is able to view both FileSets. We aren't seeing this behavior on a non-pair treed Sirenia application locally.

[eporter23]

On re-testing with cleared cache, this isn't recurring. @rjkati this may be closable if you haven't been able to reproduce it, also.