[KULRICE-9019] Like to have a way to fetch all valid TermSpecifications for a context Created: 22/Feb/13  Updated: 01/Jul/13  Resolved: 12/Mar/13

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.1.4, 2.2.2
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Critical
Reporter: Geo Thomas (Inactive) Assignee: Gayathri Athreya
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 17 minutes
Original Estimate: Not Specified

Attachments: Text File KULRICE-9019-Fixed-II.patch     Text File KULRICE-9019-Fixed.patch     Text File KULRICE-9019.patch    
Issue Links:
Fix
Relate
is related to KULRICE-9857 The changeset for KULRICE-9019 isn't ... Closed
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.



 Comments   
Comment by Gayathri Athreya [ 26/Feb/13 ]

Geo, the Rice 2.1.4 RC is coming out next week, we need to get this reviewed and committed asap if you want it. Is this patch final or are there additions?

Comment by Geo Thomas (Inactive) [ 26/Feb/13 ]

Yes Gayathri. Its the final one. Please patch it.

Comment by Peter Giles (Inactive) [ 27/Feb/13 ]

I clarified with Eric and any changes to a published service API need to be run by the KTI. This one is small enough that we can probably just send a message to the list informing them of the change.

Comment by Geo Thomas (Inactive) [ 28/Feb/13 ]

Hi Peter,
Thanks for the comments. I fixed those and attached the patch. Could you review it again and see if its good to go.
Geo

Comment by Gayathri Athreya [ 28/Feb/13 ]

attached the new patch to the review.

Comment by Peter Giles (Inactive) [ 05/Mar/13 ]

Ok, I emailed the KTI list to notify them about this change. That thread can (hopefully) be found here: https://groups.google.com/a/kuali.org/forum/?hl=en&fromgroups=#!topic/rice.kti/S0NVMp1pd8c

Comment by Geo Thomas (Inactive) [ 08/Mar/13 ]

Gayathri,
This is working as desired. Please resolve this.

Generated at Thu Nov 21 00:10:21 CST 2019 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.