dhis2-devs team mailing list archive

[Knut Staring <knutst@xxxxxxxxx>]

On Wed, May 26, 2010 at 11:05 AM, Knut Staring <knutst@xxxxxxxxx> wrote:
> On Wed, May 26, 2010 at 10:49 AM, Hynek Kruzik <kruzik@xxxxxxxxx> wrote:
>> Public bug reported:
>>
>> I suggest to imporove general functionality of listings (like list or
>> indicators or list of data elements). I found current behavior quite
>> annoying:
>>
>> 1. Filter and position is lost after modifying element details - if you
>> need to maintain for example large number of data elements, current
>> behaviour is really not very useful
>>
>> 2. I would also suggest to extend filtering options so the user can use
>> more fields than just a name = for example, short name, alias name and
>> code would be very usefull.
>>
>> 3. Paging option in long listings will be also very usefull, currently
>> we have about 8 000 organizational units and assigning them into groups
>> is really a paintful job.
>
> This does relate back to the earlier forays into
> http://datatables.net/, where pagination (3) and multicolumn filtering
> (2) comes out of the box - especially as long as everything can be
> sent to the client. The question is how to have a good division of
> labor with the server - as I'm not sure we would want to have the
> browser tackle 8000 rows on the client (though that is what we do
> today, right?).

When using server-side processing, DataTables will make an XHR request
to the server for each draw of the information on the page (i.e. when
paging, sorting, filtering etc) and expect JSON back. I suppose this
would be the way to go for big lists (but unnecessary for ones -
should we just hardcode the choice?)

http://www.datatables.net/usage/server-side

k

-- 
Improve listings to keep used filters and position and to offer more search options
https://bugs.launchpad.net/bugs/585758
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.

Status in DHIS 2 - District Health Information Software: New

Bug description:
I suggest to imporove general functionality of listings (like list or indicators or list of data elements). I found current behavior quite annoying:

1. Filter and position is lost after modifying element details - if you need to maintain for example large number of data elements, current behaviour is really not very useful

2. I would also suggest to extend filtering options so the user can use more fields than just a name = for example, short name, alias name and code would be very usefull.

3. Paging option in long listings will be also very usefull, currently we have about 8 000 organizational units and assigning them into groups is really a paintful job.

Thx