Skip to content

Latest commit

 

History

History
56 lines (29 loc) · 4.32 KB

findme.md

File metadata and controls

56 lines (29 loc) · 4.32 KB

Find Me Button (Use Case 1)

Under UK GDPR and the Data Protection Act (2018) we all have the Right of Access, and the Right to Rectification, among the other individual rights.

UK Civil Service consists of 449 department, agencies and public bodies. They operate largely independently and so to exercise the Rigth of Access we would have to contact all of them independently.

The Idea

How about a search page with a 'find me' button?

Find Me Button

 

With a single click, all the departments' data would be interrogated and the results presented in an aggregated fashion, something like this:

 

Found Me Page

Instead of very similar results from all departments, the results could be presented as a single record, perhaps with variations. This covers the Right of Access.

If we were now able to offer the user a chance to select the current address (out of the known ones) or perhaps update the details and send them back, that would cover the Right to Rectification.

The Challenges

This very simple to visualise use case presents significant challenges. But it does show what could be possible if the technology I want to explore with the ODIS worked as I hope it will.

Data Security (on read)

Of course, to do something like this, we would need to have the ability to trust the user's identity. It really must be 'find me' not 'find anybody' button. There is ongoing work on the UK Digital Identity and Trust Framework.

With a federated search approach, the source information never would have to leave the systems in which it is stored until it is requested by the user, one at a time. This solution could be potentially much safer than any centralised data storage.

Data Security (on write)

The ability to update the data would have to be carefully managed. Perhaps, rather than allowing direct updates, a suggestion for a change should be recorded and delivered to the source system, to be processed at a later date.

To avoid user disappointement, suggestings would have to be retained somewhere in the search network, so that they can be shown, before the source system gets updated or the change is rejected.

Data Aggregation and Entity Mapping

Result aggregation is essential from the usability point of view. The results will have to be aggregated and only differences highlighted. What to do with differences in data model exposed by the source systems?

One option could be to request standard representation. Automatic mapping could be considered, perhaps with the search network learning about different models and their relationships over time.

As I am thinking about it right now, the search is about searching entities in semi-structured or structured models, not unstructured content. But unstructured content could be shown as links.

Data Moderations

Not every department will respond with all the details, but still, all may need to have updates. In the process of data moderation, it should be possible for departments to either return varying degrees of detail or simply confirm/deny it has the data. Perhaps, an option for a department to register interest in updates without indicating whether they have the data could be helpful.

Search in off-line data

The adoption of such a solution in all 449 departments will take forever or longer. It might be difficult, especially since some of the data might not be in digital form. Perhaps the search could be extended to support long term requests.

To be continued...