As a student, I want to learn how to fix it when I can't access concent, so that I can use the new JSTOR integration.

When users don't have access to content, we want to be able to help them (1) understand what went wrong and (2) help them troubleshoot if necessary. That way, students don't pepper teachers with complaints. Instead, when relevant, they may push teachers to push libraries to expand their JSTOR coverage.

Flow

flowchart LR
  student((Student))
  student -->
  launch(Open JSOR assignment) -- JSTOR says: no access! -->
  error(Show error message)

As a logged-in user

• When I launch an assignment to content I can't access, I view an error message that tells me what happened and directs me to the appropriate documentation
• If I do have access to the content, I don't see the no access error message

Constraints

• We need to be able to test that the error is due to not having
  • We can identify the right behavior on JSTOR's end

Notes

• As far as we know, JSTOR authentication and authorization happens at the institutional (side code) level; the end user doesn't really matter

Ideas

• Doesn't anyone else think we ought to have a CMS-lite for error content?