Roombooking System: Difference between revisions

From The Munich Maker Lab's Wiki
Jump to navigation Jump to search
No edit summary
(update link)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
The fine folks of WERK1 have given us the task to do two projects for them, in exchange for free rent for the first 3 months. One of them is a roombooking system for one of their conference rooms.
{{Warnbox|text=<b>This system is currently not in use, but might be reactivated if necessary</b> }}


== The Task ==
{{project
They have a conference room that is situated inside, without windows. They want a system where their residents can rent out the room (for money) and control lights and a projector in the room automatically by the booking system.
|name=Roombooking
|image=Roombooking-screenshot01.png
|description=A system to allow members to reserve a part of the lab to work on stuff.<br>[https://rooms.munichmakerlab.de/ Link to MuMaLab Rooms]
|status=beta
|author=[[User:Tiefpunkt|Severin]]
}}COVID brings some interesting challenges with it. One thing is that in order to keep our space open, we were given a limit of people that can be in the space at the same time. Also, we are supposed to make sure there's only one person in one section of the space at the same time.


Here's the full project description:
For the first part, we have a check-in system, but for the second part, we've been kind of lucky to keep that up just by sheer luck. However, sometimes you want to use the workshop, and it's already taken. Also, for post-COVID times, sometimes, parts of the workshop or tools can only be used by a single person. Like the workshop when somebody is welding. So we could totally use a room booking system.
<blockquote style="border-left: 4px solid #999; background: #f6f6f6; margin:1em; padding: 1em;">
== tl;dr; ==
'''Projekt 1: Konferenzraum Buchung und Abrechnungssystem'''
We're trying this out: https://rooms.munichmakerlab.de/
<p>'''Hintergrund:''' Im WERK1 soll ein Konferenzraum entstehen, der WERK1 Residents für nur 5 Euro / Stunde zugänglich gemacht werden soll. Der Raum befindet sich im 2. Stock und ist entsprechend weit vom WERK1 Verwaltungsoffice entfernt, so dass der adminitrative Aufwand für eine händische Buchung, Türöffnung, Abrechnung etc. zu groß wäre.</p>


<p>'''Basisaufgabe:''' Da es sich bei dem Raum um einen Innenraum handelt, ist er ohne Beleuchtung kaum zu gebrauchen. Aus diesem Grund wäre die einfachste Variante zur Nutzung des Raumes: Ist der Raum gebucht, gibt es Strom und Licht, andernfalls nicht.  
== Requirements ==
Die Minimalstanforderung wäre also eine Web-Buchungsplattform mit Datenbank für eine monatliche Abrechnung, die via Microcontroller auch den Strom regeln kann. <br/>
* Simple - it should be as simple as possible really
Da der Raum auch über einen Beamer verfügen wird, sind entsprechende Nachlaufzeiten für den Beamer-Lüfter zu berücksichtigen. Hierbei muss evt. auch die Steuerung des Beamers via Schnittstelle berücksichtigt werden. </p>
* Webbased - obviously
* Accounts - When we started looking for tools, we noticed that logins/accounts might be an issue. Ideally, this would connect to some other solution we already have, which is basically just the wiki, or potentially loomio. Alternatively, it should have an easy system for creating accounts.
* Look&Feel - It shouldn't feel like it came out of the past century ideally


<p>'''Zusätzliche Aufgaben:''' Die Basisaufgabe ist in vielerlei Hinsicht ausbaubar. Entsprechende Erweiterungsprojekte könnten diskutiert werden. Hier nur einige Unterprojekte:
== Candidates ==
* Buchungsmonitor: An der Tür wird ein Monitor installiert, auf dem kommende Buchungen angezeigt werden.
Well, there isn't all that much out there. Corps usually use Exchange/Outlook for that kind of stuff, or GSuite, which is both not an option for us.
* Ein-/Ausloggen via Transponder: Alle WERK1 Residents haben statt Schlüssel Transponder. Mit einem Card-Reader an der Tür des Konferenzraums könnte die Raumbuchung noch einfacher gestaltet werden.
* [http://mrbs.sourceforge.net/ MRBS]
</p>
** This looks like it's from 1998.
* [https://www.bookedscheduler.com/ Booked], formally phpScheduleIt
** Now closed-source/hosted (Since 2020-11-01 🤦‍♂️, [https://www.bookedscheduler.com/the-future-of-booked/ blog post with details]), but used to be open source ([https://web.archive.org/web/20170806195735/http://www.bookedscheduler.com/ archive.org version of ther website])
** They've done a good job of "cleaning the internet" of their oss-past, but there's a mirror of an [https://github.com/tamsky/booked older OSS release on GitHub].
*** [https://forums.bookedscheduler.com/viewtopic.php?f=3&t=341 Found] an even more recent repo, with explainations in the README: https://github.com/effgarces/BookedScheduler/
** Seems to work fine with PHP7.2, doesn't work with 7.4 (v2.7.1,mnot checked with the latest version still available)
** Very promising
** They are also the team behind [https://www.labarchives.com/scheduler/ LabArchives Scheduler], which looked promising but is also not OSS
* [https://www.classroombookings.com/ ClassroomBookings] [https://github.com/craigrodway/classroombookings GitHub Repo]
** Aimed at schools, very nice and easy to use
** Setup is a bit tidious, as you have to setup a whole load of stuff by hand
** No self-registration possible
* [https://github.com/neokoenig/RoomBooking OxAlto Room Booking System]
** looks ok, but kinda difficult to operate
* [https://www.fab-manager.com/ Fab-Manager]
** Has a module for reservations but it's a bigger deal to set it up, so that's not really the best thing for now probably


<p>'''Material- und Hardware(Microcontroller-)kosten:''' Würden nach definiertem Projektabschnitt vom WERK1 übernommen werden.</p>
== Trials ==
</blockquote>
We had two candidates, Booked and Classroom Bookings. Classroom Bookings looked great but was a little difficult to setup, and also did not offer any options for self-registration. Booked was easier to setup, while the installation itself was a tiny bit rougher. And it allows us to not have to signup everyone upfront. So that was the winner


== Ideas ==
== Actual setup ==
* Use an existing open source booking system, and hook into that. Potential candiates (not evaluated yet)
We have a little bit older version of Booked running in a docker container on jupiter.munichmakerlab.de, on a MariaDB also in another Docker container.
** MRBS [http://mrbs.sourceforge.net/]
** phpScheduleIt [http://php.brickhost.com/]
** http://www.oxalto.co.uk/2013/09/new-open-source-project-room-booking-system/


== Files ==
== The Past ==
* MDB Protocoll
A long time ago, we were given the task to build a roombooking sytsem for our first "landlord", the Werk 1. This is what this page was originally aimed at. [https://wiki.munichmakerlab.de/index.php?title=Roombooking_System&oldid=503 This old revision] has all the details.
** MDB 3.0[[File:Example.jpg]]
* [[Archive:Self-aware Vending Machine]] - The second WERK1 project
 
== See also ==
* [[Self-aware Vending Machine]] - The second WERK1 project
[[Category:Project]]
[[Category:Project]]

Latest revision as of 14:08, 10 September 2022

Attention.png This system is currently not in use, but might be reactivated if necessary
   
Roombooking

Release status: beta [box doku]

Roombooking-screenshot01.png
Description A system to allow members to reserve a part of the lab to work on stuff.
Link to MuMaLab Rooms
Author(s)  Severin

COVID brings some interesting challenges with it. One thing is that in order to keep our space open, we were given a limit of people that can be in the space at the same time. Also, we are supposed to make sure there's only one person in one section of the space at the same time.

For the first part, we have a check-in system, but for the second part, we've been kind of lucky to keep that up just by sheer luck. However, sometimes you want to use the workshop, and it's already taken. Also, for post-COVID times, sometimes, parts of the workshop or tools can only be used by a single person. Like the workshop when somebody is welding. So we could totally use a room booking system.

tl;dr;

We're trying this out: https://rooms.munichmakerlab.de/

Requirements

  • Simple - it should be as simple as possible really
  • Webbased - obviously
  • Accounts - When we started looking for tools, we noticed that logins/accounts might be an issue. Ideally, this would connect to some other solution we already have, which is basically just the wiki, or potentially loomio. Alternatively, it should have an easy system for creating accounts.
  • Look&Feel - It shouldn't feel like it came out of the past century ideally

Candidates

Well, there isn't all that much out there. Corps usually use Exchange/Outlook for that kind of stuff, or GSuite, which is both not an option for us.

Trials

We had two candidates, Booked and Classroom Bookings. Classroom Bookings looked great but was a little difficult to setup, and also did not offer any options for self-registration. Booked was easier to setup, while the installation itself was a tiny bit rougher. And it allows us to not have to signup everyone upfront. So that was the winner

Actual setup

We have a little bit older version of Booked running in a docker container on jupiter.munichmakerlab.de, on a MariaDB also in another Docker container.

The Past

A long time ago, we were given the task to build a roombooking sytsem for our first "landlord", the Werk 1. This is what this page was originally aimed at. This old revision has all the details.

Retrieved from "https://wiki.munichmakerlab.de/index.php?title=Roombooking_System&oldid=6397"