Feature | Status | Priority | Ticket(s) |
---|---|---|---|
User-visible features | |||
Common look and feel across all instances | YES | ||
Self-identification of instances in HTTP | NO | 2 | |
Short description of the intended purpose and uptime expectation for the instance | NO | 2 | |
Instance-specific MOTD | YES | ||
Link to the token-management (/auth/tokens ) endpoint for the instance (not currently applicable to cloud pop-ups?) | NO | 1 | |
Link back to the landing page (in some cases as "open in new window") from most major Web pages in the LSP (e.g., from the Portal Aspect)
| NO | 2 | |
Display of user's authentication status (e.g., "not logged in" vs. user name) and a nearby UI element for "sign in" or "sign out" as appropriate | NO | 2 | |
Create, and add a link to - parallel to the existing Notebook Aspect and Portal Aspect buttons - a new sub-landing-page just for the API Aspect documenting what the available services are
| NO | 3 | |
Display of user's authorization status
| NO | 4 | |
Link to top-level LSP documentation (e.g., via a new lsp.lsst.io), not just Nublado documentation | NO | 3 | |
Specific pointer to identity-establishment documentation ("how do I get access?") for new users (see DMS-LSP-REQ-0021)
| NO | 4 | |
Provision for "service status" (red light/green light) information to be displayed in the future for each Aspect and, within the API Aspect, for each service (hopefully integrated with VOSI-availability endpoints of the services) | NO | 4 | |
Engineering features | |||
Usable across all LSP instances (whether LDF-hosted or cloud pop-up) | |||
Mechanism (templating? configuration variables?) for providing instance-specific content | |||
Mechanism (templating? configuration variables? CSS?) for providing instance-specific conditional display of selected content elements
| |||
Implementation supports creation of sub-pages with common appearance and with access to some instance-specific template variables (e.g., the "short instance name"). |
The "Priority" column is meant to express a temporal (what's would be useful, and perhaps even feasible, first) priority, not a "what's the most important thing to have by the time Operations starts" viewpoint.