macosforgebot
commented
16 years ago gary.weaver@… originally submitted this as comment:1:ticket:210
More info about us in case you are interested (not sure how well that Darwin Calendar Server would match our needs):
- There will be about 500-1000 organizations
- There will be < 100 people requiring access to administer events for those organizations
- Each organization would like to have the ability to have some events that are relevant only to the organization (published to their "calendar") and other events that would be relevant to all organizations (published to a central "calendar")
- The concept of rights/roles per organization is very important (a student group calendar's admin should not be able to add fake basketball game events into the men's basketball event calendar for example)
- Just having events grouped by organization is not enough - they must allow categorization or tagging to indicate that an event is both a "lecture" and is "religious" for example, but that this event could belong to the "Law School" calendar (and may or may not be shared on the central calendar depending on how it is tagged)
And there are the requirements, again- only if you're interested (summarized subset):
- Avoid double-entry of events somehow/avoid duplicate events (even with all of those organizations having their own area)
- Provide ability to show N # of Academic Calendar events from today to some configurable day in the future on the same page with today's events
- Provide ability to either a random or timed rotation of N # of highlighted/featured events from today to some configurable day in the future on the same page with today's events
- Somehow downplay repeat/ongoing events so they don't stand out as much (in other words, if an event exceeds some configurable combination recurrence and or duration or cumulative duration of time, it can be displayed differently/in different place/left-out of main list)
- Support "pull" and "push" and real-time subscription to external calendars (like CalDAV connecting to newer version of Oracle Calendar, Google Calendar, etc.)
- Create role-based user accounts to force approval of event publishing (so some easy to use (even if non-GUI) workflow for approval of events.
- Enable filtering to make events easier to find (filter by tags on events, which calendars, start and end date)
- Make filter options accessible outside the tool
- Require approval for co-sponsorship (i.e. if event belongs to more than one calendar, that needs to be approved by some administrator)
- Provide documentation and contextual help
- Offer community submission of highlighted events (which need to be approved)
- Enable departmental control of content and priority (aka some concept of workflow/approval, some way to show some highlighted events more than others). Focus is for ability of department to have different content/priority for events than those events might have in the central university view of the calendar
- Feature "reminders"
- Would be good to allow easy (WYSIWYG-ish) text formatting of event description
- Allow "RSVP"ing for events
- Keep events in calendar even if events have passed already (ability to look at old events)
- Allow boilerplate text inclusion with events (have some way to specify text that can be changed in one place but that same text is updated in all future events (maybe even past events in some cases?))
- Offer option of event templates (so you can choose a template when creating an event and then basically fill in the blanks, or maybe be able to totally customize it)
- Support multiple dimensions of categorization; e.g., subject matter, sponsoring organization, format (e.g., lecture, workshop), which are independent of one another.
- Enable audience specific content/filtering
- Support Kerberos for AuthR and Shibboleth for AuthN
- Scalable for the enterprise, supporting hundreds of simultaneous users, which will include both human beings and automated software services.
- Integrate with LDAP, email.
- Interoperate with localized software services, such as various centralized scheduling systems, enterprise, school and departmental web environments, including portals (uPortal), etc.
- Secure, supporting standard encryption of data transmission via SSL, and implementing granular, custom-defined groups and roles for users.
- Support most standard clients/browsers
- Support granular, user-defined, many-to-many relationships for events, event-types, event-categories, and event-sponsors in support of the functional requirements.
- Easy administration of recurring events (can change/delete it in one place to affect all, can change/delete one event in a recurring event series without problem).
gary.weaver@… originally submitted this as ticket:210
Apologize that this is only a single ticket, and apologize in advance for my ignorance. (If I had more time and it supported Linux fully, I'd definitely check it out.)
For some reason, the tickets I created previously (a few weeks ago) got lost. Here is what I had suggested along with some new stuff:
In addition, here are some suggestions for features, and honestly I don't know how many of these apply to the Darwin Calendar Server project:
Sorry for the overwhelming and fairly uninformed (or even ignorant) deluge of stuff here. Maybe it will help in some way though.