final tagging tool
The concept as of now is that the final product will tag files as they arrive and ad a quality indicator to their headers. This is a rather generic approach which could be used for all fits files.
For now, it would be sufficient to run the tagging on all files currently available in the archive (up to end of 2019) afterwards, we should talk about automating chrotel tagging and importing.
The final tool produced by development in chroquest should be a tagging tool that takes a file as an argument and returns the corresponding quality tag. Points that need to be adressed ahead are:
-
Writing permissions for /archive/chrotel
@guenter : Is it okay if I just have those? -
Keyword for quality tag, check if there are any standards or recommendations in place (SOLARNET, FITS) -
History Entry: Should a history keyword be added to the file if the only change is tagging and adding a KEYWORD?