LPP » INSTRU » QLop » SciQLOP

One way to deal with fact that all missions are different but have some similarities would be to describe all data products in virtual file system. For example you would be able to get Cassini FGM data through "/CASSINI/MAG/FGM" and at the same time it should allows you to get all data of one kind for a list of spacecrafts. Possible paths:

• "/CASSINI/MAG/FGM" should give access to Cassini FGM flux
• "/*/MAG/FGM" should give access to all spacecrafts FGM flux
• "/CASSINI|CLUSTER/MAG/FGM" should give access to Cassini and Cluster FGM flux

You should also be able to query and filter data, for example you may ask for all electric field data but only time series with a sampling rate higher than 1kHz.

The solution may be to describe this in XML format, now we need to choose which attributes we need to describe everything.

Some random ideas:

The spacecraft node should be described correctly.
All data products description should at least contain:

• The link to download them, it need to be flexible and multiple(allow mirrors). We can embed JavaScript rules to generate URLs from time windows.
• The DATA geometry, is it a vector, a picture or something else?
• The unit, no unit is one possible value.
• The product name we expect to see in the cdf or tab header.
• The list of sampling rates.

This solution has the big advantage to reduce code maintenance and put most information out of the code and allow users to add product/missions/mirrors and tweak them.