Welcome to meeting-gate’s documentation!

Warning

Beta software You are using a software that has not reached a stable version yet. Please beware that interfaces might change, APIs might disappear and general breakage can occur before 1.0.

If you plan to use this software for something important, please read the roadmap, and the issue tracker in Github. If you are unsure about the future of this project, please talk to the developers, or (better yet) get involved with the development of python-boilerplate!

meeting-gate

https://img.shields.io/pypi/v/meeting-gate.svg https://travis-ci.org/mauler/meeting-gate.svg?branch=master https://coveralls.io/repos/github/mauler/meeting-gate/badge.svg?branch=master Documentation Status Code Health Scrutinizer Code Quality

This is Meeting Project entrance management application (know as meeting-gate). For complete instructions and more information, please check:

http://meeting-gate.readthedocs.io/en/latest/

About

This application focuses on managing festival attendee accreditation that make use of identification methods such as bracelets or cards (rfid, qrcode) for access control or cashless sales.

The accreditation is controlled through tickets, e-tickets and pre-generated invitations, which can also be imported from other applications.

For more information of how to use this Application, check the Cases of Use & Setup section in Docs.

How it Works ?

The application needs to be fed with the tickets data, the supported kind of tickets are:

  • Web Tickets (E-Commerce)
  • Paper Tickets (Classic printed)
  • Guest Invite (Requires document identification)
  • Local sell

This data can be loaded using: REST calls to other applications, direct database inserts, insert via admin interface. How it will be inserted depends your event case of use, check the Use Cases and Setup section.

After the data is prepared, the dashboard operation workflow is:

  1. Someone reads the Ticket QRCODE using a device.
  2. The application check if it is a valid one.
  3. If necessary asks the operator to verify the ticket owner documentation if the Ticket type requires it.
  4. The operator reads a new Wristband or card to attached to this ticket.
  5. The operator confirms the Entry.

After the entrance is confirmed, the data is sent to the cashless or access control application (If enabled).

Indices and tables