Design experiment: We want to understand when/whether the "Search First" tab helps users
Opened this issue · 2 comments
What:
Could a search first design be useful for GSA privacy, ie, should we include this in our dashboard?
Could it be useful for a search that a member of the public might conduct?
What would that design look like?
For reference, here's our initial Search First prototype. Rough draft.
And here's an earlier mockup photo:
Acceptance:
- we understand whether "search first" would be useful for GSA privacy folks, enough to work on
- we understand whether "search first" might be useful for the public, enough for us to work on?
--> is it worth a mock? If no, STOP. If yes, then:
- we understand what users want from "search first" and so we can articulate what info it should retrieve (search among PII list? descriptions of PII, etc. - what type of information should it retrieve)?
- we have a mock
- we get feedback from intended user - GSA privacy or public depending on which we believe would use this.
Put some code up for this on our prototype at Search First. It is searching only in the PII column of all the systems. It returns the name of the system that has that PII in it.
What is interesting is that it is all client side. It loads all the csv data and indexes it on every page load, super fast. Someone wrote a clever computer science data structure that was perfect for this use. https://github.com/lucaong/minisearch
Not doing this for now.