Simple web service to return everything we know about a given reimbursement

[Irio]

Specially for internal reports (e.g. something strange found during analyses, needing further investigation before public reports), a web service to return everything we know about a specific record from the Quota for Exercising Parliamentary Activity would come in handy.

By everything we know, I mean the following:

• Record as reported by Chamber of Deputies (e.g. dataset.iloc[0] with dataset being pd.read_csv('data/2016-08-08-current-year.xz').
• Image of the receipt (check related work in Backup pictures from all receipts #33).
• Detailed information about the company receiving the payment (New dataset with companies information #19 is creating such dataset).

This short notebook could be replaced by a URL to this web service, with 5621548 (document_id) or 20574089000107 (cnpj_cpf) as parameter.

[cuducos]

I can code an API that serves these info as JSON (I'd do it in Django or Flask if there is no objection).

What I need:

• Any option to host it for free? (Postgres free plan at Heroku list the database o 10k rows) 😁
• Anyone willing to work on the visual design and front-end? People from Telegram that said you would like to contribute to a website, I need you 🤘

[filipelinhares]

@cuducos, I would like to learn more about Python, if you've some time to pair, let me know 😁

[brunopazzim]

If we're building an interface can we consider to have it together with the
project website (the one initially discussed on Telegram)? I think it would
be great to have everything in one place.

[baltazarparra]

we will discuss about the contents of the site?
done that , we can get the prototypes.

[cuducos]

Ok, after the discussion from the chat yesterday, I'm taking the following path:

1. Having an API/web service ASAP will free @Irio some valuable time to be spent on the exploration of the datasets, proof of concept, and proper AI, so I'm coding this simple API ASAP today or tomorrow, maximum on Monday.
2. I think we can integrate this in a web site for the project, but as this will take time, let's work in the institutional and more portal-like in parallel with no ASAP mood — this is Issue Website for consume API and publish data. #36 opened by @baltazarparra.
3. If the stack I choose to this ASAP API doesn't fit whatever we decide to do later, there's a great trash bin in my desktop and I don't mind throwing away my work there if (I'll be happy knowing it served its purpose for a while and that something better took its place); if we decided to integrate the institutional, portal-like and API in a single repo later, I also would be happy to be part of the team. TL;DR whatever we decide later, I'm in.
4. I'm probably using Python and Django for the backend and, Bourbon family for the front-end; raw Javascript or Elm (only if needed).
5. I'd love to pair, so feel free to get in touch if you wanna code together one of these days. Probably it will be something quick, just a few hours is enough — Drop a line if you wanna join me.

[cuducos]

Quick follow up:

• We have a working version of the JSON API ready to use, including query URL parameters for filtering (it's documented here)
• We have a limited visual interface that only allows searching by document_id
• The all the ~2 million records from the datasets are already loaded in the web service database

I believe we can close this issue as soon as I add more searching features to the visual version — and any further improvements could be added as issues in Jarbas repo, ok?

[Irio]

It's already enough for now, @cuducos. Mission accomplished. Let's move new features to its own issue tracker. 💯