Record page: secondary requests (aggregate, related entities) require login

[jrchudy]

This issue occurred at this link in facebase. When going to a record page, the user is given a login dialog. For users with less privileges, after logging in, they are given a Forbidden error dialog.

Some conversation points that came up while discussing this:

• should this warning/error be handled differently for different cases
  • aggregate in main section
  • inline related table main data
  • aggregate in inline related table
  • related table main data
  • aggregate in related table
• should this be a warning instead? no error?
• OR we can supply a degraded UX similar to what we do for facets when the data can't be fetched (or times out)
  • show a "warning" icon in the column header or related table header with a tooltip explaining the issue better
  • acts like a scoped warning to the location of the error instead of a page warning
• Curation status has a similar error scenario when a user is logged in then gets logged out
  • they are given a 409 error since anonymous users can't see curation status
  • the model the app thinks is different than what an anonymous user can see