User stories sprint 1

[noobling]

Checklist before you make a PR

• [x] Is the title of the PR reflective of the proposed changes
• [x] Have you added the appropriate people who need to look over this?
• [x] Have you merged master with this branch and resolved all merge conflicts?

How to review a PR

• Glance over their changes making sure there are no silly errors
• Add your thoughts on their file changes
• Try to add everything you need in a summarised comment below.
• Try to use a comment below rather than a inline comment in the code because things just get messy to read.

[m-Dorrell]

I don't think the researchers want people to edit or delete data older than the past night so that way their data will always be up-to-date instead of downloading it for analysis and a user changes something.

Also seeing other users data is likely a breach of their privacy.

[m-Dorrell]

Since we're assessed here based on the 'Coherence and reasonablenesss of the set of intermediate goals (stories) (/5)' I think we need to be more specific about which we will be able to do by the end of the sprint. Maybe we should expand upon the subtasks required to implement them? Also are all these are reasonable in a month?

[noobling]

@m-Dorrell its aggregated but yeah i was just trying to think of things to add probably change that.

I thought they agreed to allow users to change data because it is better to have data that changes than incorrect data?

Also as state I will change the username and password style to code based to remain consistent

Also are all these are reasonable in a month?

Ah they are reasonable for me since this is my bread and butter

I think we need to be more specific about which we will be able to do by the end of the sprint

Yep noted I will see what I can do