cfpb / api Goto Github PK
View Code? Open in Web Editor NEWDocumentation to support upcoming data platform API and data sets
Home Page: http://cfpb.github.io/api/hmda/
Documentation to support upcoming data platform API and data sets
Home Page: http://cfpb.github.io/api/hmda/
That was the actual feedback we got.
Proposed fixes:
Why didn't we set up Google Analytics for this? Better late than never.
On April 24th, @18F hosted an API usability session where a handful of devs from the private sector reviewed existing government documentation. Our HMDA Docs were part of the sites reviewed and we got useful, real feedback.
👍 18f took the initiative to get much-needed usability sessions rolling and we can help it stay alive by following through with quick fixes and a simple backlog.
This milestone represents the first round of fixes–we committed to three things at the session. I'll be describing our usability findings in an actionable way by making an issue about them.
We received feedback that developers did not feel they had enough context around HMDA data. The places where we tried to provide that context were ineffective because:
Most devs are also not coming to the docs from the HMDA site, so embedding the video isn't a redundant use of content.
Proposed fix:
Right now, the UI (and maybe Qu?) doesn't allow aggregations over census tract (because it's a number maybe?). Combined with state and county, the census tract id because uniquely identifiable across the US.
Not sure if this is as simple as using a string to represent the census tract?
Some of the concepts are fine, but when I tried to grab info about msamd
I got the "This might take a while" message and my browser froze for a bit. It came back after about 30 seconds though.
Perhaps Swagger isn't the best solution for this API? Not a good idea to hide this console the way we hid the others. Open to suggestions/comments. Or just a heads-up.
Field names and descriptions can be found:
They should be consistent if we're to provide good context around the data. In some places there isn't even any description.
Proposed fix:
@cndreisbach @marcesher @virtix I'll need help with this one for the first 2 examples. Will be an opportunity to explain to dev community how changes to API are handled, too. They wanted to know more about that.
msamd
)The link http://www.federalreserve.gov/pubs/bulletin found on
no longer exists and should be updated or removed.We received feedback from users that they didn't grasp the point of HMDA well enough. Right now the following places on the docs give context:
We initially thought that linking to cf.gov/hmda would help but those links weren't noticed.
Proposed fixes:
On API Calls:
We received feedback from users that they knew they needed to select this text to use in their work, but it was hard to skim through it and select it.
Quick-fix:
white-space: nowrap
: https://github.com/dezzie/api/blob/gh-pages/hmda/console/css/style.css#L177The Learn More section of the HMDA site should be important to devs who want to build something serious.
The fact of the matter is that HMDA data has been collected and described in an esoteric way we cannot change. It is important to understand those methods in order to use the data responsibly.
For example, on its own, HMDA data cannot be used to infer causality. We wouldn't want a ton of apps that say, "Dezzie will likely get her loan application denied because she's a Mexican-American woman in her 20s trying to buy a big house on her own in the nice part of Orange County, CA."
Proposed fix:
On API Calls:
The page freezes (or just takes a really long time). We received feedback that this made users leave our docs page.
Quick-fix:
HMDA, LAR...
slices, concepts...
...what are better ways to say this? Ways to say it once (because it's required), and do something where we never have to say them again?
Received requests for "interesting" endpoints. I guess our slices are too boring, impractical, or don't appear useful to developers. They also assume that devs will be HMDA-aware.
Proposed fixes:
I think we can figure these out already…? Why would we need a dedicated endpoint?
By the time the actual table comes around, we've subjected users to
The table itself lacks
NEATO: We received feedback that people were going to the Explore Page of the HMDA website to look at the definitions of fields there because they were better.
Proposed fixes:
We received feedback that devs were frustrated with the lack of context around HMDA data that for those who checked out the HMDA website, they found the Explore page to be more helpful than the Field Reference or Console sections of the docs.
We know that:
Proposed fixes:
We received feedback that people want to know more about the tech behind the API.
Proposed fix:
@marcesher @cndreisbach I'm gonna need your help on this one.
In API Calls:
We received feedback from users that it was annyoing to transfer the responses to somewhere else.
Proposed solution:
Originally we thought that if devs got to the Field Reference page, they would be interested in the "process" of making something using the API. We used this page as a place to give them the "fine print."
Intro to HMDA LAR Fine Print 101 lives at the Learn More page on cf.gov/hmda. We thought that linking them to that page would be effective.
Instead we received feedback that devs were put off by the "congressional stuff".
Still, we think they need to know how this data is reported, because the CFPB should make it clear what this mortgage data can and can't say.
Can we change it with the added / ? Whether it resolves as is or not for us who are loading the page often, we don't want to ruin someone's initial experience of the site.
In API Basics:
We received feedback that the content was easy to read but annoying to take action on.
Proposed fix:
We may not have covered all the basics.
Suggested fixes:
We got feedback from devs that there wasn't a place on the docs where we explained a change/update process. Without this they felt like building a business plan around a contribution was a shot in the dark.
Comments @marcesher @cndreisbach @virtix?
Since middle of September EQUIFAX, INC. stopped having complaints with narratives. Is this an API problem?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.