Completing GSoC project tasks : GSoC Week 13

This week I completed the final task for GSoC 2013 which is providing a way to fix validation errors in Conecepts.

Before start work on that i changed the UI view of the validation error table, as instructed by my mentor and  now the error table displays the following information.


The when fixing validation errors in Concepts, for this i have used the Concept Id and once the user need to fix the error it will redirect user to 'Edit Concept' page like shown in the image below.

With this i have successfully finished the work schedules for the GSoC 2013 project this summer under 'Validation Module Enhancements' project.  My mentor has review the final task and provided some feedback, which needs to be modified. Therefore i will be working on that as well as work on documenting during the last  week of the project before 'Hard Pencil Down Date'.

Starting 'Fix Validation Errors in Concept' : GSoC Week 12

This week i first started on trying to implement 'fixing validation errors in concepts' task. However as this is the final task for my GSoC project this time, i then decided it would be better to discuss the next steps with my mentor before we proceed. Therefore both of us had a detailed discussion on the next steps of the project.

The following are the things we agreed on finishing in the remain time.

1. In validation error table it currently displays a string of error key. We are going to change this as getting an OpenMRS Object as key and display the Object id: UUID as the first column information.

2. The fixing concepts errors option would be implemented as, when the user clicks Fix link, a new window would pop up which has the concept edit page for the given concept id. We are going to edit the Concept here, and save it back to the database.

Therefore i have started with these two points in this week and will be finishing them in coming two weeks.

Finalizing Validation Report Display : GSoC Week 11

This week i have completed VM-4 , Displaying Validation Error Report, with finishing both error views: Class and Error views.

In class view the validation errors are sorted under the class name as shown in the image below.

In error view validation errors are sorted under the error name as shown in the image.

After getting feedback from my mentor on this ticket, i will be starting my final feature of GSoC 2013, which is Fixing Validation Errors in Concepts, hopefully from next week.

Completing the display errors based on Class type: GSoC Week 10

This week i first completed the code which displays the validation errors based on Class name. I have been able to display the Class errors in a table where the errors are displayed under each class as Error id and the Error description as follows.

After that  i worked on correcting the code written for this feature, after getting the code reviewed from my mentor Wyclif. There were also some feedback for Stop Validation feature and therefore i had to correct them all in this week too.

Categorizing the validation errors based on class : GSoC Week 9

As i had created the layout of the Report page which will be used to display the generated validation report last week, this week i coded to get a combined Map of validation errors along with  having Object type's Class name as they key of the Map.

So i have implemented for iterating via all the detected validation errors and comparing the Class name the similar set of errors are pu into a single collection and final validation error Map is generated.

Then after using that Map, the errors are displayed in the 'Class View' tab of the report page as a table as sketched in follows.

Class Type	Error Name	Description
Concept	Duplicate Name Exception	A is duplicated in Concept "B"
	Duplicate Name Exception	C is duplicated in Concept "B"

Currently i am having some issues in displaying this in the page, and that is why there is no screenshot of the yet. I will be publishing the screenshot in my next week blog once i fix all the bugs regarding the task.

Group and Display Validation Errors : GSoC Week 8

After passing the mid evaluation, this week i started working with ticket VM-4 which is display the error report produced in validation.

To view the validation report, you have to click the 'Show Report'. Then you are redirected to Report page where the validation errors are displayed in a tabbed pane whch has two tabs.

1. Class View tab : This displays the error list based on the Error class
2. Error View tab :  This displays the error list based on the Name of the error.

As the initial work i created the tabbed pane and got the errors  list into it as displayed in the snapshot.

Here Comes the Mid Term : GSOC Week 7

This week is the mid evaluations week in GSOC 2013 and today is the last date for mid evaluation submission. (Feeling excited :D)

This week what i basically did was making sure that all my previous codes work and all the documenting is made. Then there was the mid term presentation at the weekly developer forum for my project and i presented the tasks i have done so far.

You can find the PDF of the presentation in here.

In the last days of the week, i discussed the next task of the project with my mentor Wyclif. The next task is 'Grouping validation errors based on class type or error type'. I am going to start it coding today and progress will be updated next week :)