dhis2-devs team mailing list archive

[Murodullo Latifov <murodlatifov@xxxxxxxxx>]

Hi Jason,

Thanks for clarification. I understand importance of validation. We have trouble 
with duplicates, etc. We have few OrgUnits, and have mach more Data Elements say 
compared to India, so cases vary.  Looking at all these I am thinking it would 
be better to have  expandable System Settings, which would allow us to customize 
regex for  each implementation providing default. This would allow to say 
translate or do not translate OrgUnits, validate or do not validate shortnames, 
etc instead of removing existing feature.

regards,
murod





________________________________
From: Jason Pickering <jason.p.pickering@xxxxxxxxx>
To: Murodullo Latifov <murodlatifov@xxxxxxxxx>
Cc: DHIS 2 developers <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
Sent: Fri, January 14, 2011 5:19:26 AM
Subject: Re: [Dhis2-devs] Some thoughts on improvement of DHIS2 customization

Hi Murod,

You can check out this blueprint regarding flexible regex validation. We have 
had a lot of discussion about this. 


https://blueprints.launchpad.net/dhis2/+spec/regex-validation

I developed  the blueprint in part from things that came up in Tajikistan while 
I was there, as well as from other places where the need for flexible in-field 
validation is required. 


It is a good point regarding the Cyrillic characters, where validation would 
likely need to happen on the server side, since Javascript is not well suited to 
validation of Unicode. 


Agree with the orgunit translation as well.  See...

https://blueprints.launchpad.net/dhis2/+spec/orgunit-translation
https://bugs.launchpad.net/dhis2/+bug/519175

Please see Lars response here..

http://www.mail-archive.com/dhis2-devs@xxxxxxxxxxxxxxxxxxx/msg04512.html

Regards,
Jason



On Thu, Jan 13, 2011 at 1:21 PM, Murodullo Latifov <murodlatifov@xxxxxxxxx> 
wrote:

 
>  
>
> 
> 
>Hi all,
>
>There are some issues I am facing with implementation. First OrgUnit is no more 
>localized as was earlier. Maybe this is good for some implementation, but not to 
>all, like we have multi language requirement here in Tajikistan. New 
>implementation of categorycombos does not have translation functionality.
>Another issue is use of validation rules for data entry using regex. Existing 
>regex for shortname does not validate cyrillyc letters (unicode), latin chars 
>(ANSI) are ok. 
>
>Looking at these two issues I suggest to create some sort of common service wich 
>accesses key/value pairs and that is used to determine behaviour of the system 
>or module. For above examples we could use global property of translate OrgUnit 
>or not. Or we could easily adjust regex to match our  needs.
>
>
>regards,
>murod
> 
>
>  
>  
>
>  
>  
>
>_______________________________________________
>Mailing list: https://launchpad.net/~dhis2-devs
>Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~dhis2-devs
>More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+260968395190