Add example for fetching mutating datasets

[lmartinking]

This is a bit of a hack, but you can fetch mutating datasets by using mock.ANY as the hash value.
Combined with daily sub directories, you can fetch data that changes potentially every day.
This PR adds a simple example of this scenario. I have discussed with @leouieda on slack.

[welcome]

💖 Thanks for opening this pull request! 💖

Please make sure you read our contributing guidelines and abide by our code of conduct.

A few things to keep in mind:

• Remember to run make format to make sure your code follows our style guide.
• If you need help writing tests, take a look at the existing ones for inspiration. If you don't know where to start, let us know and we'll walk you through it.
• All new features should be documented. It helps to write the docstrings for your functions/classes before writing the code. This will help you think about your code design and results in better code.
• No matter what, we are really grateful that you put in the effort to do this! 🎉

[leouieda]

Suggested change

	Fetching Mutating Data
	Bypassing the hash check

[leouieda]

@lmartinking thank you for taking the time to do this! I really appreciate it 🥇

I think this would be better as a general example of how to bypass the hash check. What I find missing a bit is explaining why it wouldn't work normally and how you got around that with mock.ANY (really smart hack by the way). I really like the setup and example so we could phrase it as:

Sometimes we might not know the hash of the file or it could change on the server periodically. In these cases, we need a way of bypassing the hash check. One way of doing that is with Python's unittest.mock module ... (yada yada yada).

In this example, we are downloading...

[lmartinking]

Hey @leouieda I've updated the branch based on your feedback. Let me know what you think.

[leouieda]

Thanks for the changes @lmartinking! I made some editorial suggestions to the text. You can commit them directly to your branch through Github. Feel free to reject/edit any of those 🙂

[lmartinking]

Hi @leouieda I have committed all your suggestions and then squashed them together. I think you write very clearly, I'm afraid you have ended up pretty much writing these docs as well!

[leouieda]

@lmartinking not at all! This would have never happened if you hadn't started it. I just provided some tweaks to what you already had 🙂

Thank you for this contribution! We started a new authorship policy recently and would like to acknowledge all contributors by adding them as authors on the Zenodo archives we make for releases. We would be more than happy to include you if you could add yourself to the AUTHORS.md file (full name, affiliation, ORCID). You can do that in this PR still. Of course, that is optional and I understand if you'd rather not be included.

Either way, I'm happy with this and can merge as soon as the CI checks are green. 🎉

[lmartinking]

@leouieda If I contribute code, then we can think about the authors file. Otherwise, I'm happy as is. Merge if ready! 😄

[leouieda]

Alright, as you wish. Just wanted to point out that we value code and documentation contributions equally (what's the point of undocumented code?). Feel free to open a PR later adding yourself if you change your mind 🙂

Thank you!

[welcome]

🎉🎉🎉 Congrats on merging your first pull request and welcome to the team! 🎉🎉🎉

If you would like to be added as a author on the Zenodo archive of the next release, make sure that you have added your full name, affiliation, and ORCID (optional) to the AUTHORS.md file of this repository.

We hope that this was a good experience for you. Let us know if there is any way that the contributing process could be improved.