5 - Set up boulders in database

PulexIrritans commented 2 years ago

Value statement - a requirement, not a solution

As a user I want to save my data in a database to be able to access my data from anywhere.

Description (Text, Scribble, Wireframe, Design)

Each boulder should be saved as a document in the collection boulders in the mongodb as per the following example:

{ "id": "1", "name": "King Kong", "sector": "Monkey Island", "level": "1", "hold_color": "yellow", "setter": "Nora Born", "tags": [], "img_start": "King_Kong_start.jpg", "img_complete": "King_Kong.jpg", "weighting": 100, "start_date": "2022-05-20", "expiry_date": "" }

Acceptance criteria

[x] At the page "Find" the boulders list is fetched from the db.
[x] All boulders that are present in the boulders db collection are being rendered on the find page.
[x] There is a hint in the front end in case no boulders could be fetched.

Tasks

[x] set up mongodb atlas
[x] upload boulders (as json) to collection boulders
[x] connect backend server with mongodb
[x] setup API key in env. file and make sure it's ignored by github
[x] set up GET route on backend server to fetch boulders from db on incoming fetch request
[x] implement fetch for boulders list on frontend (find page)
[x] implement error handling

Size

(medium)

mbosselmann commented 2 years ago

Hi Antje, I like your user story. 👍 My remarks:

I think you could write your value proposition also from a user perspective. Suggestion:

As a user I want to save my data in a database to be able to access my data from anywhere.

I would add under acceptance criteria that if there is no data in your database, the user gets a hint. And for tasks I would add error handling. :)

PulexIrritans commented 2 years ago

@mbosselmann Hi Mareike, thank you for your feedback. I have updated the user story accordingly.

PulexIrritans / Heelhook-Capstone