I find it useful to be able to filter CDF resources by their source system.
How come Assets, Files and Events have a “source” attribute, while time series and events do not?
I assume then, that in order to properly filter by source for any resource type, it might be best to rather add “source” as a metadata key for any resource type, rather than use the attribute field which is not available for all resource types?
Btw., for the Relationships resource type, “source” has a different meaning than it has for Assets - I suppose this could cause some confusion?
Best answer by Thomas Sjolshagen
Hi and thank you for this excellent suggestion.
I’ve taken the opportunity to start a discussion internally (at Cognite) about the “source” parameter in general - making it available in Time Series and Sequences where it’s currently not - and proposed an update to the API documentation for the Assets, Events and Files instances of the property.
I’ve left the sourceType property in the Relationships API alone because I believe the description there is adequate and appropriate if/when the “source” property descriptions for “Assets”, “Events” and “Files” is updated to more clearly indicate the purpose of the property itself.
I’ve taken the opportunity to start a discussion internally (at Cognite) about the “source” parameter in general - making it available in Time Series and Sequences where it’s currently not - and proposed an update to the API documentation for the Assets, Events and Files instances of the property.
I’ve left the sourceType property in the Relationships API alone because I believe the description there is adequate and appropriate if/when the “source” property descriptions for “Assets”, “Events” and “Files” is updated to more clearly indicate the purpose of the property itself.