This is the draft of the drafts of the design specs of event management system to help streamline event organising. Attached is the database design. Probably using Paladin
All are welcome to comment and criticise. IP however remains with SgDotNet.
----
Opportunity
SGDotNet has a simple event management system in place. Whenever there is a new event, the event organiser first manually creates a registration page, which contains information about the event. He does so by
When the event draws near, the event organiser has to open the file, for each record inside the xml file, he has to use the community server admin page to check out the member's email address (if the email has not been collected) and send a mass mail to attendee any additional information that was confirm since then.
Problems faced
The current way is mundane, and time-consuming. Council members are voluntary, and most likely to have a day job. The time spent on the above task might take 30 minutes to 2 hours, collectively, which could otherwise be used to attend to other user group matters. Therefore, the council members are looking at ways to streamline this process.
Vision Statement
Streamline the event organising procedures to reduce the time needed to handle the planning and necessary follow-up work of each event.
Scope of the Project
This project seeks to provide a web-based interface of managing the events. It also seeks to have the necessary integration with community server, like authentication and roles. This project must be able to integrate with DotNetNuke, which SGDotNet is waiting for the integration module of DotNetNuke and CommunityServer to be completed.
Feature / Function List
The project will be divided into phases. Please refer to the various project phase requirement specification for more details
Administration Modules
Admin modules allows members with the necessary access rights to manage events. There are different sub modules in the administration, mainly
User Groups Management
Currently, in SGDotNet, there are two user groups, the main user group, and the Student user group. This module allows the system to manage events for different user groups, and to cater for future expansion of SGDotNet.
Access Rights Management
This module allows administrators to manage which role is allowed to perform what tasks. The roles will be taken from Community Server, and the access rights granted applies only to one user group.
Events Management
This module allows users to manage events, whether its seminars, practical session or social. This should be flexible enough to be used as a purchase form.
An event is deemed to be a seminars when the topics are defined for the meeting.
An event is deemed to be used not as it is intended when publish is set to false. Setting publish to false causes the event not to appear on the events page.
The events management module must be flexible to collect any information that the organisers requires. Therefore it has a page that allows organiser to define what is to be collected, the way (like using choice fields, or combo boxes), and the datatype of the information. The module would probably store this information in xsd format, or xml format.
Topics Management
This module allows users to specify what topics will be covered in the event, and who will be speaking on that topic. It also allows users to post attachments as and when it is available.
Venues Management
This module allows users to manage venues where events would be held.
Speakers Management
This module allows users to manage speakers, and their profiles
Notification Management
This module allows organisers to mass mail attendees about any latest information they need to disseminate
Registration Management
This module allows organisers to view the attendees and the information collected. There should be a print function which prints the information collected, as well as attendance sheet
Best Regards, Kit Kai, MVP (SharePoint Portal Server)
Tentative meeting date is 6th June, around 7:00pm, either at Microsoft, or at my office.
Microlau, Zhong Qiang and Web Team are requested to be present.
Council members and interested members are welcome to attend. Do indicated your attendance pls.
microlau Blog: http://community.sgdotnet.org/blogs/microlau
kitkai wrote:Oh yah, any suggestion for a code name?
BlackDot
ImeldaMercuryOrionOrblusCamomilePoseidonRombus
My $0.02.
Venue - Add URL field
Speakers - Add Blog field
Add Agenda table between Events and Topics - Primary reason, we sometimes slot some stuff like quick talks etc but those are not topics. (e.g. breaks). Agenda - AgendaID, EventID (FK1), StartTime, EndTime, TopicID (FK2)
HIHs.
kitkai wrote:Tentative meeting date is 6th June, around 7:00pm, either at Microsoft, or at my office.
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral
Which code name u guys like...
As icelava has suggested for a theme, I don't really know how to decide a theme. In fact, I'm the typical developer who would call the system, "Event Management System", or "EMS".
You people got to help me out here...
kitkai wrote: Which code name u guys like... As icelava has suggested for a theme, I don't really know how to decide a theme. In fact, I'm the typical developer who would call the system, "Event Management System", or "EMS". You people got to help me out here...
Code names are just used for easy reference and to motivate the developers. You should not need to go through an extensive process of selecting code-names - this is not a "Maggi mee - search for a new product name contest". Just pick one and move on!
The core requirements of the system are more important and requires greater focus.
My worth.