Skip to content

Working diary

Jump to bottom
BjornSeifert edited this page Jan 8, 2021 · 22 revisions

Week 10 report (2021-01-08)

Axel:

  • Worked on functions.
  • Worked on the report.
  • Worked on the poster.

Björn:

  • Worked on functions.
  • Worked on the report.
  • Worked on the poster.

Week 7 report (2020-12-18)

Axel:

  • Worked on functions.
  • Commented and polished existing backend code.

Björn:

  • Worked on functions.
  • Added testdata with traceable farm information removed to github.

Yuting:

  • Added a home page and login page to the webapp.
  • Implemented most functions for the interfaces.

Week 6 report (2020-12-11)

Axel:

  • Worked on functions.

Björn:

  • Worked on functions.
  • Studied food data for understanding.

Yuting:

  • Keep working on the dashboard layout.
  • Tried to recycle code.
  • Sealed the HTML style into CSS files.

Tomas to do list: Contact farmer about food.

Week 5 report (2020-12-04)

Axel:

  • Moved all backend code to Github and standardized most code with Björn.
  • Added some new functions.

Björn:

  • Moved all backend code to Github and standardized most code with Axel.
  • Added some new functions.
  • Ran all finished backend code and uploaded all resulting keyvalue data to Github.

Yuting:

  • Managed to draw interactive diagrams based on CSV files.
  • Re-designed the layout of the dashboard.

Muhammad:

  • Worked on Administrative page for web application
  • Functions for importing CSV files from external source.

2020-12-04

Tomas: ¨

  • Needs to set up read access to Gigacow data.
  • Fix key values for a week from Niklas
  • Need to set up the staging server where farmers can access their Dashboard (will take more than a week I think).

2020-11-27

Tomas feedback: It is important that we use Github to create a shared codebase where we can keep track of the project. With a shared codebase on Github it means that you don't end up spending Christmas desperately trying to get the four different codebases to work together. As a supervisor I strongly encourage you to:

  1. Have a branch each that you work on and have as a backup (in case computer breaks etc).

  2. When you are done with a feature (an functioning addition to the codebase that improves the Dashboard) you create a pull request to the main branch so you add your code to the project repository and talk about it with the team.

  3. When a pull request is merged with master everyone update their own branches to track the main.

  4. Try to have a minimal working demo so that you know if a pull request break things, so just a minimum viable product (first step would perhaps be as simple as the start up script so that a user can clone the main branch, run the start up scrip and get a local webserver running that displays the source data in unformatted HTML). Then you work on the features necessary to create functioning Dashboard and add them step by step.

This way you can all track the progress of the project and talk to each other identifying the different features you need to reach the desired end state by January. As a supervisor I can also say that I think it is better that you spend a week getting a collaborative working model than that you try to

Clone this wiki locally