Skip to end of metadata
Go to start of metadata

(Draft in progress below ... not completed)

Purpose

Unauthenticated view-only access will become increasingly critical to universities in order to reduce the number of places information is replicated and must be kept in synch.  For example, both prospective and current students need to search for course and program data, while only current students (and advisors, and faculty, and other staff) need to change or manipulate the data, as in updating program information.

Unauthenticated access requirements are forecast to grow, as mobile device usage grows.  Research shows that students and other users are already quite comfortable shifting their information access tasks to these small devices, while they still prefer to do data-entry-intensive tasks with a larger keyboard and display.

The ability to locate information with public search engines (Google, Bing, Yahoo, etc.), and then to get access to it, requires unathenticated view-only access.  A side benefit is this will make it easier for faculty and staff to collaborate (to identify other sources with complementary information) and for departments to reduce and re-use content.

Detailed Description

Give a detailed description for the enhancement. Clearly describe all concerns, eliminating ambiguities.

Usage Scenarios

Include at least one usage scenario, from the user's task perspective, that might be helpful in understanding the issue:

  • Future students and current students who are searching for course or program requirements data, but have not yet logged in to authenticate, can still do so.
  • People who are searching for a particular reference/resource via a public search engine and would like to know if it is available through a university library, can do so even if they are not affiliated with that university or library.

Mocks and Diagrams

Include any mocks (for UI enhancements) or diagrams that might be helpful in understanding the issue:

Performance

If applicable, list expectations for performance (optimal and worst cases would be fine, give time in seconds):

References

Include links to other confluence pages or external resources that might be helpful for this issue:

Requirements Listing

List all requirements (individual verifiable statements) that indicate whether the work for this item has been complete. If there are requirements that are not essential to the functionality but would be nice to have if time allows, enter those under 'Secondary':

Primary:
  1. item
  2. item
Secondary:
  1. item
  2. item

Dependencies

List any functional or technical work that must be completed before work on this item can begin:

  1. item

Issues

List any issues that need to be resolved before work on this item can begin:

Functional:
  1. item
  2. item
Technical:
  1. item
  2. item

QA or Regression Testing Plan

List steps needed to test the basic functionality of this update, enhancement, bug fix

  1. test/steps
  2. test/steps

Checkoff

Functional Analysis Complete? No (completed by SME)

Needs Review by KAI? No (completed by SME)

Technical Analysis Complete? No (completed by DM)

Needs Review by KTI? No (completed by DM)

Estimate: 30 hours (completed by DM)

Technical Design: Link Here (completed by DM)

Jira: KULRICE-6679 

Final Documentation: Link Here (completed by DM)

Added to QA: No (completed by SME)

  • No labels