Document for tracking the changes in metadata

[bhsi-snm]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] As the flow of metadata is being populated over different services, it is important that there a clear way to track the changes that are happening when and where.

Describe the solution you'd like A clear and concise description of what you want to happen. The Way to do that is to have a tabular document which I have created under Documentation/Metadata_tracking.md https://github.com/NHMDenmark/DaSSCo-Integration/blob/main/Documentation/Metadata_tracking.md -- dead link

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

EDIT: Split the tables into separate files: https://github.com/NHMDenmark/DaSSCo-Integration/blob/main/Documentation/Metadata_fields.md

https://github.com/NHMDenmark/DaSSCo-Integration/blob/main/Documentation/Track_fields.md

[bhsi-snm]

@ThomasAlscher1991 can you please fill up the metadata populated in ingestion client

[ThomasAlscher1991]

Just updated the table. NOTE: Derivatives don't repopulate the metadata fields but rather create a copy form the parent asset and subsequently create a new asset. The only field populated in this case is "parent_guid".

[Baeist]

Further updated the table. Included the tracking data that is specific to the integration server. @bhsi-snm