Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Analysis, Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-8631Rewrite of data dictionary constraints
      KULRICE-10711Data Dictionary Analysis (items DD1 - DD6)
      KULRICE-10712Data Dictionary Analysis (items DD7 - DD9)
      KULRICE-8793Perform analysis of the KNS data dictionary framework
      KULRICE-9441KNS/KRAD Equivalence for Data Dictionary
      KULRICE-10114Maintenance Gap Analysis: Data Dictionary Properties (rows 82 - 85)
      KULRICE-10513Maintenance Gap Analysis: Data Dictionary Properties (rows 86 - 89)
      KULRICE-10514Maintenance Gap Analysis: Data Dictionary Properties (rows 90 - 94)
      KULRICE-10515Maintenance Gap Analysis: Data Dictionary Properties (rows 95 - 98)
      KULRICE-10516Maintenance Gap Analysis: Data Dictionary Properties (rows 99 - 102)
    • 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

        Issue Links

          Activity

          Hide
          Kristina Taylor (Inactive) added a comment -

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

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

          Brainstorm with Jerry, Peter and Claus.

          Show
          Claus Niesen added a comment - Brainstorm with Jerry, Peter and Claus.
          Hide
          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
          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
          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
          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:
              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

                  Structure Helper Panel