make sure that users aren't offered options (e.g. on file save) which won't work
visibility of solar services - should there be solar 'hot lists' in voexplorer
interface - accessibility issues
give operations specs for running the client UI - e.g. minimum system requirements and then java memory etc
system availability
mailing list - plus direct news feed to the vodesktop - inform users of outages etc.
Individual Components
VOExplorer
new version - issue of pre-canned lists
the vodesktop button - there will be changes to this - voexplorer/filemanager etc will appear in your start menu.
registry - our DSA will get registered as one entry - rather than multiple entries at present (KA)
in vo-scope - if you select more than say 10 'things' get a warning - 'are you sure?' - before displaying the actual data files.
how do you know that services are really working? e.g. CTIP service is up but the application doesn't work (incorrectly configured).
need sample test data - run a test
Query Builder
current version a good basis to start exposing to 'beta' users * screen space * comments * re-execution of 'error' queries
implementation of non-standard features? can we get more than 4 of the top 20 sdss queries working sooner - or do we wait for the ivoa stds process? Will it be possible to send 'native' sql to databases through our query builder? (in discussion - this would be a good idea - we'd have a DSA service which would accept native sql)
Task Runner
the error messages should get back to the UI
system availability
mailing list - plus direct news feed to the vodesktop - inform users of outages etc.
usable now - but go for a fuller release (say beta) in Apr 2007
Scripting
python scripting is in good shape - the 'astrogrid' package should be in the release.
Documentation
feature audit
annotation feeds - wiki to voexplorer - circumvents the registry - possibility to 'add value' - tag column should always be open.
describing the sorts of errors that we get from the system
service errors
system errors
lack of data
Server side components
Myspace --> Vospace - 1.1 is required.
we will have the 1.1 software available. Noel needs to know when this will be up for him to provide connects to.
1.0 std is going to be agreed at the Sept interop.
Registry component
Community with IAA
need to be able to access UKIDSS through VODesktop (use case - a belfast user registered with the manchester community would want to be able to query ukidss - without having to logon to any other community)
A roadmap of which AG server side components are going to be ready/ deployed is required in advance of beta release.
Timeline
pre-beta - current alpha jar files - can we get the release of that such that those that download it have to leave their contact details.
helioscope?
monitoring?
bundled release with taverna
package - vodesktop, taverna, topcat
need for another image viewer
adql - native pass through
Beta release - mid Jan - release the vodesktop with a range of user documentation.
after beta release - no new functionality - only bug fixes
deployment plan - how to get the AG initial set up defined.
aim for a full operational release at the NAM2008 - Apr 2008 in Belfast.