-
Notifications
You must be signed in to change notification settings - Fork 133
Description
Descriptive summary
Setting the admin set during create or editing a work and changing the admin set, does not move the work from the Default Admin Set to the newly selected admin set.
Rationale
Changing admin sets is a core behavior and should work for ActiveFedora AdminSets and Valkyrie AdministrativeSets.
Expected behavior
Edit work and change the Administrative Set for the work should update which admin set the work is in.
Actual behavior
Edit work and change the Administrative Set for the work has no impact on the admin set.
Steps to reproduce the behavior
Configure Hyrax:
- Edit
/config/initializers/hyrax.rband set:
config.collection_model = "Hyrax::PcdmCollection"
config.query_index_from_valkyrie = true
config.index_adapter = :solr_index
- restart rails app
- Make sure regular
hyrax-developmentandhyrax-valkyrie-devsolr cores are running . Your core names may vary depending on how you start them and how they are configured in the app. - Make sure you have access to the datastore (i.e. postgres)
NOTE: For testing of nurax-pg, the solr core is typically named nurax-pg.
Create an admin set
- navigate to: Dashboard -> Collections
- click button: New Collection
- select type: Admin Set
- click button: Create collection
- set Title: My Admin Set (or other meaningful name)
- click Save
To reproduce:
- navigate to: Dashboard -> Works
- click button: Add new work
- select type: Monograph (needs to be a Valkyrie resource)
- fill in required metadata and upload file if needed
- click tab: Relationships
- under Administrative Set, select the admin set created in the prerequisites
- click button: Save
This forwards to the new work's show page. The admin set relationship does not show in the Relationships section.
- click button: Edit
- click tab: Relationships
The admin set is set to the Default Admin Set instead of the one you selected.
Related work
See related issues in Issue #5326 UBER: Hyrax-Valkyrization MVP