Closed klarareder closed 3 years ago
Database conform data The following checklist will help you to prepare your data in a way that you will have less trouble uploading it into the OEP. The main purpose is to have your data machine-readable and simultaneously for humans easy to understand.
This is a poor and a good example. This gives an Idea how to solve these problems, there are many good ways to solve it and two possibilities are show here.
poor example
good example In the good example there are two options how to split the timer series.
I have have the following two questions concerning the OEP, numbering from above:
@christian-rli I assigned you for this issues because we are both working on the tutorials issue. I made the first tutorial. Please feedback on:
This is a good collection of data best practices @klarareder Some quick feedback:
6a: should this say each cell? 6d: "In case of years as columns" should not be in brackets, but start the sentence in my opinion. 7: wording: "decimal separator" instead of "separation". we need to differentiate "decimal separator" (symbol between integer part and fraction part of a number) and delimiter (symbol separating fields/columns/cells). There is no one mandatory way / best practice / one correct way of what symbols to use, only culturally different ways. people do have to specify what system they're using, though. As this is slightly relevant, see here for a complete list of metadata values with a short description that I just finished: https://github.com/OpenEnergyPlatform/examples/wiki/Metadata-Description 8: In a database, cells without values are always "NULL". After uploading data with empty cells, when you query the values of those empty cells you get NULL as a value. You can also explicitly set empty cells NULL, but it's not really necessary. Also, wording: "Think about what..." 10a: Always use the same format. Always use ISO 8601. https://xkcd.com/1179/ , https://en.wikipedia.org/wiki/ISO_8601
@christian-rli thanks for the good feedback. I changed it to your suggestions. Only 6d I reworded: not only in case of years as colums one can transpose data but also in cases like having different parameters etc.
@christian-rli I placed the obove text on the OEP. If you check out features/tutorial-app you can see the changes and check if everything is ok (links working, no copy paste errors, texts ok etc.) I forgot to mention the Issue in the commit, that is why it is not shown here, sorry. Once you agree with it, we can start a pull request and close this issue.
@MGlauer I pushed everything which was shown on my change of file list, but I noticed, that the static folder is not shown and thus I am not sure if I pushed the images.
Did you add the folder to your stage (e.g. with git add
)
@klarareder I did not read through the whole thing yet, but I had a quick look and noticed that a) links all worked, but b) there were no images. So it seems like you did not include your static folder (or the images).
@klarareder Reading over the text I noticed a couple things. At one point you write "speaking names". I'm not really sure what you mean by that, but your example makes me guess something like "expressive names"? Also, in 7 there is a "deliminator" that's probably meant to read "delimiter". The text is fine otherwise. Just add the images and it's ready to go.
@christian-rli is this included in the new tutorial page in the upcoming release next week? Or has this to be added to the Tutorials once they are online?
relates to issue: #9