What kind of anonymisation needs to be applied to the data before it can be used?

Anonymisation is under the responsibility of the data provider and should be applied in case the data product includes personal data that fall under the GDPR legislation.

The anonymisation type can be agreed with the data consumer in the dataset policy.

Related Questions

Are there audit trails or monitoring tools currently used to track data lineage and reuse across the LDS infrastructure?

Can or will services like anonymisation or translation be offered on the LDS side to help potential data providers get their data in publishable condition?

How does the LDS account for data quality and ensure data is not synthetic? Is there a system in place to gauge the quality of a resource?

How will data compliance, rules and guidelines be enforced?

How will sensitive data, like healthcare data, be handled? Will there be additional security measures?

Should the responsibility for monitoring and enforcing license compliance rest primarily with the operators of open data portals?

What frameworks or methodologies will be used to track the origin, versioning, and individual contributions to language datasets?

What mechanisms are in place to ensure that licensing conditions are respected when language data is reused or redistributed within the ecosystem?

Will data providers be held responsible for not violating intellectual property rights or containing personal information/data in their datasets?

What kind of anonymisation needs to be applied to the data before it can be used?

Related Questions

See also