Improve metadata experience for versioned entities
Description
Release Notes
None
relates to
Activity
Show:
Andreas Neumann December 4, 2018 at 6:21 AM
The most important metadata is for datasets,. Dataset currently are not versioned, and at the time that they are, it might be a good idea to support versioned metadata. Before that, there needs to be a clear understanding of what it means to have versioned metadata for an entity, versus metadata for a versioned entity,. For example, deploying a new version of an app, does it inherit the metadata from the previous version of the app? etc.
Currently metadata is does not belong to a specific version for a versioned entity like application/schedule/program.
This is to extent is acceptable but the problem arises while serving search queries. Since the version information is not retained for metadata while serving the search result the only entity a which gets to user is default version even though there are other version which have the same metadata.
At the least we should include all versions in the search result or somehow signify that there are multiple version of the matched entity rather than returning back the default versioned entity.
Ideally we should provide feature for adding metadata across all version or to specific version and retain the version information and serve them back accordingly.