-
Notifications
You must be signed in to change notification settings - Fork 7
1.3 How the Structure Manager works
Adam Ploshay edited this page Dec 6, 2018
·
3 revisions
This describes the components involved to allow the user to drag and drop pages and sections around to represent structure and then save it to the work resource. The resulting data representing the structure is saved as described here.
The actual post to the controller /concern/scanned_resources/:id/structure
with the resulting data happens here.
Example of JSON data representing logical order that is posted:
{"nodes":[{"label":"Front matter","nodes":[{"proxy":"tj6731378c"},{"proxy":"t6q182k16k"},{"proxy":"t3f4625410"}]},{"proxy":"tdb78tc03k"},{"label":"Section 1","nodes":[{"proxy":"tdf65v787x"},{"proxy":"t6d56zw60x"},{"proxy":"t7h149p86f"}]},{"proxy":"t6d56zw617"}],"label":"Logical"}
Views:
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/master/app/views/curation_concerns/base/structure.html.erb
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/master/app/views/curation_concerns/base/_structure_node.html.erb
Javascript:
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/master/app/assets/javascripts/structure_manager.es6
- https://github.com/IU-Libraries-Joint-Development/pumpkin/blob/master/app/assets/javascripts/structure_parser.es6
Stylesheets: