forked from pulibrary/plum
-
Notifications
You must be signed in to change notification settings - Fork 5
1.1 How Plum persists structure of member pages
Randall Floyd edited this page May 24, 2018
·
1 revision
Saving of structure begins with:
POST /concern/scanned_resources/:id/structure => curation_concerns/scanned_resources#save_structure
The #save_structure method in a registered curation concern (i.e. a ScannedResource) comes from:
- CurationConcerns::MemberManagement
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/d0e720466e85ac0b89fd5497c51b089775ff326b/app/controllers/curation_concerns/curation_concerns_controller.rb#L5
#save_structure calls SaveStructureJob
Structure passed from form is used to set #logical_order on resource:
#logical_order comes from:
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/d0e720466e85ac0b89fd5497c51b089775ff326b/app/models/scanned_resource.rb#L7
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/master/app/models/concerns/structural_metadata.rb
Logical order classes behind #logical_order
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/master/app/models/logical_order_base.rb
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/master/app/values/logical_order.rb
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/master/app/values/logical_order_graph.rb