Mirror Strategy to Zenodo

[mam10eks]

We need to figure out a mirror strategy to Zenodo. So that every tutorial that we have (especially for teaching, but also for conference tutorials) by default points to the Zenodo Mirror, so that the client side development is really robust and even works when nothing on our side is running (e.g., a power outage).

[mam10eks]

cc @johanneskiesel, @potthast with your Zenodo Experience, do you maybe have time to discuss this in our next TIRA meeting this Thursday at 14:00?

[johanneskiesel]

I have no idea what you are planning to do (tutorials in TIRA?).

I am available at that time, though.

[mam10eks]

Awesome, thanks, I can explain this in the meeting :)

[potthast]

We can certainly discuss this in more detail. I was thinking of a combined strategy of GitHub hosting and Zenodo archival. But let's discuss this.

[potthast]

Quick update after Johannes hinted at me that I misread: Thursday, I'll be on an errand at 14; can we meet ahead of time, if I should be around?

[potthast]

(gerade Gespräch mit Maik)

[mam10eks]

From the discussion:

• Disraptor to AWS
• Proxy that can point to either TIRA or Zenodo

@potthast for the proxy: I like the idea that you had to move this proxy that switches between the TIRA or Zenodo data storage to disraptor.

[mam10eks]

I start a draft in a (currently private repo) that we can use for static hosting: https://github.com/tira-io/tira-data

[mam10eks]

The orga-preparation is done:

[TheMrSheldon]

Should it be static.tira.io according to the planned board above? Or is static.tira.io for the frontend itself?

[mam10eks]

Our update from our discussion today: