Skip to end of metadata
Go to start of metadata

Content on this page is Work In Progress

Purpose

Students need a quick way to iteratively refine their searches without being taken to new pages, getting disoriented in navigation trails.  Being able to filter searches based on visible facet choices is fast becoming a design pattern that could be used effectively to address this need.  The Kuali Student and UW's My Plan team are already building a faceted search capability, but need API integration within the Rice framework's lookup architecture (enable KS/MP to return values to the lookup "under the covers" and enable the lookup to send results back to KS, so KS can populate the faceted search module that they build.

Detailed Description

The Kuali Student and UW's My Plan team are already building a faceted search capability, but need API integration within the Rice framework's lookup architecture:  enable KS/MP to return values to the lookup "under the covers" (no lookup UI exposed to the user) and enable the lookup to send results back to KS/MP, so KS/MP can populate the faceted search module they create.  Note:  it is possible that this could be contributed back to Rice in future so other applications could use and benefit from this.

Usage Scenarios

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

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: Link Here (completed by SME)

Final Documentation: Link Here (completed by DM)

Added to QA: No (completed by SME)

  • No labels