child works do not inherit the parent work’s visibility

[alishaevn]

Descriptive summary

child works do not inherit the parent work’s visibility (when the parent work has a lease or embargo on it)

Steps to reproduce the behavior in User Interface (UI)

• create work1, with a file, and add a lease (the lease should be applied to the work and file set)
• using the “add a child” link on work1's show page, create work2, that also has a file with a visibility of private. (side note, the “add a child” link may not work. I had to right click to copy the link and paste it in the url bar)
• create work3, also with a file, and set its visibility is public
• go back to work1 and edit it. on the “relationships” tab add work2 as a child
• on the show page for work1, scroll down to “items”. you should see its file set along with work2 and work3. work's 2 and 3 will have the visibility that each was created with. they did not inherit the parent visibility. neither did the file sets attached to them.

Actual behavior (include screenshots if available)

this is happening on main, commit sha 92ead3a248c40db2857d8709ca9968afbe1e7089

Acceptance Criteria/Expected Behavior

• I assume that the expectation is that when following the steps above, the child works and file sets attached to them, inherit the parent visibility.

Rationale (for feature request only)

I assume that the expectation is that when following the steps above, the child works and file sets attached to them, inherit the parent visibility.

Related work

I noticed this wasn't working while doing work for #6126