Reminder: Create & find trunk-related issues here. Legacy Trac tickets are still available. Problems? Workflow feedback? Need a module project? Open a support ticket.

OpenMRS Trunk

Merge Cohort Report Designer to Trunk

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Should Should
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: OpenMRS 1.5.0
  • Component/s: None
  • Severity:
    3
  • Keywords:
  • Description:
    Hide

    The cohort report designer needs to be merged to trunk so that users can take advantage of the xml reports. The concept-name-tag branch is technically in-line to be merged next, but seeing as the cohort-report-designer branch doesn't effect anything that concept-name-tag touches, it should be a simple merge.

    TRAC-1014 should be fixed before this merge is done.

    Show
    The cohort report designer needs to be merged to trunk so that users can take advantage of the xml reports. The concept-name-tag branch is technically in-line to be merged next, but seeing as the cohort-report-designer branch doesn't effect anything that concept-name-tag touches, it should be a simple merge. TRAC-1014 should be fixed before this merge is done.
  1. cohortReportDesigner.2.patch
    (395 kB)
    Burke Mamlin
    2008-12-05 02:15:05 EST
  2. cohortReportDesigner.patch
    (591 kB)
    Burke Mamlin
    2008-12-04 04:33:16 EST

Activity

Hide
Mike Seaton added a comment - 2008-12-04 04:32:49 EST

Attached find a patch as a replacement for the cohort-report-designer branch. This patch contains all necessary changes. To address the issues highlighted in the code review:

  1. Context.setVolatileUserData() - Removed this altogether, as it is not currently used and needs more thinking through
  1. DWRCohortService - Added comments as requested and removed use of "getCurrentEvaluationContext", instead substitution a new EvaluationContext.
  1. CohortReportFormController - This was not addressed. This is a new web controller, which works as designed and will likely be replaced down the road. If refactoring is desired here, we can open a new ticket.
  1. cohortReportForm.jsp - Fixed the tooltips to go back to default behavior since they were not working correctly. Will appear after short delay.
  1. reportSchemaXmlList.jsp - Changed this slightly as requested.
  1. User Interface (in general) - Added some instructive text to each Tab.

Patch attached.

Given that this has been code reviewed once, and touches very little existing code, I will plan to check this into trunk tomorrow pending comments.

Show
Mike Seaton added a comment - 2008-12-04 04:32:49 EST Attached find a patch as a replacement for the cohort-report-designer branch. This patch contains all necessary changes. To address the issues highlighted in the code review:
  1. Context.setVolatileUserData() - Removed this altogether, as it is not currently used and needs more thinking through
  1. DWRCohortService - Added comments as requested and removed use of "getCurrentEvaluationContext", instead substitution a new EvaluationContext.
  1. CohortReportFormController - This was not addressed. This is a new web controller, which works as designed and will likely be replaced down the road. If refactoring is desired here, we can open a new ticket.
  1. cohortReportForm.jsp - Fixed the tooltips to go back to default behavior since they were not working correctly. Will appear after short delay.
  1. reportSchemaXmlList.jsp - Changed this slightly as requested.
  1. User Interface (in general) - Added some instructive text to each Tab.
Patch attached. Given that this has been code reviewed once, and touches very little existing code, I will plan to check this into trunk tomorrow pending comments.
Hide
Ben Wolfe added a comment - 2008-12-04 13:07:43 EST

I'm satisfied with the wording additions to the jsp form, thanks.

I don't remember saying we should get rid of the getCurrentEvaluationContext(). I think we wanted to change it from getMyEvaluationContext() (which I did, to make it "current")

Show
Ben Wolfe added a comment - 2008-12-04 13:07:43 EST I'm satisfied with the wording additions to the jsp form, thanks. I don't remember saying we should get rid of the getCurrentEvaluationContext(). I think we wanted to change it from getMyEvaluationContext() (which I did, to make it "current")
Hide
Mike Seaton added a comment - 2008-12-04 13:25:52 EST

Thanks Ben, We can certainly tweak this wording going forwards. See my comment on the other ticket regarding the "getMyEvaluationContext" - it just isn't currently needed, and I didn't feel it should be added if it only adds unnecessary complexity.

Show
Mike Seaton added a comment - 2008-12-04 13:25:52 EST Thanks Ben, We can certainly tweak this wording going forwards. See my comment on the other ticket regarding the "getMyEvaluationContext" - it just isn't currently needed, and I didn't feel it should be added if it only adds unnecessary complexity.
Hide
Ben Wolfe added a comment - 2008-12-04 13:29:55 EST

Which ticket do you mean?

Other comment: wasn't the cohort builder using the setVolatileUserData() method for "temporary" storage of the users search history?

Show
Ben Wolfe added a comment - 2008-12-04 13:29:55 EST Which ticket do you mean? Other comment: wasn't the cohort builder using the setVolatileUserData() method for "temporary" storage of the users search history?
Hide
Mike Seaton added a comment - 2008-12-04 14:25:46 EST

I mean ticket TRAC-1146: ReportService - Initial Refactor

Yes, the setVolatileUserData() still exists, and is presumably still used by the cohort builder. It is no longer used by this patch / branch (since I took out the logic around "getMyEvaluationContext() / getCurrentEvaluationContext()". So, it should not be an issue that needs resolution for this to be merged into trunk.

Show
Mike Seaton added a comment - 2008-12-04 14:25:46 EST I mean ticket TRAC-1146: ReportService - Initial Refactor Yes, the setVolatileUserData() still exists, and is presumably still used by the cohort builder. It is no longer used by this patch / branch (since I took out the logic around "getMyEvaluationContext() / getCurrentEvaluationContext()". So, it should not be an issue that needs resolution for this to be merged into trunk.
Hide
Ben Wolfe added a comment - 2008-12-04 14:28:58 EST

Ah, didn't realize you refactored to take out the need for getCurrentEvalContext. Good work.

Show
Ben Wolfe added a comment - 2008-12-04 14:28:58 EST Ah, didn't realize you refactored to take out the need for getCurrentEvalContext. Good work.
Hide
Mike Seaton added a comment - 2008-12-05 02:17:44 EST

Changes committed to trunk in changeset rev:6193.

Final changes attached as patch cohortReportDesigner.2.patch

Code review document updated to reflect fixes. One new ticket raised - TRAC-1150 - for some additional refactoring work.

Show
Mike Seaton added a comment - 2008-12-05 02:17:44 EST Changes committed to trunk in changeset rev:6193. Final changes attached as patch cohortReportDesigner.2.patch Code review document updated to reflect fixes. One new ticket raised - TRAC-1150 - for some additional refactoring work.

People

Dates

  • Created:
    2008-08-29 18:49:52 EDT
    Updated:
    2010-07-08 16:21:18 EDT
    Resolved:
    2010-07-01 22:42:24 EDT