Advanced Search - Specific Features and Reasons

This post provides an example of user scenarios, and example of successful UI for the advanced search filtering, to clarify the general request for advanced search.

Scenarios include where the user wants to find only parts...
1. with schematics
1.1 … created by SnapEDA
1.2 … created by manufacturer
1.3 … created by 3rd parties
2. with footprints
2.1 … created by SnapEDA
2.2 … created by manufacturer
2.3 … created by 3rd parties
3. with 3D models
3.1 … created by SnapEDA
3.2 … created by manufacturer
3.3 … created by 3rd parties
4. with simulation available
5. of specific package type (e.g., DIP, TSSOP, etc.)
6. that are { in stock, not in stock, no availability data }
7. with clean results from Verification Checker for { All, Manufacturability, Schematic, Documentation, Miscellaneous }

For the UI, any reasonable UI is possible. While enabling the advanced search to be fully specified via text in the search box is likely desirable, it may be easier for a first release to only allow the advanced search to occur after the initial search results have been provided.

In fact, here's an example UI using a sample of ~1000 random-generated (fake) data, using the above grid to show the results:
https://gist.github.com/henrygab/ef470d9273ec544086735b86ac630550/raw/f3f367f4b34be57c93e549421a90570427917906/example.html
(You can copy and paste that code directly, to try it out, at https://dojo.telerik.com/)

Of course, your particular technology choice may differ (may not be Telerik's solution). The UI exposed should have the following:
1. Ability to filter by multiple selections for a single column from a query result shown to the user
2. Ability to filter by multiple columns at one time

My sincere thanks for this great service!