Solutions to aggregate data automatically or manually

[jurra]

Potential problem When yaml files become bigger they can become more error prone. People can easily make mistakes in yaml.

Manual solution

1. Let people open an issue using a metadata template that then the repo owner can add to the aggregate. 👍
2. Ask people to push their profile in a small yaml file in a folder, and then the owner of the repo, can add it to the big list.
3. Let people do pull request directly on the data file :-1 Not everyone feels confident in doing a pull request, although it can be fun to learn how git works :) If this is a goal then we just need to double check the change.

Automated solution

1. For the context of many people updating their profile, it might be better to ask them to put their little yaml profile in a folder, validate it, and then aggregate it to a bigger yaml file or json file. So we could automate the generation of the current manually written yaml file.
2. Use google apis and generate the aggregate from the current google table. This implies running the build of the metadata before building the website.

[jurra]

Example of a metadata template that can be turned into an issue template for the manual solution.

Firstname-Lastname:
  first-name: FirstName
  last-name: LastName
  photo: url   
  position: Assistant Professor
  faculty: Faculty of Aerospace Engineering
  department: Aerodynamics, Wind Energy, Flight Performance and Propulsion
  email: jasdsa@tudelft.nl
  website: mywebsite.org
  orcid: 0000-9834-000-1231
  github: username
  expertise: open source, dancing, playing tennis,