Skip to content

Provisioning Technical Components

Malte Vogl edited this page Jun 24, 2022 · 9 revisions

Various technical components will need to be made available to workshop participants. Most will be hosted online someplace. We should make some decisions about where they will be hosted, and whether we have any fallback implementations to use (in case of a service outage). Also what if any preparations are needed for the provisioning of the software. Of course, we want to minimize the preparations by the participants (experience shows that they won't even know about them until the workshop starts) but we want to identify them.

Recogito

Online

https://recogito.pelagios.org

Hosted Fallback?

Should we put together a docker container from https://github.com/pelagios/recogito2 as a fallback?

Preparations by Team

Preparations by participants

Protege (WebProtege)

Online (WebProtégé)

https://webprotege.stanford.edu/

Comment Malte: the online version gives an error while looking at individuals, we need to use the desktop version

Local Fallback

We need to require participants to have this ready for the workshop.

Desktop Protégé https://protege.stanford.edu/

Preparations by Team

Preparations by Participants

Blazegraph

Online

There is a blazegraph docker container that is available: https://hub.docker.com/r/lyrasis/blazegraph Should we host one someplace for everyone to use? Or expect participants to go through installing docker (or other container)?

If we provision it for everyone to share, where would we host this?

(I suppose another option is Neptune, under an AWS free tier account?).

Local Fallback

Preparations by Team

Preparations by Participants

Jupyter Notebooks

Online

https://tljh.jupyter.org/en/latest/ has recipes for deployment on various services.

Local Fallback

Preparations by Team

Preparations by Participants

Other?