Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

BUG: Updating a Collection's visibility through the UI, if created in a Hyrax v5.x/Fedora v6.5/Valkyrie v3.3/Pair-Tree'ed application, doesn't persist to Fedora #6864

Closed
1 task
bwatson78 opened this issue Jul 18, 2024 · 2 comments

Comments

@bwatson78
Copy link
Contributor

Descriptive summary

BUG: Updating a Collection's visibility through the UI, if created in a Hyrax v5.x/Fedora v6.5/Valkyrie v3.3/Pair-Tree'ed application, doesn't persist to Fedora

Steps to reproduce the behavior in User Interface (UI)

  1. Start a Docker instance of Sirenia
  2. Log in as a user capable of creating a collection object
  3. Venture to Dashboard, click on Collections, and then Add a new Collection
  4. Choose a User Collection, and then fill in all required fields
  5. Save the Collection and wait for that object's edit page to load with a positive persistence message displaying
  6. Click on the Discovery tab and change the visibility to public
  7. Save and observe that the visibility doesn't reflect the desired option
  8. Open a rails console, pull the Valkyrie object by id, and observe that the visibility hasn't been changed.
  9. Open the Fedora UI, locate the object, and observe that it has also not been updated.

Acceptance Criteria/Expected Behavior

  • Changing the visibility in the UI should reflect in the show page, Valkyrie object, and Fedora UI page.

Related work

#6349

@rjkati
Copy link

rjkati commented Aug 5, 2024

This behavior also applies to works. When I attempt to change the visibility of a work via the UI, I get a Failed save on # undefined method 'split' for nil:NilClass error and the visibility of the work and files do not update.

undefinedmethod

I'm not sure if a new ticket for works is needed given that the behavior in the UI is similar to Collections, but I'm happy to create one if that's better for folks.

@rjkati
Copy link

rjkati commented Aug 6, 2024

In Hyrax 5.0.1 using sirenia, I'm able to change the visibility of a collection successfully in the UI, but my edit access is removed if I create the collection as a non-admin user. Since I can't replicate the visibility issue described in this ticket for collections, I'll close this ticket and open two new ones for the edit access issue and work issue described above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants