You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a specific problem?
We just deprecated data_qualifier, joint_controller, retention, and third_country_transfers from Dataset. https://github.com/ethyca/fideslang/pull/146. The idea being that these more "legal" type fields don't belong on the data engineering construct: "dataset". Similarly, we have data_qualifier and retention on DatasetCollections and on DatasetFields. I assume these fields should be deprecated similarly in a follow-up @rsilvery
Describe the solution you'd like
Deprecate data qualifier and retention fields from DatasetCollection and DatasetField in fideslang.
I believe that data qualifier (identifiability) for both collection and dataset are also exposed in the UI.
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
From fideslang created by pattisdr: IABTechLab#149
Is your feature request related to a specific problem?
We just deprecated data_qualifier, joint_controller, retention, and third_country_transfers from Dataset. https://github.com/ethyca/fideslang/pull/146. The idea being that these more "legal" type fields don't belong on the data engineering construct: "dataset". Similarly, we have
data_qualifier
andretention
onDatasetCollections
and onDatasetFields
. I assume these fields should be deprecated similarly in a follow-up @rsilveryDescribe the solution you'd like
Deprecate data qualifier and retention fields from DatasetCollection and DatasetField in fideslang.
I believe that data qualifier (identifiability) for both collection and dataset are also exposed in the UI.
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: