Design

The Source Repositories item on the Products page (and in the Products menu) should have a landing page that doesn't require authentication to view and that provides a description of what it is (contents, purpose) and who should have access.

The Products page has the heading "Portal Products."  Is this accurate? Are these actually products of the Research Software Portal?

The products section has three different "products" listed that are actually all about use cases: (1) use case registry, (2) delivery priorities, and (3) delivery plans and status. This seems unnecessarily complex.

When logged in, the MY ACCOUNT feature appears as a menu item under the LOG OUT heading in the main menu. This isn't intuitive. I wouldn't think to look under LOG OUT for the MY ACCOUNT feature.

When I login, I'm taken to a user profile page and given options to make changes.

1) The "Manage Display" link shows me an Access Denied page. Why was I given a link?

What are the software and service requirements for SPs to support authorization policy definition, configuration, operation/enforcement, logging, etc., to implement policies that differentiate among credentials presented to GSI(?) or other services?

I like the Software Operators and Integrators section, does it make sense to have a place for documentation for the "Available packaged software", where we can link to the various readthedocs/github/etc.  I don't know whether that merits a "top-level" support menu or if it needs to be within the

This summary concludes the design review phase of XCI-419 work.

Being that we just decided to close out SDIACT-159 because we were having difficulty getting a plugin deployed to Nagios and no users were demanding the data, can you remove Nagios from the document on page 13.

The design specifies that the Info services is using AWS RDS Aurora PostgreSQL as the backend.  What about the backup on Jetstream?  It would need to be independent of AWS, right?  Is it running regular PostgresSQL and somehow mirroring Aurora data?