Repository used for the HackaTrain Contest assignment. It contains the explanation of what is required to be delivered and the assets needed to complete the assignment.
As a Hackatrain contestant
I want to have an easy, standardized way of importing location files
So that the location datastore is kept up-to-date
At Parkmobile a large part of the work we do revolves around having an accurate and up-to-date datastore of parking locations. Luckily we do not have to drive around cities to count the number of parking locations, we get lists of the parking locations delivered to us! Unfortunately our clients highly rely on their Microsoft Office environments, meaning we get these lists of parking locations delivered as CSV files.
This is where you come in!
We are looking for a simple, yet effective way, to import these CSV files into our datastore, removing the chances of human mistakes in the process where ever we can.
- All CSV asset files must be imported and processed
- Each row of location data must end up in the datastore
- The solution must at least expose the datastore REST API so it can be easily used by the import process
- Provide proof that your solution works
The datastore is completely shielded of from outside access for security reasons. We therefore need to expose a REST API to accept incoming changes.
- Until the datastore is finalized by the IT/DBA department we should provide a mock for the datastore, so we can start with the assignment
- How to deal with invalid data?
- Import all CSV asset files
- Import Excel files (out of scope for now)
- Mocked datastore
- Process CSV asset files
- Move data into datastore
- Create tests
- Write documentation
- Technical Specification
- Argument your design decisions
- Provide instructions on how-to run your solution