I'm very impressed with HELIO, the overall system design and the development approach. I do have a few suggested improvements for HELIO:
** On the event catalog have selections within a checkbox lists be "or" and between lists an "and". Currently both are "and".
** Checkbox placement is opposite in HEC and ICS. Checkboxes should precede the label. Same true for ILS. Checkbox is before the label in other cases (and in IDL as well.)
** Add quotes to field names to ensure they are SQL safe.
** ILS provides daily cadence for location. This should be noted on the service page.
** HFE - place a submit (search) button in the main form as well as at the bottom of the field list to minimize scrolling after search parameter entry.
** HFE - toolbar buttons should differ in appearance from the "memory" buttons which appear in the left column. The pointed shape give the impression of a sequence of step or breadcrumb style history.
** HEC should limit view of lists based on intersections with time.
** HEC - Need sorting capability for returned tables. Allow sorting on any field.
** Using HFE ICS with a observatory constraint of "stereo" had zero results. Observatory name must be an exact match. This isn't always desired.
** Using HFE ICS - The Observatory name has a dash (stereo-a) whereas the obsinst_key has an underscore and is preceded by observatory name (stereo_a_swea). This makes it difficult to search for items based on instrument name. Since there is an Observatory name field the tendacy is to enter just the observatory name in one field and instrument it the other. Its possible to combine the two in the service and to convert the dash/underscore convention. However a consistent use of dash and underscore would be desirable since both values are displayed to the user.
** HEC - add "Select All" button for result table.
** DPAS - add "Download All" for quick acquisition of data or "Select All" for placing all items in a shopping cart (Save Selection)
** DPAS - save select creates an output data save set with no functional capability (blank dot). This is a "shopping cart" of data. It could be droppped on a download service (new) or from the result view page add capability to download or create a wget/curl script that the user can run from a local system.
I'm very impressed with HELIO, the overall system design and the development approach.
ReplyDeleteI do have a few suggested improvements for HELIO:
** On the event catalog have selections within a checkbox lists be "or" and between lists an "and". Currently both are "and".
** Checkbox placement is opposite in HEC and ICS. Checkboxes should precede the label. Same true for ILS. Checkbox is before the label in other cases (and in IDL as well.)
** Add quotes to field names to ensure they are SQL safe.
** ILS provides daily cadence for location. This should be noted on the service page.
** HFE - place a submit (search) button in the main form as well as at the bottom of the field list to minimize scrolling after search parameter entry.
** HFE - toolbar buttons should differ in appearance from the "memory" buttons which appear in the left column. The pointed shape give the impression of a sequence of step or breadcrumb style history.
** HEC should limit view of lists based on intersections with time.
** HEC - Need sorting capability for returned tables. Allow sorting on any field.
** Using HFE ICS with a observatory constraint of "stereo" had zero results. Observatory name must be an exact match. This isn't always desired.
** Using HFE ICS - The Observatory name has a dash (stereo-a) whereas the obsinst_key has an underscore and is preceded by observatory name (stereo_a_swea). This makes it difficult to search for items based on instrument name. Since there is an Observatory name field the tendacy is to enter just the observatory name in one field and instrument it the other. Its possible to combine the two in the service and to convert the dash/underscore convention. However a consistent use of dash and underscore would be desirable since both values are displayed to the user.
** HEC - add "Select All" button for result table.
** DPAS - add "Download All" for quick acquisition of data or "Select All" for placing all items in a shopping cart (Save Selection)
** DPAS - save select creates an output data save set with no functional capability (blank dot). This is a "shopping cart" of data. It could be droppped on a download service (new) or from the result view page add capability to download or create a wget/curl script that the user can run from a local system.