Beta-test the City of San Jose's open data portal
Opened this issue · 17 comments
Background:
The City of San Jose is in the process of re-launching its open data portal.
http://data.sanjoseca.gov/home
The Challenge:
Help the City of San Jose beta-test the data portal by trying to perform various functions.
- Find a dataset of interest. What is in the dataset? How big is the dataset?
- Access the dataset of interest using your method of choice (browse in the portal, download to your computer, write code using the API)
- Analyze the dataset using your tool of choice (spreadsheet, statistics program, write your own code)
Provide a summary of your experience, what you found intuitive or difficult about the task, and any other feedback you have for improving the user experience. You can send your feedback by commenting on this issue below, or typing it in this Google Doc.
Bringing up http://data.sanjoseca.gov/dashboards/9388/quality-of-life/ as well as the tabs is taking longer time than expected.
Drag and drop to arrange clauses.Remove all
<% var columnFieldValues = this.dataStream.get('columnFieldValues'), columnId = column.split('column')[1]; switch(modif){ case 'A': modif = gettext('VIEWDS-SORT-ASC-ORDER'); break; case 'D': modif = gettext('VIEWDS-SORT-DESC-ORDER'); break; } %>
x <%= gettext('VIEWDS-COLUMN-TEXT') %> <%= columnFieldValues[columnId].headerText %>: <%= modif %>
consistency issues : datasets Vs Datasets Vs DataSets
Testing Links
The following tabs lead to the same page: Open Government (seems to be a right link), Public Meeting (the link should instead direct to http://www.sanjoseca.gov/index.aspx?NID=226)
Links Aren't Functional on http://data.sanjoseca.gov/developers/ #65
Online Support and Get Your API Key ! links aren't functional yet.
(@radhikapc, I tried the links above from a Google Chrome browser window and they worked for me. They resulted in pop-up windows. -@mthong)
Filtering data is giving errors:
http://data.sanjoseca.gov/dataviews/225701/labor-force-and-unemployment-rates/
<% switch(operator){ case '0': // = case '3': //!= case '1': // > case '5': // >= case '2': // < case '6': // <= case '4': // contains any case '13': // contains all case '9': // not contains all %>
Value:
Enter value
<% break; case '7': // between case '10': // not between %>
Value 1:
Enter value
Value 2:
Enter value
<% break; case '8': // in list case '11': // not in list %>
Values:
Enter values
Values must be comma separated.
<% break; case '12': // unique value %>
Values:
<% break; default: break; } %> - See more at: http://data.sanjoseca.gov/dataviews/225701/labor-force-and-unemployment-rates/#sthash.kjumzkqo.dpuf
Filtering data is broken at http://data.sanjoseca.gov/dataviews/225701/labor-force-and-unemployment-rates/
http://data.sanjoseca.gov/dataviews/225564/employee-compensation-2015/
Filtering data in Employee Compensation 2015 should have more options. Greater than, smaller than, and between operators are not available for use.
Filtering issues at http://data.sanjoseca.gov/dataviews/226206/affordable-housing-under-construction/
Giving partial values/ uppercase does not return correct value
After running an operation, the filter box goes unfunctional.
Filtering not functional. String search returning incorrect results
Multiple Sorting is not functional
Filtering is broken at http://data.sanjoseca.gov/dataviews/226207/affordable-housing-family-housing/
Another broken option. It seems like filtering and sorting in general need some treatment.
Nothing to view in Custom View
Animal Hospital Receptionist Resume displayed in the Help Site on Code for San Jose:
Error sending email. Not functional. 
Using the API for the datastreams in an app is not very intuitive. The returned json object has the meta-data in its own key-value set, but the actual data is in an array like this:
[
{
"fStr":"header1",
"fHeader":TRUE,
"fType":"TEXT"
},
{
"fStr":"header2",
"fHeader":TRUE,
"fType":"TEXT"
},
{
"fStr":"Value1",
"fType":"TEXT:
},
{
"fStr":"Value2"
"fType":"TEXT"
},
{
"fStr":"Value3",
"fType":"TEXT:
},
{
"fStr":"Value4"
"fType":"TEXT"
}
]
In the data, every cell is at an equal footing, making no distinction between rows and columns. There is the property "fRows" and "fCols" to help us count out where everything should be, and header cells have a "fHeader" property, but this is still cumbersome. Even something as simple as grouping these objects in a sub-array representing each row would greatly improve working with this data.
There is no way to leave feedback about specific datasets. You can't ask questions or point out errors.
Metadata for datasets is non-existent. What if I don't understand one of the column headers? There should be detailed information for each dataset.