Details

    • Type: Rice Enhancement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: KIM
    • Labels:
      None
    • Rice Theme:
      Kuali Application Business Drivers
    • Priority Score:
      0
    • Functional Justification :
      users can set up and maintain their preferences for all kuali applications in one place. better management of the data related to users (central repository)
    • Technical Justification:
      in the absence of this, many different ways to manage this information are being developed. this would save effort, eliminate duplication, ensure consistency, and centralize related data
    • Impact if not Implemented:
      the same sort of diverse and duplicate effort that has been occurring thus far and hardship to users
    • Priority - KFS:
      No Priority
    • Priority - KC:
      No Priority
    • Priority - KS:
      No Priority
    • Priority - Rice:
      No Priority
    • Effort Estimate:
      Medium ~ 500 hrs

      Description

      facilitate central storage of user preferences using the same "type" framework used for roles, permission, templates, etc. client applications should be able to provide configuration and one central profile should be able to be used by kuali users to set their preferences for the action list, default accounts on requisitions, etc. client applications should also be able to access and update these preferences via api, so they can be maintained closer to the related screens as well, when that is desirable... similar to how some client application documents currently update kim role membership.

        Attachments

          Issue Links

            Activity

            Hide
            ewestfal Eric Westfall added a comment -

            The backend portion of this is potentially simple. The UI aspects of such an environment are more complex. Probably the most straightforward approach would be to treat this similar to a user preferences "portal" where it links out to preferences that can be set in the various functional areas. A framework could be packaged with KRAD for surfacing these preference components. There is certainly some design work that would need to be done here but first step would be to make sure we understand the functional requirements around this.

            I think there's a question of whether we want the actual preferences living centrally or within each application database (closest to where it will actually be used).

            Show
            ewestfal Eric Westfall added a comment - The backend portion of this is potentially simple. The UI aspects of such an environment are more complex. Probably the most straightforward approach would be to treat this similar to a user preferences "portal" where it links out to preferences that can be set in the various functional areas. A framework could be packaged with KRAD for surfacing these preference components. There is certainly some design work that would need to be done here but first step would be to make sure we understand the functional requirements around this. I think there's a question of whether we want the actual preferences living centrally or within each application database (closest to where it will actually be used).
            Hide
            ewestfal Eric Westfall added a comment -

            Setting effort estimate as medium at the moment absent more specifics on this one.

            Show
            ewestfal Eric Westfall added a comment - Setting effort estimate as medium at the moment absent more specifics on this one.
            Hide
            abyrne Ailish Byrne added a comment -

            interesting - i was thinking of this a lot like how you can assign roles including qualifiers specific to each application in the kim person document. like i have one screen to set my action list preferences and default account for requisition etc. and the drawing of that screen is based on configuration similar to role type services. i think it would be good to talk more about the functional vision for the users - perhaps at the kai-wg. thanks, eric!

            Show
            abyrne Ailish Byrne added a comment - interesting - i was thinking of this a lot like how you can assign roles including qualifiers specific to each application in the kim person document. like i have one screen to set my action list preferences and default account for requisition etc. and the drawing of that screen is based on configuration similar to role type services. i think it would be good to talk more about the functional vision for the users - perhaps at the kai-wg. thanks, eric!

              People

              • Assignee:
                kymber Kymber Horn
                Reporter:
                abyrne Ailish Byrne
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: