Dependent Resource Modeling

[maxdumas]

Resources marked as dependent should appear in the same forms as the resource they depend on. They should NOT be visible from the landing page; creating/editing/listing them alone is not possible and they are only manipulated as part of the resource on which they depend.

The field will be a boolean is-dependent in the root of each resource. Each resource will need to check all of its linked resources to see if the linked resource is dependent, and if it is then its field are included in the form.

[ethanresnick]

More context for future readers: the motivation for this is that, without it, the UX absolutely sucks for adding dependent resources. Consider adding a school attendance to a person. It takes 5 steps:

1. From the homepage, go to SchoolAttendance's ADD view and fill out the form. Click Submit.
2. Copy and paste the id of the new SchoolAttendance that shows up in the resulting LIST view.
3. Go back to the homepage.
4. Click on Person's LIST button, find the Person to Edit, and open up that Person.
5. From the Person's EDIT view, paste the id copied earlier into the schools typeahead.

Of these steps, the copy-and-pasting between steps 2 and 5 is non-obvious and cumbersome. Moreover, steps 2, 3, and part of 5 ought to be unnecessary, and would be made so by dependent resource UI. As a side benefit, modeling dependent resources would be to clean up the landing page by removing items that don't make sense there.