Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-9089

Design and analysis for how new metadata and Data Dictionary will be loaded and split from current data dictionary

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: Analysis, JPA, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-9098Determine how DictionaryValidationService will play into the new data dictionary design
      KULRICE-12564Analysis of Data Dictionary Contstraint Rewrite
      KULRICE-12166Two instances of the data dictionary service (and data dictionary) are loaded in Rice context
      KULRICE-10711Data Dictionary Analysis (items DD1 - DD6)
      KULRICE-10712Data Dictionary Analysis (items DD7 - DD9)
      KULRICE-8793Perform analysis of the KNS data dictionary framework
      KULRICE-8631Rewrite of data dictionary constraints
      KULRICE-4670integration with Data Dictionary
      KULRICE-9441KNS/KRAD Equivalence for Data Dictionary
      KULRICE-4742Look into loading of data dictionary changes to prevent full restart
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Data Dictionary
    • Sprint:
      JPA Sprint 4
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      The design for the new data layer indicates data dictionary becoming a part of the krad-data module and a home for metadata related to data objects. UIF-related configuration will live in a different "dictionary". Need to augment the design document with specifics on how this will work and come up with an approach for how it will be designed and implemented.

        Activity

        Hide
        Eric Westfall added a comment -

        One of the thoughts here was that we would end up with a Data Dicationary, View/UIF Dictionary, and Document Dictionary corresponding to the differnet modules of Rice. These would be loaded into different spring contexts most likely. And, in fact, for the data dictionary itself, the spring xml configuration is entirely optional as the metadata can come from many different providers.

        Show
        Eric Westfall added a comment - One of the thoughts here was that we would end up with a Data Dicationary, View/UIF Dictionary, and Document Dictionary corresponding to the differnet modules of Rice. These would be loaded into different spring contexts most likely. And, in fact, for the data dictionary itself, the spring xml configuration is entirely optional as the metadata can come from many different providers.
        Hide
        Eric Westfall added a comment -

        This is not a blocker anymore, reducing to critical.

        Show
        Eric Westfall added a comment - This is not a blocker anymore, reducing to critical.
        Hide
        Eric Westfall added a comment -

        I don't think there is really much more work to be done on this besides what we will discover as we go along. Essentially, the embedded metadata into the data dictionary that jonathan implemented a long time ago satisfies this jira.

        Show
        Eric Westfall added a comment - I don't think there is really much more work to be done on this besides what we will discover as we go along. Essentially, the embedded metadata into the data dictionary that jonathan implemented a long time ago satisfies this jira.

          People

          • Assignee:
            Eric Westfall
            Reporter:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

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

                Agile

                  Structure Helper Panel