Data quality problem: discuss & solve

[njyx]

Happens with variety of fields but Images, Title and Description have the biggest effect because they are visible to people searching. Only two real solutions:

• Show the crap, hassle people to update their specs.
• For each API we have to have a parallel data structure (like a shadow APIs.json) which we can edit and add things to where for any field which has data, that data overides what we get from the original (then we'd need a way of editing to those and do the work of adding that data). Maybe no UI for images needed, just a workflow for us.

In the long run the only realistic solution is #1, but maybe just not show / accept APIs which don't have the basics in an ok form. Maybe the second thing makes sense in the short/medium term, but I wonder if it makes sense to invest in something which is something others should fix.

Maybe effort shoudl go into building stuff which filters out things with poor data?

[kinlane]

I added overlays for the APIs.json and APIs levels - https://apis-io-admin.apievangelist.com/

The only way I think we will be able to deliver high quality site is if we hand edit the title, description, images, and eventually tags.

The way I have it now is that every APIs.json and associated APIs will have to have an "overlay" title, description, and image added before publishing. Whenever the the APIs.json is pulled the overlays remains the override and can be. updated at any time.

I will be adding a separate ticket for proposing an image template for rapidly creating for each API.

Next I will add better controls on the overlay admin page to filter, sort, and deal with as it becomes longer list.