There's already an implicit relationship between primary and secondary admin pages in the IDL, i.e., the primary class should have a link to the secondary. Would it make sense to add a "config_field" attribute to IDL links to make the relationship explicit? Then the admin page component could check for the attribute when loading the IDL class definition; if config_field = true, it could add a link to the grid directing the user to the appropriately-filtered secondary admin page.
For example, the IDL class definition for config.z3950_source has a link to config.z3950_attr. We would add a "config_field" attribute to the link field, like so:
Since we have a config_field attribute, the Z39.50 Sources grid would use the other IDL attributes
to construct a link to this URL:
/eg2/en-US/staff/admin/server/config/z3950_attr?gridFilters={"source":"oclc"}
Working branch user/jeffdavis/lp1847800-secondary-admin-pages doesn't construct that link yet, but it attempts to make the config_field IDL attribute available to Angular in order to do so:
There's already an implicit relationship between primary and secondary admin pages in the IDL, i.e., the primary class should have a link to the secondary. Would it make sense to add a "config_field" attribute to IDL links to make the relationship explicit? Then the admin page component could check for the attribute when loading the IDL class definition; if config_field = true, it could add a link to the grid directing the user to the appropriately- filtered secondary admin page.
For example, the IDL class definition for config.z3950_source has a link to config.z3950_attr. We would add a "config_field" attribute to the link field, like so:
<field reporter: label=" Attrs" name="attrs" oils_persist: virtual= "true" reporter: datatype= "link" config_ field:" true"/>
Since we have a config_field attribute, the Z39.50 Sources grid would use the other IDL attributes US/staff/ admin/server/ config/ z3950_attr? gridFilters= {"source" :"oclc" }
to construct a link to this URL:
/eg2/en-
Working branch user/jeffdavis/ lp1847800- secondary- admin-pages doesn't construct that link yet, but it attempts to make the config_field IDL attribute available to Angular in order to do so:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ jeffdavis/ lp1847800- secondary- admin-pages