Improve the Open Event format and add support to Giggity and other Open Source conference apps

[mariobehling]

The Open Event format has reached a first stable stage, but there are still open questions with the implementation of the format. It also has not been implemented in Open Source conference apps.

Please get familiar with the Open Event format, propose improvements and make a list of applications that could benefit from supporting the format. Outline which apps can be implemented in your project and make a list of relevant issues and milestones.

As an example you could have a look at Giggity here https://github.com/Wilm0r/giggity. Sample docs of the Open Event files are here https://github.com/fossasia/open-event/tree/master/sample

Some of the relevant project discussion is in this issue: https://github.com/fossasia/open-event/issues/56

Open Event: The Open Event Project offers event managers a platform to organize all kinds of events including concerts, conferences, summits and regular meetups. The components support organizers in all stages from event planning to publishing, marketing and ticket sales. Automated web and mobile apps help attendees to get information easily. There are four components of the project:

1. The Open Event Format Definition [JSON Schema Sample]

2. The Open Event Orga Server [Repository]

3. The Open Event Android App Generator [Repository]

4. The Open Event Web App Generator [Repository]

The source code of each component has its own repository and technology stack. The software applications can be hosted as stand alone solutions or they can be integrated as microservices into the Open Event Orga Server through APIs.

Communication: Please join our mailing list to discuss questions regarding the project: https://groups.google.com/forum/#!forum/open-event and Our chat channel is here: https://gitter.im/fossasia/open-event

Open Event Format Definition: The Open Event project enables the exchange of data between all components as well as with other services through a standardized Format. The Open Event repository provides a sample implementation of the format. It includes JSON files for all relevant event information and binary data for images and audio files. Repository: https://github.com/fossasia/open-event

Open Event Orga Server: The Open Event Orga Server enables organizers to manage events from concerts to conferences and meet-ups. It offers features for events with several tracks and venues. Event managers can create invitation forms for speakers and build schedules in a drag and drop interface. The event information is stored in a database. The system provides API endpoints to fetch the data, and to modify and update it. Organizers can import and export event data in a standard compressed file format that includes the event data in JSON and binary media files like images and audio. The Repository: https://github.com/fossasia/open-event-orga-server and the Communication Channels: Please join our mailing list to discuss questions regarding the project: https://groups.google.com/forum/#!forum/open-event. Our chat channel is on Gitter here: http://gitter.im/fossasia/open-event-orga-server

Demo version: A demo version is automatically deployed from our repositories:

• Deployment from the master branch - http://open-event.herokuapp.com
• Deployment from the development branch - http://open-event-dev.herokuapp.com
• Developer documentation gh-pages - http://dev.eventyay.com

[the-dagger]

@mariobehling Since giggity supports xml samples and our sample is in json format, so what do you suggest at this point?

1. Add json support to giggity or
2. Make a copy of our samples in xml format.

[mariobehling]

@the-dagger The Open Event format is using a set of JSON. How can we make Giggity using this set? As I am not the one implementing it, questions should go to @heysadboy.

[the-dagger]

Yep understood. There are two ways to do so, in the first one we will need to change the samples whereas in the second one we will be making changes to Giggity which will including making changes to the Giggity app.

Both of these methods are doable, so wanted to get your approval on which change you would prefer.

Thanks.

On Friday, May 12, 2017, Mario Behling notifications@github.com wrote:

@the-dagger https://github.com/the-dagger The Open Event format is using a set of JSON. How can we make Giggity using this set? As I am not the one implementing it, questions should go to @heysadboy https://github.com/heysadboy.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fossasia/labs.fossasia.org/issues/151#issuecomment-300954564, or mute the thread https://github.com/notifications/unsubscribe-auth/AGQtlri8930yUWMjsui4Q3-IFTJWfISiks5r46zZgaJpZM4JoQTq .

-- Best, Harshit Dwivedi

[scandindian]

@mariobehling @the-dagger I created an issue about this earlier. https://github.com/fossasia/open-event/issues/134 If we want Giggity to read our JSON data format we have to change their code to read our data only in JSON while other events provide theirs in XML. I think it would be better if we modify ours according to the app. I saw that they also rejected earlier requests to do this while the other events follow this XML format only.

They have their raw data like this. Which I have to add in the PR. https://github.com/Wilm0r/giggity/blob/master/app/src/main/res/raw/menu.json

And the information of events in a conference is like this in XML https://programm.froscon.de/2016/schedule.xml

which I will be adding as the alternative XML sample in ours.

Even if we add JSON support we have to modify ours to support their format.

@the-dagger 1st option is better and reliable.

[mariobehling]

We can iterate and start with the simple solution. I don't know how well the export of the XML from the Orga server already works. Please try.

We probably need to change Giggity in following steps as well as (last time I checked) it did not provide support for all our data sets. So, it is part of this project to go into details. Thanks.

[ssirowa]

@mariobehling , I'm a Computer Science and Engineering Student at Indian Institute of Technology. I would like to work on this during GSoC. Can you help me get started.