Finally finished with todays update, took me a bit longer than expected :(
- Added download of partial votables, still needs testing and work to clone it, this means doing SELECTIONS affect the original object to a point that if the unmodified voTable is downloaded the user will get the modified version as well
- Changed colors again, tell me what u think marco
- Removed uncessary text from splash screen
- Fixed small problem on select rows the counter was losing the css
- Removed a couple of debugs left that were breaking the code
- Chaged the date persistance completly to depend on cookies instead of an internal variable.
- Added the _Blank on downloads so that it wont pop up the dialog to navigate away from the page
- Added a jquery plugin to deal with setting cookies easier
Hi! we (here in Trinity) have used HFE today and we have certain comments regarding to usability. To track them separately they are post in independent comments.
ReplyDeleteHave a good day!!
1) When saved events which have just one date entry, the times of the events are not saved making impossible to parse them to a different query.
ReplyDeleteWe've tried this with different catalogues, for example cme_cat. Our suggestion is that a starting time and end time are filled with the time provided by the result, but showing a warning that st_time and end_time are the same. This will allow to the user to choose which range (s)he wants.
2) Label field, when saved, is not shown properly on the history bar. At least if it's longer than certain length.
ReplyDeleteSuggestion: maybe a mouseover showing the name and number of results (as in previous version) helps to quickly review what is in where...
3) Text boxes are bit tricky. They don't allow to select the text inside or to place the cursor in any place, just at the end. For example, if I want to change the year on a time query I have to move the cursor with the arrow keys. This could result quite annoying.
ReplyDelete4) When saved the results from the ICS, there's always the time icon, however it works also as an instrument... could that icon be like a mix between the both? so it's clearer that it can be used either as a time range or as an instrument selection.
ReplyDelete5) There is some instruments duplicated on the DPAS shown on the HFE but not on the stand alone service.
ReplyDeleteI've reported this on DPAS blog too.
6) Would be good if the DPAS could show thumbnails of the results as SDC does for Hinode. At least, it could provide a link to the SDC page for that result.
ReplyDeleteThe link can be easily generated from the file name of Hinode/EIS. For example:
eis_l0_20070123_132644.fits.gz
would be linked with the thumbails on:
http://sdc.uio.no/search/show_details?FILE=eis_l0_20070123_132644
This comment was also posted on DPAS blog.
7) when saved results from DPAS... same problem that reported for the HEC on point 1. The time is not saved, neither the instrument. In this case there is a starting and end time.
ReplyDeleteIt could be very useful because for a certain observation I could be interested in which events happen at that interval.
I've tried this just with EIS, which has a broad time interval (some files could contain hours of data).
8) We found more useful the bars as they were previously, history on the top and services on the left, because when you want drag results from previous queries they were closer to the working area. Now the last results go farther and farther down, so it maybe useful either to put the history on the other direction (ie. upper the newer stuff), or restrict that bar to a certain height and a up and down arrow.
ReplyDelete9) Regarding also to the buttons as in point 8, it would be nice to have the possibility on the history bar to show just results saved or queries, since the queries history helps to the user to understand what have been done, this could be made showing small icons of the queries besides (or above) the saved results icons.
ReplyDeleteand to don't leave this with just 9...
ReplyDelete10) There is a real need of the CXS to be on the HFE. Otherwise we are lost on the results without having some context. This has also been posted on the CXS blog.
an important one for those that don't have a big screen.
ReplyDelete11) After a query, the results appear below the query form... but it is unnoticeable if the screen is not big enough. I would suggest to show some kind of 'warning' saying the number of results found just on right-hand-side of where the queries are done... it also could be an anchor link, so if you click there the page scroll down until where the results are.
thanks for the comments, they were all taken into consideratiom
ReplyDelete