Printable tickets & better check-in process for OSEM about mentoring

[matheussbernardo]

Hello, where can I find the Juniot labeled issues?
---Edit----
Whoops my bad I found on the repository sorry.

[divyanshumehta]

I really like this idea. Would love to implement this idea for GSoC 2017.

[matheussbernardo]

Hello, My name is Matheus, I'm a Software Engineering student on Brazil, Starting the fourth year.
I'm working part-time with ASP.NET and I have done some projects with ruby on rails for college and also side-projects by myself. It's the first time I'm applying for GSoC and hope it will be an amazing experience.
I would like to know @Ana06 if my lack of knowledge with HAML is a problem?

Also congrats the openSUSE team on how the GSoC web page is organized because is one of the best I have seen, it has very clear instructions. Kudos.

Hope I can collaborate with OSEM.

[Ana06]

@siddhantbajaj

Are you planning to use some gem for implementing QR code like rqrcode?

That's up to you, when writing the proposal you can explain how you would like to implement this. But of course gems can be used if they helps you.

So basically at the time of check-in attendee will have a printed ticket with a QR code on it, Organisers will decode the QR code and the attendee will automatically marked as present in the conference database?

Exactly!

We also want to limit when the ticket is valid (the times, days, etc.), to register information about when the user arrive/leaves the conference and to modify the number of conference resources

didn't really understand this part.

You could for example have a conference which last 5 days and buy a ticket only for one of the days. So basically limit until when the ticket is valid.

Register at what time/day a user arrives. It could happens that a conference which last 3 days wants that people register every day, so you would want to store the days a person go to a conference and the time he arrives everyday. And then we have to find out a proper way to show this to admins. It could be shown for every user or for statistic or both.

Resources where introduce in openSUSE/osem#1261 So could want to automatically change the number of resources you have when a user arrives. For example, if you ask when registering the T-shirt size, if a user ask a S T-shirt you can automatically decrease the number of S T-shirt when reading the QR.

All this is basically about making the QR reader and the registration process more complete, but if there is something you think is not useful or you any other idea about that you can always write it in the proposal. 😉

[Ana06]

Hi @matheussbernardo!

I would like to know @Ana06 if my lack of knowledge with HAML is a problem?

No! It is something you can learn. 😉 You can see in the haml documentation the equivalence with erb. If you want you can work on any of the issues that implies touching the views so you can see how it is. For example:

openSUSE/osem#463
openSUSE/osem#400
openSUSE/osem#1156
openSUSE/osem#658

[siddhantbajaj]

Hello @Ana06 @mdeniz,
I have some doubts regarding this feature:

• Are you planning to use some gem for implementing QR code like rqrcode?

• It would be desirable to makes this process more efficient by allowing to do reading the generated QR

  So basically at the time of check-in attendee will have a printed ticket with a QR code on it, Organisers will decode the QR code and the attendee will automatically marked as present in the conference database?

• We also want to limit when the ticket is valid (the times, days, etc.), to register information about when the user arrive/leaves the conference and to modify the number of conference resources

  didn't really understand this part.

[Abhinand-p]

@Ana06 @mdeniz

I was thinking about Group enrollments. All members of group may not arrive at same time. Another issue is to check who registered is only attending.
QR code to be extended with a metric integrated gem. Being a authentication research guy, I want to develop: Interface to take input metric data prior hand; Non-intrusive metric reader(people should not be stopped for checking) ; Connect an OSEM App SUSECLIENT . In local host after cloning, i am trying to create "Pxxxxx" menu option for attendees, organizers, sponsors, booths .

[Ana06]

Hi @Abhinand-p, sorry I didn't answer before. I didn't read the message. 🙂

I was thinking about Group enrollments. All members of group may not arrive at same time.

What do you exactly mean with Group?

Another issue is to check who registered is only attending.

Can you elaborate on this? I am not sure of what you mean.

QR code to be extended with a metric integrated gem. Being a authentication research guy, I want to develop: Interface to take input metric data prior hand; Non-intrusive metric reader(people should not be stopped for checking) ; Connect an OSEM App SUSECLIENT . In local host after cloning, i am trying to create "Pxxxxx" menu option for attendees, organizers, sponsors, booths .

I am not sure if I follow you. You can add your own ideas to the proposal, but ensure that they are clear. Also mention if another part of the project won't be done to do this.

If you have question you can find me and other OSEM developers and mentors in #osem channel on freenode IRC.

[Abhinand-p]

Hi
Group means:
In any normal conferences, there may be 2 or more people from same institute / company registering together. example guide and his research scholars
another example : a research team from same industry

In authentication, face biometric can be used, while registration process itself.
When he attends it is just a cross verification.
Therefore i meant "who registered is only attending"

I will state clearly in proposal. Thank you.

[Ana06]

This was already done, so I close it 😉