| Summary: | Handle Google Books API requests for OPACSuggestionAutoFill on server side | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Katrin Fischer <katrin.fischer> |
| Component: | OPAC | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | victor |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Crowdfunding goal: | 0 |
| Patch complexity: | --- | Documentation contact: | |
| Documentation submission: | Text to go in the release notes: | ||
| Version(s) released in: | Circulation function: | ||
| Bug Depends on: | 14242 | ||
| Bug Blocks: | |||
|
Description
Katrin Fischer
2022-05-14 14:59:21 UTC
Do we have other stuff where Koha acts as a proxy? If the GDPR was really enforced well, using a proxy would be an obligation since there is a reasonable solution to avoid altogether sending personal data to a 3rd party. Then just notifying the user is invalid since it's forcing them to accept a personal data transfer to use the feature when it's in fact unnecessary. When GDPR was coming up, I recall it was talked as having that impact. But obviously is a matter for enforcement to have an actual proceeding of a given complain. And then to have enforcement authorities decide that a data processing is unnecessary because there is a reasonable technical solution to avoid it and provide the same service. |