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

Like to have a way to fetch all valid TermSpecifications for a context

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.4, 2.2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-6491Add validation to TermSpecification maint doc based on existing TermResolvers
      KULRICE-832RuleXmlParser inefficiently fetches all rules
      KULRICE-5723Make sure that we validate that everything within an agenda is valid within that agenda's context
      KULRICE-6662Apply sql for permission to the Term,TermSpecification and Context to master DB
      KULRICE-7626Expose relationship between Context and TermSpecification at the DTO level
      KULRICE-11373Module configurer changes required to have both the module spring MVC and the module services in the same context
      KULRICE-886ServiceLookup Context Object to fetch services through service locators and Return a LocatorResult instead of object from both getObject and getService from locators
      KULRICE-918Need a way to add context to value finder classes
      KULRICE-3882JPA: discover JPA cascade/fetch option mappings vs OJB(auto-xxxx/proxy), find out what conversion scripts have done and will do for it
      KULRICE-3653No context-sensitive help available for Rice documents
    • Rice Module:
      KRMS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Pending Review
    • Include in Release Notes?:
      Yes

      Description

      It would be really useful for KC to have a new method in KrmsTermRepositoryService to fetch all TermSpecifications for a context. It will provide more flexibility for us to know the TermSpecificationDefinitions before hand and can build the facts using those term keys. One of the user requirement in KC is to create Terms by using Document properties. We can easily achieve this by using reflection if know the Terms while building the facts.
      I have done this work locally and tested in both Bundled and Embedded mode.
      Peter,
      Could you take a look at the patch and see if its appropriate to commit the fix form our side. If you have any other suggestions to get the TermSpecifications for context in any other ways, please suggest that too.

      1. KULRICE-9019.patch
        3 kB
        Geo Thomas
      2. KULRICE-9019-Fixed.patch
        3 kB
        Geo Thomas
      3. KULRICE-9019-Fixed-II.patch
        3 kB
        Geo Thomas

        Issue Links

          Activity

          Gayathri Athreya logged work - 28/Feb/13 5:30 PM
          • Time Spent:
            17 minutes
             
            Review by Gayathri Athreya

            People

            • Assignee:
              Gayathri Athreya
              Reporter:
              Geo Thomas (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 17 minutes
                17m

                  Structure Helper Panel