Uploaded image for project: 'Kuali Rice Roadmap'
  1. Kuali Rice Roadmap
  2. KRRM-25

Design and implement Kuali Organization Management (KOM)

    Details

    • Type: Rice Enhancement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: Unknown
    • Labels:
      None
    • Rice Theme:
      Adopting Existing Code
    • Priority Score:
      9
    • Impact if not Implemented:
      Duplication of effort within applications will continue as each, generally, relies upon some organization structure. Management will be a nightmare as organizational changes will need to be maintained in multiple applications for a single change.
    • Priority - KFS:
      High
    • Priority - KC:
      Medium
    • Priority - KS:
      High
    • Priority - Rice:
      No Priority
    • Theme:
      Kuali Application Business Drivers
    • Application Impact:
      High
    • Effort Estimate:
      High ~ 1000 hrs

      Description

      This has been discussed extensively in the past. Here are the notes from a KAI spreadsheet on the subject:

      "Organization infrastructure in Rice. This solution would provide the ability to use a single hierarchical structure, or context specific hierarchy structures unique to each application, but with overlapping organizational branches. This solution would achieve technical re-use across projects. A centrally maintained hierarchy is extremely important in controlling, for example, data role up for reports, establishing ownership of data, and accommodating workflow. It is further recommended that the consistent titling of this data should be "Organization" (from KFS), thus doing away with the KRA/COEUS "Unit". Shared tables and a shared set of service to retrieve from and update context specific and shared information those tables"

        Attachments

          Issue Links

            Activity

            Hide
            cfairlie Cath Fairlie (Inactive) added a comment -

            KS comment: KS has developed an ORG service which could be a good starting point for KOM design. The service design for KS ORG originally had input from Aaron Godert back in 2008 when it looked like KOM would move ahead a little faster. We tried to build it with the overall Kuali perspective in mind, but then when KOM efforts got delayed we just ran with the KS perspective. However, it should be a very good starting point for this body of work.

            Show
            cfairlie Cath Fairlie (Inactive) added a comment - KS comment: KS has developed an ORG service which could be a good starting point for KOM design. The service design for KS ORG originally had input from Aaron Godert back in 2008 when it looked like KOM would move ahead a little faster. We tried to build it with the overall Kuali perspective in mind, but then when KOM efforts got delayed we just ran with the KS perspective. However, it should be a very good starting point for this body of work.
            Hide
            jcoltrin Jessica Coltrin (Inactive) added a comment -

            Rice team is willing to champion this if noone else is.

            Show
            jcoltrin Jessica Coltrin (Inactive) added a comment - Rice team is willing to champion this if noone else is.
            Hide
            kgeis Ken Geis added a comment -

            I'm looking forward to this eventually getting into Rice to help us with KC at UC Berkeley. We have our unit hierarchy in KC which represents the master organization tree, but we're starting to have separate administrative clusters where administrative services are being provided to groups of units that are not aligned with the master org tree. Being able to reference these groups would enable authorization and roll-up as listed in the description. I've seen the KS design, and I was encouraged by it.

            Show
            kgeis Ken Geis added a comment - I'm looking forward to this eventually getting into Rice to help us with KC at UC Berkeley. We have our unit hierarchy in KC which represents the master organization tree, but we're starting to have separate administrative clusters where administrative services are being provided to groups of units that are not aligned with the master org tree. Being able to reference these groups would enable authorization and roll-up as listed in the description. I've seen the KS design, and I was encouraged by it.
            Hide
            jcoltrin Jessica Coltrin (Inactive) added a comment -

            removing myself as assignee

            Show
            jcoltrin Jessica Coltrin (Inactive) added a comment - removing myself as assignee

              People

              • Assignee:
                kymber Kymber Horn
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: