Currently, our metadata endpoints provide two separate resources:
However, there is no mapping of which data fields are populated by each source. This association would improve transparency and make downstream analysis and integration easier.
Feature Request:
Add metadata or implement a solution that assigns/indicates which fields are populated by each source, so users can query or visualize the specific field coverage for every source.
Example Use-Case:
- Looking up a particular source in metadata will also show which fields it provides or affects.
- This will help with debugging, documentation, and client-side schema validation.
Requested Solution:
- For each data source, provide a listing of fields it populates, either through a new API endpoint or as part of existing metadata endpoints.
- Ideally, this mapping should be auto-generated/updated as new sources or fields are integrated.
References:
Currently, our metadata endpoints provide two separate resources:
However, there is no mapping of which data fields are populated by each source. This association would improve transparency and make downstream analysis and integration easier.
Feature Request:
Add metadata or implement a solution that assigns/indicates which fields are populated by each source, so users can query or visualize the specific field coverage for every source.
Example Use-Case:
Requested Solution:
References: