Metadata Discussion: higher-level config hierarchy #171
Description
Currently, the configuration structure supports two levels: parent configs and child configs. This works well for defining attributes and settings that can be inherited by related child configs. However, I can see use cases (for example IMOS datasets), where multiple parent configs should share common global attributes, such as citation, acknowledgement, disclaimer, etc. These can be common to many collection but could be overwritten by child configs for specifc cases if needed.
Benefits:
- Reduce duplication of common global attributes across multiple parent configs.
- Ensure consistency for dataset that should comply with the same metadata standards (e.g., IMOS).
- Make it easier to update shared settings in one place.
Example:
Level 1 (Granpa Config): IMOS
Level 2 (Parent Config): SRS, ACORN, etc...
Level 3 (Child Config): Specific collection config