...
- Applications - Because Applications are instance specific, this page's contents would be limited to show only those Applications for my user's assigned ODS instances. When defining a new Application, the specific instance to add it to would need to be known, either as a new field in the Add Application overlay or as a tab-wide Instance selection/filter showing only those instances associated with the user.
- Descriptors - We suspect we need an ODS instance selection here, and then show descriptors for that instance. But, if there is a single API, what distinguishes one instance's descriptors from the next? Does the single API combine results from each instance?
- Education Organizations - Similar concerns as with Applications. The user should only see Education Organizations from their assigned ODS instance, and when they hit Add Local Education Agency, they'll need to have an ODS instance selected.
- Risk: This screen raises further questions about terminology. Early discussion of the deployment model displayed in the "Goals" section above tended to equate "District" with each ODS instance database. The sample Education Organization of Grand Bend ISD suggests that Education Organizations may be districts. It's unclear, then, whether there is a strict association between Education Organizations and ODS instances in all cases, or whether there are, say, non-district Education Organizations which might in fact span ODS instances.
- Bulk Load - Because bulk load hits the API with a specific Key and Secret entered in this screen, we expect no further need for Multi-Instance concerns here. Is this in fact a "global" API-level concern, belonging under Global, or is it somehow in fact ODS instance specific?
- Learning Standards - Same questions as for Bulk Load.
- Reports - AA currently adds reporting views to the target ODS database to enable reports. We expect this page to need an ODS Instance selection similar to Applications and Education Organizations.
- Risk: There's a similar conceptual/vocabulary risk here as with Education Organizations above. This screen has a District drop down list. Given that specific ODS instances have been described in terms of districts so far, it raises the question about how strictly true those examples are, or whether we need to be extra precise in our language: on the reports tab, for instance, would the user select both an ODS Instance and a District, and when would those not be the same apparently selection to the user.
- Recommendation: When the existing "Select District" dropdown has only one option, autoselect it. The underlying data for this dropdown is Local Education AgeneciesAgencies, so should "Select District" be rephrased to match?
- Recommendation for any ODS instance selector: when the current user has exactly one instance available to them, autoselect it.
...