Open joerg-halo opened 3 years ago
Current status of the database: Auxiliary data can be uploaded, e.g. pdf files. However, the structure of these stored files is not adequate, because required metadata can't be stored, e.g. the assignment of a flight protocol to a specific flight.
To me "access to auxiliary data [...] e.g. forecasts" sounds way more sophisticated that "uploading a few extra PDFs". The first one feels more like a big toolbox of interlinked data, nice visualization tools, possibilities to make correlations of measured and predicted data etc... The second one feels more like a "dropbox"-link.
Could you elaborate a bit on what your idea of auxiliary data is?
I rather had the second one in mind: Storing some pdfs in a way that they are easily found. So that a flight protocol can be easiliy found when dealing with data from the corresponding flight.
If you want, @d70-t, we could extend this use case to the first case, adopting the effort label. Do you think that there is a demand for this in parts of the HALO community?
Hmm, I don't think that a separate use case is required for "real" auxiliary data. That could likely be treated just as normal data. If at some point good metadata schemes are in place and online visualization works as well, than that should be perfectly covered anyways.
A place for reports / pdfs / nice pictures and linkage to the individual datasets (as proposed here) is a good addition.
Alright, @d70-t, I adopted the effort label - sorry, it took me quite some time to come back to this use case...
As scientific user I want to access auxiliary data to a HALO flight, e.g. forecasts. Thus, I want to obtain a broader picture of the flight I am interested in.