You are here: Home old structure Teams IT Team Specifications Events

Events

event system spec:

  • each cp can add/edit/delete events for his/her lc
  • invitations for events are created through the event system
  • special events (congress) can only be created by board members
  • board members can grant these rights to persons
  • lcs are encouraged to add all the previous events they already organized for the completeness' sake

required event data:

  • name
  • start date
  • end date
  • description
  • type (dropdown) (new types should be possible to create)
    • workshop
    • exchange
    • internal (nobody invited, but worth mentioning)
    • custom (description of customness in descpription)
  • date created
  • date last modified

optional event data:

  • number of participants
  • application deadline (date)
  • invited lcs (all, selection of lcs)
  • before event images (for describing the event)
  • after event images (for showing how it was, however this should be only a smaller selection of images)
  • images may have descriptions
  • eventually image should be replace by image/sound/movie
  • report by lc
  • report by anybody
  • for spec of report see report system spec
Document Actions

Required event data

Posted by Ceh at Sep 13, 2005 07:33 PM

Under section TYPE: We should also include leisure and fun events, which are event's that usually take place in the summer with the small fee. (e.g Riversplash, Tunnix,....)

Borut

Custom events

Posted by techmage at Aug 04, 2006 06:35 PM

But those qualify as custom events.

Notification of the CP's about events

Posted by Ceh at Sep 24, 2005 10:01 PM

When a ceratin CP enters in the event specification, all cp's shoud be informed about this(We should also discuss if the invitation to event is sent to every LC or an organizing LC CP chooses to whom the invitation will go). How? An e-mail is sent to the CPs informing them about the upcoming event. This shoudl be only a short specification in which there would also be a link to the www.eestec.org, to the event section, where every single CP could apply people form his/her LCwith all the neccessary data: >Name >Surename >Nickname >Picture >Studies (which year, which field) > Need visa or not >other special needs >Medical problems >......

. Similar was made in the Madrid congress.

Notification

Posted by tijana at Sep 27, 2005 03:54 AM

I think all the CPs should be informed if an EESTEC event is taking place. An notification message via e-mail with event title and link to our site, would be great. Organizing LC of course holds the right to choose the participants.

Madrid Congress application system was really good (people apply, get(or not) to be approved by their CP who also define the priority of the applicants, organizaing LC defines number of places for each LC that applied (none places also possible), and first X people get to participate in the event. I hope it will be possible for all EESTEC events.

notification

Posted by Florian Friesdorf at Oct 01, 2005 04:49 PM
Everybody should be notified, but not necessarily invited.

Publishing an event / Applying to event

Posted by Ceh at Sep 24, 2005 10:13 PM

If we are doing a system, to reduce all the extra work of the CPs, trying to explain who is invited, who can come who cannot come,..etc I think we need the following: Organizing LC - Wehen "publishing" an event: You beed to specify who can come. By that i don't mean the LC's, but the level of stuidies. E.g. If the requirement for applying to workshop is EE-telecommunicatoions only 4th and 5th, and + year there shoudl be an option to write this in it. Appying to the event: CP that will aplly the particiapnts to the event (let's say event i desribed above) can't apply anybody else than Telecomunications 4th and 5th year and + year!!! there shoudl be also an option to send a special request to an CP from the organzing LC, for participants who don't meet the criteria to apply, but could also may be be accepted. Then the CP from the organizing LC answers on the request for application.

It would be also very useful to have some info on the particiapnts. For example (eneterd by the CP who applys his/her LC members): > active EESTEC-er or not (just to see how many others that are not YET in EESTEC are we attractiong with our events) With this entries we would be also able to see how on how many exchanges someone has been and how many active EESTECers, alumnies and (at the moment) non-EESTECers (that are hopefull gonna become EESTECers) are we moving around Europe with our events.

borut

danger of bureaucratization

Posted by Florian Friesdorf at Oct 01, 2005 04:21 PM
Good ideas in - however we need to make it also fit to what EESTEC is. Means if a CP wants to have only 4th and 5th years, then this information should be visible for people registering and a CP should get these people listed first. However I think it should be possible to register also, if not 4th or 5th year - it just needs to be seen later.

Another point is, that at the moment often LCs are sending people who are not yet a member - which is a very convenient method of making them a member. However normally they dont have a web account at that stage. So either they first need to create a web account (maybe with stage newbie) or they need to be registered in a different way by there CP.

I don't like the idea of the different way. However, this needs to be discussed.

Event req and participants

Posted by techmage at Aug 04, 2006 06:40 PM

One field would have to be a link to the event website (optional of course) (for more in-depth informations)

Let's not fix everything in a web structure yet, adoption of the portal, as useful as it is, will be slow, also new members will have no clue about its usage. Will-be members even less.


Partners and sponsors: