Events portal

[AbdealiLoKo]

@phanikaran This needs to be release in about a week.
Whats the status

[AbdealiLoKo]

Reminder.

[AbdealiLoKo]

Reminder 2

[AbdealiLoKo]

updates ?

[AbdealiLoKo]

Phani, reminder

[AbdealiLoKo]

Utture tasks which we had discussed :

• - Make tabs in events
• - Show contents for the tabs
• - Edit content of tabs
• - Delete tabs
• - Edit name of Tab
• - Allow only event coords to edit the event details (and cores and supercoords and QMS)
• - Participant login (Shaastra ID creation)
• - Event registration for participants
• - Participant dashboard to find event information

Will add more later

[AbdealiLoKo]

updates ?

[akshayutture]

Finished the tabs part - add, delete and edit tabs (combined the editing of name and content of tab). Should I do anything else?

[AbdealiLoKo]

check the checklist on top. and check everything done, there are a few things left - like allowing event coords only to do it

[AbdealiLoKo]

Event coord can only edit their own.

Core, supercoord, qms can edit any.

So, make a separate function to check this. If we want a new type of user
to be able to edit, we'll simply edit that function, and everywhere else as
this function will be used, itll get changed everywhere. plus, where can i
see the stuff u made ? im assuming u made a test template ?

On Sat, Jul 5, 2014 at 3:19 PM, akshayutture notifications@github.com
wrote:

Is this the specification - Allow only event coords to edit the event
details (and cores and supercoords and QMS) - So an event co-ord can edit
event details of any event or just their subdepartment events?

Reply to this email directly or view it on GitHub
#80 (comment)
.

[akshayutture]

I uploaded the stuff to github. The view and event-tab model is at apps/events. The url to see it is at localhot:8000/events/add_tabs . The html file is at templates/events/events2.html. . .

If a co-ord has co-ord relations with more than one sub-dept, he should be able to access every subdepartments' edit pages right?

[akshayutture]

some clarifications

1. Its a little difficult to give only some users access to the add,edit and delete buttons, so can I make a different view for those who can access these buttons and a different one for those who cannot?
2. Can every qms co-ord also edit any event-tab?
3. To allow only those event co-ords from a sub department access event tabs from that event category I'll have to make a one to one relation between the Category (events model) and the sub department model. Is that okay?

[AbdealiLoKo]

Different view as in? Arent you doing it in Ajax? Again, dont worry whether
they can see the button or not. if they click the button it should come
"You are not allowed to edit this" << Thats the backend part

Not sure about qms co-ord - why does this matter ? I had mentioned earlier
no ? Make a function that takes a user and a event and gives out true or
false. if true, the person can change stuff, fi false he cannot. We'll
modify the conditions for the true/false later.

The event model and subdept already have a relation, check subdept model
On Jul 8, 2014 7:26 PM, "akshayutture" notifications@github.com wrote:

some clarifications

1. Its a little difficult to give only some users access to the add,edit
   and delete buttons, so can I make a different view for those who can access
   these buttons and a different one for those who cannot?
2. Can every qms co-ord also edit any event-tab?
3. To allow only those event co-ords from a sub department access event
   tabs from that event category I'll have to make a one to one relation
   between the Category (events model) and the sub department model. Is that
   okay?

Reply to this email directly or view it on GitHub
#80 (comment)
.

[akshayutture]

I created a function in which you need to put the criteria for giving permission to edit /create/delete a tab. For now I've kept the criteria that you need to be a qms or events core.

If you don't have permission, those 3 buttons won't get displayed
Is thats okay? If yes, I'll push

[AbdealiLoKo]

Push to the branch.
And push even if unsure - the branches are meant for testing out. You can
always push again
On Jul 9, 2014 12:42 AM, "akshayutture" notifications@github.com wrote:

I created a function in which you need to put the criteria for giving
permission to edit /create/delete a tab. For now I've kept the criteria
that you need to be a qms or events core. Is that okay. If yes, I'll push

Reply to this email directly or view it on GitHub
#80 (comment)
.

[akshayutture]

What should I do next? Participant login? If yes, give me the specifications