Logo
Home page
Sign up form
Join Event form
Event list
Payment method

Project information

What's ESN?

Is a non-profit organization that supports and promotes the mobility of students in higher education.

What are their needs?

A centralized and easy to access and maintain managerial software in order to manage their members and the various event they organize.

Current process - Pain points

  • Only cash payment for the ESNcard
  • Handwritten receipt
  • Event managed through a Facebook group
  • Hard to maintainGoogle Sheet
  • Use of Google Form
ESN padova img

Objectives

This project is intended to be a Web App that will be used by ESN Padova It would help them to streamline and facilitate tasks of registering members and maintaining a membership list different every year (currently made by volunteers). The use of a web application would then likely increase the visibility of its events to international students and make it easier to register for events organized by ESN Padua, just from their smartphones.

Furthermore, that allows volunteers to manage events and Erasmus students, since there is the opportunity to join some events only if you're a member of ESN Padova (that corresponds to getting an ESN card and paying a fee). At the moment, the subscription is made with a paper form, the payment is by cash or POS and the overall database is a spreadsheet. Events are managed by a communication manager, who posts them on Instagram, the website, and the Facebook group. Mainly former platforms. As a result, this is a very time-consuming process, that requires a lot of effort from volunteers and, what is more, it is not very efficient. The overall goal is to facilitate the process and build a stronger database

User Tiers
User Tiers

User Management

Erasmus and International students should be able to register and create a new account autonomously through the Web Application.

Once they confirmed their email, they are assigned a tier 0 user. Tier 0 users have limited users and they can only see and participate in certain events that are open and available for everyone and don't require any kind of registration. Tier 0 users are not to be considered members since they don't possess and paid for an ESN card (association card), and they didn't insert all the information necessary to be considered a member.

A Tier 0 has to possibility to become a Tier 1 user and become a member of the section once he/she fills in the subscription form and pays the card fee. Once they did what is above, they can come to the ESN office with a precompiled document that needs a signature, and they will receive their ESN card.

Tier 1 users are, in a nutshell, all the Erasmus and International people that are a member of ESN Padova and can participate in all the event available for them. Tier 1 users can indeed see all the events, participate and pay the fee (if needed) through the use of the application.

Main functionalities

Database

The main idea and use of the above-presented Web Application is to provide a reliable management system to ESN Padova. The not-so-efficient procedure described above, besides not being reliable and not very agile to changes, may be subjected to input errors and several works every time some specifc list (i.e. participant list to a specifc event).

A centralized DB (i.e. PostgreSQL) and a user-friendly interface where Erasmus students and International people can autonomously become members can reach the goal of slimming down the work done by the volunteers to manage and keep this spreadsheet updated.

As a second but welcome goal, ESN Padova is also looking for a platform where members can see and pay for events. In fact, at the moment the main place where members get to know about an event is through social networks or the website, where it may not be easy to navigate given the amount of information on the website.

ER Schema
ER Schema

Our database has 3 main entities, plus an important relation. The main entities are:

  • Usersthis entity contains all the information about every kind of user, from tier 0 to system admin. This table has new entries every time the registration form is filled: the dummy form will generate a tier 0 user, while the real form will generate a tier 1 user. Every attribute is self-explanatory and stored in a very intuitive way.
  • Eventsas for users entity, event has a long list of attributes, wisely chosen about how events are organized. Some events are restricted to certain users, based on tiers, or have a limited number of participants. All these particularities are fully represented in the entity.
  • Payment this entity contains all the information about payment for event participation. Of course the actual web application isn't linked to real payment methods, but once it will be, this Entity will be related to real payments, in order to trace them, know most favorite payment methods, etc.
  • Participantsopposed to previous entities, this is a relation between users and events, collecting user role.

Other informations

Tags and Causes are two entities that are used to classify events. Every ESN event supports at least one cause, such as rising founds, meeting freshman, etc. and can be tagged as school, party, cinema, etc. These two entities are used to filter events, to help users find what fits their interests. EventTag, EventCauses, R1 and R2 are relations without attributes, used only to join tables.

(This is just a quick explanation regarding our Web Application, if you are interested in the details check our Documentation ).

Developers

  • Borsato Alessandro
  • Campagnoli Andrea
  • Cardillo Vittorio
  • Lenartavicius Vaidas
  • Maglie Mattia
  • Marcato Francesco
  • Pallante Laura
  • Talukder Md Imran Faruck
  • Villani Matteo
  • Zago Giovanni