|
|
# Archive Team Header Policy
|
|
|
|
|
|
## Requirements
|
|
|
|
|
|
The main data we are interested in in relation to the Archive is the ***science ready level1 FITS data***. This is what we use as a source to describe observations, accordingly our descriptions can only be as precise as the headers of the files. The question we ask to determine whether a specific header format is sufficient for our purposes is:
|
|
|
|
|
|
> Does the header contain all information to completely describe the underlying observation solely from it's constituent FITS files?
|
|
|
|
|
|
This is the paramount requirement that ***must*** be fulfilled for a successful integration into our archive. Further specifications can make the data more interoperable and easier to deal with, but if this requirement is not fulfilled, it is a total showstopper. In this context *completely* is meant to indicate the full set of fields of an [observation description](standards_and_references/Mandatory-Fields-for-Observation-Descriptions). They include, but are not limited to:
|
|
|
|
|
|
* Observation: Is it possible to find the unique parent observation solely from the header?
|
|
|
* Coordinates for the observation: Which part of the sky/the sun is covered?
|
|
|
* Temporal coverage: When does the observation start and end?
|
|
|
* Spectral coverage: Which wavelengths are covered by the observation?
|
|
|
|
|
|
## Explicit Recommendations
|
|
|
|
|
|
Any file structure that satisfies the requirement above is formally fit to be integrated into the archive. In practice, it makes sense to further specify these requirements both as a way to enhance interoperability and as a way to provide a proven structure to which new instrument concepts can adhere.
|
|
|
|
|
|
### Header Structure
|
|
|
|
|
|
### File naming conventions
|
|
|
|
|
|
This is only one of the benefits of well-structured and well-defined headers. Additional benefits are:
|
|
|
* Interoperability: Third party tools that follow the same standards are compatible with your data
|
|
|
* Attractiveness: Data that is easier to use and understand is more attractive for others to use and will thus higher scientific impact.
|
|
|
|
|
|
When dealing with potential files to integrate into the archive, we distinguish between on the one hand old files from existing archives and possibly discontinued instruments and on the other hand new instruments that are under development. |