Chicago / metalicious

An open source data dictionary which can be deployed to track the metadata of one or more databases.
Other
65 stars 22 forks source link

Improve the search functionality to improve filtering #16

Open tomschenkjr opened 10 years ago

tomschenkjr commented 10 years ago

While the data dictionary was designed to be driven primarily through a search box, we need to improve advanced search filtering.

The most basic aspects of the functionality would be to add filtering for 'database', 'table', or 'field' results.

jpvelez commented 10 years ago

Would also improve search usability to make the search bar even bigger and more central, and to have autocomplete.

derekeder commented 10 years ago

Browsing http://datadictionary.cityofchicago.org/ 7 of the 11 business function categories contain no datasets:

It would be useful from a discoverability perspective to either hide these empty categories, or display the number of datasets associated with each one on the home page.

screen shot 2014-01-15 at 11 11 56 am

gregsanders commented 10 years ago

Right on, Derek. This would be an improvement, and a worthy endeavor. ...Not yak shaving at all. Almost snarfed up my morning cup of mountain tea at "yak shaving"! (in your other post). Never heard that one.

----- Original Message ----- From: "Derek Eder" notifications@github.com To: "Chicago/metalicious" metalicious@noreply.github.com Sent: Wednesday, January 15, 2014 11:13:02 AM Subject: Re: [metalicious] Improve the search functionality to improve filtering (#16)

Browsing http://datadictionary.cityofchicago.org/ 7 of the 11 business function categories contain no datasets:

• 311 
• Buildings housing and property 
• Business and economic development 
• Infrastructure and public works 
• Parks and recreation 
• Places and boundaries 
• Public safety 

It would be useful from a discoverability perspective to either hide these empty categories, or display the number of datasets associated with each one on the home page.

screen shot 2014-01-15 at 11 11 56 am

— Reply to this email directly or view it on GitHub .