singh1114/eventsrest

REST API for the event manager app.

Trouble Less Events

Information about the directory structure

http://www.revsys.com/blog/2014/nov/21/recommended-django-project-layout/

MINIMUM PLAN

• Add accounts in the app.
• Create the base template.
• Start by creating the templates for participants.
• The participant view must consist of a login window.
• If logged In take them to the view having three buttons.
  • Add profile.( create view)
  • Update a profile.( Update view and delete view)
  • see all profiles.( Retrieve view)
  • Participate in an event.

Installation

• $ sudo apt-get install python3-pip
• $ sudo apt-get install virtualenv
• $ sudo apt-get install git

Now go to a place where you want to create the virtual environment.

• $ virtualenv -p python3 .

Now fork and clone the repository.

• $ git clone https://gitub.com/your_username/EventRest

• $ source bin/activate

• $ cd EventRest

• $ pip install -r Requirements.txt

Now create the mysql database and change the credentials in the file EventRest/MainDataBase/settings/base.py

After that make the tables and migrate the models.

• $ python manage.py makemigrations
• $ python manage.py migrate

Create superuser for admin part

• $ django-admin create superuser

Future plan

For the time being the event proposal are shared by using email. I want to create an interface through which the users can create and share their ideas directly into the app. The app interface will look like this:

Event Name - ..... Event coordinator Name - ...... Coordinator Branch - ...... Event coordinator Year - ..... Number of members - ..... Proposal - ............

SUBMIT

The core-team has the power to select or deselect the event. If a user has logged IN as a core member he or she can select as well as reject the event. Here voting can happen: If more than half core members decide to reject the event and if more than half people decide to accept the event then the event is selected. After selecting the event the room and time is going to be allocated to the event.

Once all details are filled by the core team, special Id and password will be generated for the event coordinator and he can futher generate as many ID's and passwords as the number of members as he suggested in last step. The event coordinator must take care of this step and allow proper sending of userIDs and passwords. He can ask the main programmer to increase or decrease the allowed members, if needed.

Role of event coordinators

Role of event members

• Members can allow the submittion of the forms and check for the presence of the participants. If the member is not present remove there names from the list. This means for the members, we need the participants view with the permission of update and delete.

Role of participants

• Participants can login using google or email and then they can add a profile. The profile is going to made visible to the member and then member can take the entry fees and select the check box for the fees submitted.

• There is no much need of participant to be authenticated. But if authenticated we can save their profiles

• Participant can also add multiple profiles.

• When the members take the attendence the non present members must be sent to a trash list from where they can be retreived. The participants who have not paid are also going to be in the same list.

• Certificates will only be issued to the people who have registred, appeared and paid the fees.

• The extra money of the students who have not appeared must be given to the programmer :)

eventsrest's Issues

Allow participant login thorough google login API

Solve the problem with the models

For the time being,
I am able to detect the following problem in the models:

• The EventApp has a model of Participants_List which contain, EventId and other items like participant_name and all.
• This thing must be transferred to the overridingAuth app.

Solution
A good solution is to divide the model into two parts for normalisation purpose. The eventApp will contain a model having two fields i.e. event_id and participant_id( which is the foreign key to the overridingAuth app's participant model) and an overridingAuth/participant model containing all the attributes of the participant.

Unable to handle get URL parameters.

At the login page, if we are getting a get request with query string with values of next, the query set is not handled properly.

Write code to handle the next query set.

No need for the admin to see the participant list

Participant list is visible to the admin. There is no need for doing that.

Navigation bar is not rendered properly.

Navigation bar at /parti_index/ is not rendered properly in chromium browser.

Correct the typos

Correct the spelling mistakes:
Imformation Technology - Information Technology

Found error while trying to signup and login for the participant

Remove django-bootstrap as dependency

Remove django-bootstrap3 as dependency and add it as a simply downloaded bootstrap file in the static folder.

Complete the minimum plan

• Override the accounts to get a type attribute in it.
• Create the base app.
• Get the first view for participant i.e. the signup view working.
• Get the login view working.
• Create all the templates for participants.

Remove django-bootstrap from requirements

Remove the django-bootstrap3 package from the requirements.txt as it is not required anymore.

There is no need for the models in overridingAuth app.

The purpose of using models in overridingAuth app is fulfilled by the use of User groups. So, there is no real need of them now.

Redirect from login and signup pages if the user is already logged in

If the user is already logged in there is no point in sending him/her to the login and signup pages.

Clicking on add profile doesn't opens up the correct URL

We have not added the correct URL in the href of the add profile card. Change it to the relevant URL i.e. /add_profile/

Convert the function based views to class based.

There are some function based views. Convert them into the class based views.
Use this https://docs.djangoproject.com/en/1.11/topics/class-based-views/intro/#using-class-based-views

If possible change the name of the app to something relevant