Indian eCourt Records Search Website
Budget: ₹12,500 – ₹37,500 INR
I need a data-driven web application that can pull case information from the Indian eCourt portals and present it in an easy-to-navigate interface. A visitor must be able to search by name or by address and then refine the results with quick filter and sort controls.
PostgreSQL will be the primary datastore, so the backend should create a clean schema, write to it on every fetch, and read from it for subsequent requests. Please handle the full workflow—scraping or calling the public eCourt endpoints, de-duplication, error handling, and scheduled refresh—so the results stay current.
To keep expectations clear, here is what I would like handed over:
• A responsive front end that shows two main search boxes (name, address) plus dynamic filter/sort panels.
• A secure API layer that queries the eCourt source, stores records in PostgreSQL, and returns JSON to the UI.
• Setup scripts, brief documentation, and deployment guidance so I can run the site on my own server.
If you have experience dealing with large public datasets, captchas, or rate-limited government sites, mention it—those skills will be valuable here. Let me know your suggested tech stack for the crawler/service layer and your estimated timeline.
PostgreSQL will be the primary datastore, so the backend should create a clean schema, write to it on every fetch, and read from it for subsequent requests. Please handle the full workflow—scraping or calling the public eCourt endpoints, de-duplication, error handling, and scheduled refresh—so the results stay current.
To keep expectations clear, here is what I would like handed over:
• A responsive front end that shows two main search boxes (name, address) plus dynamic filter/sort panels.
• A secure API layer that queries the eCourt source, stores records in PostgreSQL, and returns JSON to the UI.
• Setup scripts, brief documentation, and deployment guidance so I can run the site on my own server.
If you have experience dealing with large public datasets, captchas, or rate-limited government sites, mention it—those skills will be valuable here. Let me know your suggested tech stack for the crawler/service layer and your estimated timeline.