Event Management Systems

hi all,

i want this functionality for a conference website:

users can submit papers, emails are sent to the users to confirm that their paper been received
all the submitted papers will have a link to the conference event page
conference event node shows a list of submitted paper titles
submitted papers are only viewable by the Judge role members only
judges evaluate the papers

how to implement these?

thanks,
enky

We've posted a draft specification for CiviEvent (phase 1) on the wiki. We are actively soliciting community feedback prior to
finalizing the specifications on or around December 7. If you are interested in an integrated Event Management component for CiviCRM -
please review the spec carefully and post your feedback and questions as comments on the wiki.

http://wiki.civicrm.org/confluence//x/eyQ

This specification reflects feedback and suggestions from many folks in the CiviCRM and Drupal communities. We'd like to especially thank
and acknowledge Jeff Porter of The Foundation for Pr

Here's the low-down on the upcoming.org integration module:

Per the developers description: The upcoming.org module enables you to import events and venues from upcoming.org and display them in a calendar using the event module. Upcoming.org is a website that helps you share and keep track of your events. Synchronizing (using upcoming.org as the master repository) is also supported. Additionally, this module exposes the upcoming.org REST API, making clients written to use it interoperable with Drupal. This makes it possible to build a whole network of websites sharing their events, all using a defined API.

Not sure where to tell people this, but here goes...

So, after much goofing around with Views, Location, Gmaps, node_import and a bunch of other stuff, I have come to the conclusion there is no reason to support eventfinder going forward. A savvy admin can configure about 90% of what eventfinder does with other modules at this point, and I am about to release a write up about it. There were 2 things killing that module, one was the external depenencies and need to update it pretty much every 4 weeks, the other was the fact it was hard for a lot of people to configure. No matter how much documentation I provided people were still not figuring it out.

I’m the current maintainer of the eventrepeat module after hunmonk handed the keys over to me this summer. We’ve done some initial work redesigning the interface to bring it into the node form and we are looking to push the code to a new 4.7 version very soon. I’m inviting all the people interested in using eventrepeat with events to take a pass at testing and give some feedback.

Obviously, we are currently more interested in making a deliverable, working module than adding in non-critical ui and api feature suggestions. After we get a solid 4.7 version, we’d like to get a 5.0 version. At that point we will be open to suggestions for non-critical support and features.

Since part of the purpose of this group is to track views development, I thought I would share my solution for creating flexible date range arguments for the Date module.

Creating arguments for date fields is hard because there are so many possible ways people might want to use them. You may need to find a full date or a part of a date or you may want to look for a date + duration or maybe specify that the duration will start on the current date or some other date, etc. etc. In creating arguments for dates I have been finding that the list of arguments in views gets longer and longer, but no matter how many you create, someone will always come back and ask for another type of argument.

I have been playing with the Timeline project from simile.mit.edu.
http://simile.mit.edu/timeline/

The Timeline project delivers a scrollable, DHTML timeline which is analogous to the Google Maps interface (as seen in GMap module) except this shows a timeline of nodes. This project is new and under active development, but working mostly.

The attached module requires views module. It provides 2 views plugins: Timeline Horizontal (works) and Timeline Vertical (does not work due to bug in Timeline project). It also provides the beginnings of an API of sorts, where you can programmatically make timelines. E.g. this function

In my opinion, the use of timestamps for the representation of dates in Drupal core is problematic. It is fine for recording all events that happen now, and it is even fine for recording historical events, as long as they happened 1970 or later. They are utterly useless if you want to make a geneology site.

More disturbingly, the event module also relies on timestamps for representation of events. As far as I can tell, this is a huge limitation. The CCK date field uses the ISO 8601 standard which saves times as as string: 20060610T20:47:48+01:00. While there are lots of arguments about how the data should be persisted in the database, to me, it is clear that the ISO 8601 string is ideal for representing the date in Drupal code (unless you're doing archeology, then I've got no idea what you do with BC dates).