Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-12564

Analysis of Data Dictionary Contstraint Rewrite

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Analysis, Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      From Jerry:

      The current implementation of constraints in the data dictionary is very confusing and error prone. Moving forward will be a maintenance issue.

      [This] is really a technical thing. The code is very hard to support. Although there might be a possibility to rewrite a bit to use expressions. I think we should just brainstorm about this sometime

        Attachments

          Issue Links

            Activity

            Hide
            kbtaylor Kristina Taylor (Inactive) added a comment -

            We will defer this until we can have more of a complete brainstorming session on it.

            Show
            kbtaylor Kristina Taylor (Inactive) added a comment - We will defer this until we can have more of a complete brainstorming session on it.
            Hide
            cniesen Claus Niesen added a comment -

            Brainstorm with Jerry, Peter and Claus.

            Show
            cniesen Claus Niesen added a comment - Brainstorm with Jerry, Peter and Claus.
            Hide
            cniesen Claus Niesen added a comment -

            Notes from meeting between Jerry, Peter and Claus:

            • Implementation is complex
              • it's hard to figure out what's going on and fix issues
              • some constraint examples are long and tedious
                • Would expressions make it simpler? (Expressions are currently not supported in the data dictionary but that might be a good feature.)
            • It would be a good idea to get feedback from projects that have used DD constrains, mainly Kuali Students.
            • Specifically:
              • case constraints
              • must occur constraints
              • see KRAD Labs -> Kitchensink - > Validation
            Show
            cniesen Claus Niesen added a comment - Notes from meeting between Jerry, Peter and Claus: Implementation is complex it's hard to figure out what's going on and fix issues some constraint examples are long and tedious Would expressions make it simpler? (Expressions are currently not supported in the data dictionary but that might be a good feature.) It would be a good idea to get feedback from projects that have used DD constrains, mainly Kuali Students. Specifically: case constraints must occur constraints see KRAD Labs -> Kitchensink - > Validation
            Hide
            gilesp Peter Giles (Inactive) added a comment -

            Thanks for adding those notes Claus. A couple of points of clarification:

            • "expressions" above refers to Spring EL expressions.
            • This basically is a technical debt issue, the priority is not very high since it's been painful for us but this feedback isn't coming from our customers. We've moved this item to the backlog for now.
            Show
            gilesp Peter Giles (Inactive) added a comment - Thanks for adding those notes Claus. A couple of points of clarification: "expressions" above refers to Spring EL expressions. This basically is a technical debt issue, the priority is not very high since it's been painful for us but this feedback isn't coming from our customers. We've moved this item to the backlog for now.

              People

              • Assignee:
                Unassigned
                Reporter:
                cniesen Claus Niesen
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 days
                  3d
                  Remaining:
                  Remaining Estimate - 3 days
                  3d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified