Application

Instructions of how to use the application are written below, beginning of how to load ticket data into system.

Loading Tickets

The tickets data can be loaded using the following methods:

  • REST calls to other applications.
  • Direct DATABASE inserts.
  • Insert manually via django-admin interface.

Web Tickets

This kind of ticket is the basic one, it handles a sell via e-commerce platform. Using the meeting.gate.models.WebTicket model:

class meeting.gate.models.WebTicket(*args, **kwargs)[source]

WebTicket data handles web tickets information.

Web tickets contains a QRCode (uuid param) usually previously generated from another application.

The required attributes are:

Parameters:
  • uuid (string) – The universally unique identifier for the ticket.
  • product_id (integer) – The product ID or type.
  • product_name (string) – The product name or description.
  • buyer_name (string) – The product buyer name.
  • buyer_email (string) – The product buyer email.
  • shop_purchase_date (datetime) – The shop purchase date.

So, you need the create the web ticket containing the attributes above.

Example: 
>>> WebTicket.objects.create(uuid='SOME-UUID',
...                          product_id=123,
...                          product_name='Festival Ticket',
...                          buyer_name='Regular Joe',
...                          buyer_email='buyer@email.com',
...                          shop_purchase_date=datetime(2012, 12, 12, 12))
<WebTicket: SOME-UUID>

Note

The complete attribute list below is autogenerated, most of the fields are not necessary to create a valid WebTicket.

Parameters:
  • id (AutoField) – Id
  • created_on (DateTimeField) – Criado em
  • modified_on (DateTimeField) – Modificado em
  • wristband_code (CharField) – Pulseira
  • entry_on (DateTimeField) – Entrou em
  • wallet_id (PositiveIntegerField) – Id carteira
  • wallet_info (TextField) – Wallet info
  • shop_purchase_date (DateTimeField) – Comprado em
  • wristband_ptr (OneToOneField to qrcode) – Wristband ptr
  • uuid (CharField) – Qrcode
  • qrcode_requires_identification (BooleanField) – qrcode_requires_identification
  • qrcode_ptr (OneToOneField to webticket) – Qrcode ptr
  • person_name (CharField) – Nome da pessoa
  • person_document (CharField) – Documento da pessoa
  • product_id (PositiveIntegerField) – Id do produto
  • product_name (CharField) – Nome do produto
  • buyer_name (CharField) – Nome do comprador
  • buyer_email (EmailField) – Email do comprador

Paper Tickets

Usually paper ticket vendors provides a text file containing one uuid/qrcode per line. There is a way to import these tickets using the model meeting.gate.models.BatchPaperTicket.

Access /gate/batchpaperticket/ admin interface and add the batch file to create the paper tickets in one operation.

Guest Tickets

This ticket is used for guests, they still receive a qrcode to be accredited. The meeting.gate.models.GuestTicket model handle this information with extra fields related to the guest information and also requires identification during the accreditation process.

class meeting.gate.models.GuestTicket(*args, **kwargs)[source]

GuestTicket data handles guest tickets information.

Guest tickets contains a QRCode (uuid param) usually previously generated from another application and also the guest name and document required to allow the guest entrance.

The required attributes are:

Parameters:
  • uuid (string) – The universally unique identifier for the ticket.
  • list_name (string) – The list this guest is related, for example: Sound Crew.
  • person_name (string) – The guest name to be checked on ther person document.
  • person_document (integer) – The guest document id code.

So, you need the create the guest ticket containing the attributes above.

Example: 
>>> GuestTicket.objects.create(uuid='SOME-UUID',
...                            list_name='Sound Crew',
...                            person_name='Regular Joe',
...                            person_document='ABC-123')
<GuestTicket: SOME-UUID>

Note

The complete attribute list below is autogenerated, most of the fields are not necessary to create a valid GuestTicket.

Parameters:
  • id (AutoField) – Id
  • created_on (DateTimeField) – Criado em
  • modified_on (DateTimeField) – Modificado em
  • wristband_code (CharField) – Pulseira
  • entry_on (DateTimeField) – Entrou em
  • wallet_id (PositiveIntegerField) – Id carteira
  • wallet_info (TextField) – Wallet info
  • shop_purchase_date (DateTimeField) – Comprado em
  • wristband_ptr (OneToOneField to qrcode) – Wristband ptr
  • uuid (CharField) – Qrcode
  • qrcode_requires_identification (BooleanField) – qrcode_requires_identification
  • qrcode_ptr (OneToOneField to guestticket) – Qrcode ptr
  • person_name (CharField) – Nome da pessoa
  • person_document (CharField) – Documento da pessoa
  • list_name (CharField) – Nome da lista de convidados