=======================================================
Minutes from NPM Diagnostic Tool session
EGEE JRA4 Face to Face meeting, Edinburgh, 12 July 2005
=======================================================

Present
-------

DANTE:  Loukik Kudarimoti (LK)
DL:     Mark Leese (ML)
UEDIN:  Ahmed Abdelrahim (AA), Ratnadeep Abrol (RA), 
        Alistair Phipps (AKP)

Actions
-------

[RA] Add maxresults to entry form
[RA] Add scale changes/zooming in to result graph as 'should' requirement

Minutes
-------

The client has been set up to display as much valid information as possible so
the user can only construct a valid request.

Request flow:
1) Enter time period
2) Select source
3) Select destination
4) Select metric
5) Select parameters

Other request flows are possible, but everyone happy with this order.

There is a need to highlight invalid values lower down on later edits.

If fields cannot be gathered from the framework (e.g. statistic - capability
query not supported), just display all possible values (configurable fallbacks
that are based on our requirements and are available in the NM-WG schema), but
should warn the user that this has occurred, if possible (to be considered).

LK/ML agree that form is simple enough, but a quick start guide should be
written.

RA had considered using multiple pages instead of a single page, but each page
would be very small.  All agree that the single page is better.

RA points out that page refreshes are required but ML does not think this is a
problem - could help users get feedback about interaction.

'maxresults' is not currently present on the form, but must be added.  We should
also allow a time focus to be specified (and +/- time tolerance).

Possible UI (ML):

        maxresults [______]             -time
                                     - [______]
    Start     End            Target
0  [______] [______]  |  0  [______]    +time
                                     + [______]

There is an issue with how we map the Target time to Start/End time
specification.  ML thinks this is defined in the schema requirements but thinks
half way between start and end time will be suitable.

Clickable areas on the result graph (image) would be very useful, if possible.
e.g. to zoom in to sections of the graph.  This will be added as a 'should'
requirement.  For now the query can be edited.

AKP 15/7/2005