Unclear documentation

The following questions remained unanswered after I had gone through the documents in the project management and the app projects. @krlwlfrt has already answered them in the chat, but it would be nice if this would also be noted here.

1. How do timers work? Answer: The connector can be fired automatically via a "systemd" timer. (See dishes-connector/systemd/importer/dishes-connector.timer in StApps-TU-Berlin Group) Maybe this could also be implemented and documented in the minimal connector as an example.

• Documented in minimal-deployment

2. How do connectors communicate with the backend if there are multiple backends? Answer: The connectors are located in the same virtualized subnet by Docker-Compose. Each backend version needs its own connector.
3. What the frigg are Plugins? Maybe a detailed answer should be written here. In the previous documents they are not mentioned yet or the information went down too fast and I missed it. Also an example similar to the minimal-connector would be quite nice. Maybe a slimmed down version of the isbn-availability plugin?

• Plugins will be documented in api#16 (closed)

4. What does the final deployment look like? I think the link to the minimal-deployment/docker-compose.yml is enough. But looking at the whole project, it would be good to point out again that every university has its own backend. At this point it would also be interesting to explain again how this is meant in the specifications in chapter 9, that you can change the university in the settings and then load appropriate templates. This sounds at this point as if there is a common backend for all universities.