Manual data normalisation and author verification

[SeverusYixin]

Due to a bug in the data_normalizer where it fails to properly normalize the raw data from GitHub after execution, the data is being manually normalized for now. Additionally, the authors' names have been manually reviewed and verified.

[SeverusYixin]

Hi @haesleinhuepf, would mind checking this PR :) And merge it :)

Thank you!

[haesleinhuepf]

Hi @SeverusYixin ,

I'm not sure if this modification is a good idea. The yml file becomes less readable. Furthermore, on the website this entry looks ok:

Can you explain why you want to change this?

[SeverusYixin]

Hi @haesleinhuepf , Thank you for your feedback! 😊 First, I would like to clarify that I haven’t made any changes to the script—it has always worked this way. Let’s try to recall the discussion we had earlier: when I asked you about this, I mentioned that normalizing the output might result in something like this in the YAML file. At the time, you mentioned that as long as it displayed correctly on the website, you were fine with how it appeared in the YAML file.
That said, I agree that as the Data_content grows, improving readability in the YAML file could indeed benefit maintenance. To address this, I’ll go ahead and create an issue to propose modifying this output for better readability.