View · Search · Index


Filtered by date 2020-05-01, 1 - 9 of 9 Postings (all, summary)

Site Wide Image Upload Widget

Created by Dave Bauer, last modified by Gustaf Neumann 01 May 2020, at 04:50 PM

MGH and Solution Grove are collaborating on a new image upload widget that will hopefully be easier to use and more easily integrated into any Xinha text element. 

Here is how it will work. The user will be editing the content of an object using a rich text editor (XINHA). If they decide an image or reference to a file is needed in the content, they can click the attach-file or attach-image icon.  A popup window appears allowing the user to choose a file to upload. The file is uploaded and stored in the content repository. If it is an image a thumbnail will be generated and linked to the full size image. When the content of the object is saved, the content is scanned for references to files or images, and a link is stored in the database that the particular object is "using" a file or image. This is the simplest case. Some more complex cases include allowing the user to search or browse images they have previously uploaded in a popup window to choose and image to insert.

The use case we are trying to solve:

  • In assessment, right now an admin can associate one file or image with a question. The admin can already enter HTML for the question description. We need to allow image upload from Xinha so the admin can add an arbitraty number of images to one question description. We need this functionality in any richtext widget within the assessment creation process. 



  • upload image without thinking about where it will go, just entry optional title, description and choose a file from your Desktop
  • image will have parent_id=package_id where its created.   if an object is used in multiple pages, we will keep track of that and let the owner see where it is used. We'll need to write a parser to extract /image/ url links. (DONE uses application_data_link feature from acs-tcl)
  • image will inherit permissions depedning on the setting of the user. In general it'll inherit from the package_id or the subsite where its created.
    • To avoid namespace conflicts we can do someting like this for the
        • = '{$item_id} {$filename}' or automatically rename the item filename(1) (2)...  (DONE, we strip the item id on display)
    • Image may be "private" which means it does not inherit permissions from any other object. This means the only person who can see it is the owner. If the image is uploaded within the context of another object, ie Xowiki page, a link is created between the page and the image. If someone has permission to view he page, they can also see the image. We make this work by creating a special URL /image/${image_id}/private/${xowiki_page_id}/${filename} This generated a unique URL that includes the "viewing context". When this URL is accessed 1) the system is checked to make sure a data link exists, that is, that the image is used "in" the viewing context object, and that the viewing user has permission to see the viewing context object.
  • User uploading image will be granted direct "admin" permission over the image  DONE
  • images will have a centralized URL for delivery, ie: an acs-subsite/www/images.vuh similar to o.vuh so urls will appear to be /images/${item_id}/image-filename.jpg (for example)  (Thanks to gustaf to notice the obvious namespace conflict with just using filename)  DONE
  • images are stored as image type in the content repository (stored with "file" storage type) DONE
  • thumbnails will be generated (propose to use the image-magick package, I have some code to contribute that will process an image upload and generate a thumbnail (this will be disabled if image-magick package is not installed) 
    • A new image thumbnail API is DONE

Once we have this in place, we have a simple, site-wide solution to upload image attachments to any object. This can be used in places like forums etc, and solves the problem of figuring out how to configure each Xinha widget in every package to find a place to store images.  By attaching the image directly to the object we solve the issue of finding a place to store images.


Future Ideas


These ideas are not planned for an initial implementation, but definitely are on our TODO list

  • Add a UI to browse images you uploaded
  • Add a UI to allow users to browse any images they can read?
  • Add a way to search metadata on images when choosing an image so when you choose the add image button in Xinha, it will allow you to search existing images you have uploaded
  • Add a recently viewed/uploaded feature to the image picker, so you can choose an image you recently viewed or uploaded without searching for it
    • Here is an example of what that could look like (actual working code exists for this now)
  • Add a clipboard feature to the image picker, so you can use the optional clipboard package to mark an image in your clipboard while viewing it, then choose it from the clipboard to insert a link into another object. 




2006 November 3rd and November 4th (Training and Hacking Days)

Created by Carl Robert Blesius, last modified by Gustaf Neumann 01 May 2020, at 04:49 PM

Training and Hacking Days

The training and hacking days are part of the Fall_Conference_2006 and will be held in parallel at the Boston Museum of Science (details to follow).

Newbie Training for OpenACS/.LRN

This will be held in a beautiful classroom at the Musuem of Science with about 20 computers and taught by Tracy Adams.  This is an overview course designed to give you cover just enough of the right topics to lay the foundation for more advanced work.  The objective of the day will be to

1) Get hand-on introduction to the very basics
2) Get a high-level introduction to the more advanced topics and know where to go for more.


9:30-10 - Preparation time, download and explore your virtual server image 

10-11 - The Basics

  • TCL Basics - set, list
  • ADP Basics - tags
  • Templating Basics
  • Hands on exercise

11-12 - Package Management, Site Map, Request Processor

  • Package Manager, Installation Example
  • Site Map Tour - Mounting
  • Hands on Exercise - Modifying Site Map

12-1 - Basic Apis

  • Procedure Documentation - api_doc
  • URL Parameters - ad_page_contract
  • Request Parameters - ad_conn
  • Protecting pages to members
  • Logging  ns_log 
  • Hands on example

1-2 - Lunch at Museum of Science - There is no food or drink in the Museum of Science classrooms.

2-3 - Creating Packages

  • Package Info File
  • Directory Structure
  • Creating Data Model
  • Installing Package on System
  • Creating Upgrade Script
  • Upgrading
  • Adding to Site Map
  • Hands on Exercise

3-4 Procedures, Forms, Mail

  • Forms - ad_form and components
  • Mail - acs_mail_lite
  • Procedures and self documenting
  • Hands on Exercise

4-5 Database API, Displaying Multirow Database Results

  • Database API
  • Multirow/Multiple
  • Hands on Exercise

5-6 Advance Topics

  • ACS Objects
  • Permission System


Hacking Days (a.k.a. Bug Bash)


more soon

OpenACS Core Packages (oacs-core)

Created by Benjamin Brink, last modified by Gustaf Neumann 01 May 2020, at 04:48 PM

Core packages are defined in CVS. See Aliases_at_CVS

Chart showing core package dependencies according to package specification files for oacs-5-9:

chart showing openacs core packages according to package definition

Chart is available in 2 versions:

2006 OpenACS/.LRN Fall Conference

Created by Carl Robert Blesius, last modified by Gustaf Neumann 01 May 2020, at 11:39 AM


Boston, Massachusetts, USA

Harvard Conference Center 

Map (includes location, close hotels, and public transportation stops) 

Dates and Schedule

Registration and Fees

  • Registration is open. Please let us know if you need any documents beforehand for visa applications or reimbursement
  • Fees: Main conference fee is $95 (if you can not afford the cost of the conference please let us know - we will have a discounted rate and financial assistance may be available). Please see the registration page for additional details.



Average from Weather Underground

Local Airports

Logan International Airport is the airport in Boston. It is the closest airport to the conference center. Logan's airport code is BOS. International flights can land at Logan.

The Manchester Airport in Manchester, New Hampshire, and T.F. Green in Providence, Rhode Island, are airports within about an hour's drive of Boston and Cambridge. Many inexpensive airlines serve Providence and Manchester. It is possible to get from downtown Providence to Boston via commuter rail or bus. Hanscom Field in Bedford, Massachusetts, about 25 minutes away from Boston, has flights to and from Trenton, New Jersey.

Local Train Stations

Amtrak, the major American rail company, serves several stations in the Boston area. South Station is one of the area's major transit hubs. It is also on the Red Line (subway line). Amtrak also arrives at North Station, which is on the Green Line, and Back Bay station on the Orange Line.

Bus Lines and Subway



Best Western Inn at Longwood (SOLDOUT)
342 Longwood Ave, Boston, MA 02115
(617) 731-4700 or 1-(800)-GOT BEST
$159/night - "PARTNERS HEALTHCARE" rate
(try to reserve before October 16th to ensure availability)
0.5 miles from conference center

Longwood Guest Suites
63 Parker Hill Avenue, Boston, MA 02120
$132/night - 1 person occupancy
1 mile from conference center

Longwood Inn
123 Longwood Ave, Brookline, MA 02446
$119/night standard rate
0.8 miles from conference center



Looking for Roommates

(please add your name here if you are looking for someone to share a hotel room with) 

Crash Space

 (please add to these lists with a link to your user profile)


Crash Space Available:

Crash Space Needed:

Who needs a visa to enter the US?

If you are not a resident of the United States, you may need a visa to enter. If you already have a visa and need to enter the US, make sure it will not expire before you use it to apply for admission (entry) at the port. Citizens of the following 27 countries do not need a visa to enter the US for tourism or business for stays of 90 days or less [1]:

Andorra Iceland Norway
Australia Ireland Portugal
Austria Italy San Marino
Belgium Japan Singapore
Brunei Liechtenstein Slovenia
Denmark Luxembourg Spain
Finland Monaco Sweden
France the Netherlands Switzerland
Germany New Zealand United Kingdom

[1] Providing you meet the visa waiver criteria:

a) You must have a machine-readable passport (this means it should have a line of chevrons (e.g., <<< ) valid for six months past your expected stay in the U.S.

b) Any passport issued after October 26, 2005 must include a digital photo.

c) You must have a ticket going out of the US. I.e. only a one-way ticket into the US is not sufficient.

Information for Canadians

Canadian citizens generally do not need either visa or passport to enter the US. All travelers should bring evidence of their identity (e.g., a government photo-id) and citizenship (e.g., a passport; or a birth or citizenship certificate). Fiancees of US citizens, or spouses of US permanent residents, may need a visa even if they are Canadian citizens — especially if they are coming to the US to await final immigration status. .

Getting a visa

To get a visa, contact the nearest US Embassy, Consulate, or other authorized institute to find out how long the process will take (generally anywhere from 3 to 45 days).

Some guidelines for painless visa processing:

  • Ask us for a letter of invitation.
  • Start applying for a visa early. The basic visa process will not take this long, but you will want time to resubmit the application if necessary, and to buy your tickets after the visa has been granted.
  • Prepare for your visa interview/application. You should have
    1. Your entire travel itinerary, from when you leave your country to when you return

      Note that your travel plans depend upon early approval of the visa application

    2. Your invitation, and printed information about the conference

      If you are getting financial support to attend the conference, make sure you have printed documentation of this as well.

    3. Proof of association with OpenACS and/or .LRN (information about you as a researcher, developer, .LRN user, etc.)
    4. Evidence that you will return home -- that is, of "binding or sufficient" ties to your home country (normally your country of residence). Useful examples include:
      • evidence of family ties in your home country
      • evidence of property ownership
      • evidence/statements of bank accounts
      • an employment contract or letter from an employer demonstrating you have employment beyond the end of your trip
      • evidence of attending school, or a letter from a school official demonstrating you will be a student there beyond the end of your trip

Getting visa help

A letter of invitation alone does not guarantee you will be issued a visa. If you have followed the above steps, and your visa application is rejected, let us know immediately. Immigration officials in Massachusetts will contact your embassy to try to overturn the rejection.

If you cannot afford the cost of visas or related fees, let us know. Financial assistance may be available.

Interest in Attending

Enter your name, and any topics you are interested in here Fall Conference 2006 Interest in Attending

Social Program

Dinner  on November 1st will take place at

Jasper White's Summer Shack
Starts at 8:00PM
50 Dalton Street in the Back Bay, Boston, MA
across from the Sheraton Hotel entrance and the Hynes Auditorium. Upstairs from Kings Bowling Alley.
Closest Subway T Station: Green Line - Hynes Auditorium.

The social program on subsequent days will be informal and will be announced at the event




 MGH LCS ACSPropel  Solution Grove 


File Storage

Created by Robert Taylor, last modified by Gustaf Neumann 01 May 2020, at 11:37 AM

I added views support to file storage folder-chunk as can be seen here: 

Furthermore I added the ability to download checked files (instead of having to download the whole folder). THe name of the zipfile will be the name of the folder you are looking at (so the same as if you download the whole folder).

As the file is zipped, this effectively lets you download a compressed ZIP file, so you don't have to download that much data.

just playing around

Created by Robert Taylor, last modified by Gustaf Neumann 01 May 2020, at 11:36 AM

One stormy night I was bored ... and this was born:


1.  Some links to other design work ideas:





2.  I was playing around with a screenshot of the other night and I wanted to see what the site would look like  with the following criteria:

a) REUSE all standard OACS components.  No funky layouts, no funky font work, just standard OACS out of the box layout and components.

b) SIMPLIFY the design.  Don't change anything, just remove the unnecessary design components already present.  We should NOT get caught up in a multimonth redesign sessions that takes forever to implement.  Modify what we have and make it look unified.

c)  Consider the UTILITY factor of the website.  I don't want to think about the website as a 'special use case' of our toolkit.  I would like to re-use our own tools as much as possible.  Out of the box the site would default to XoWiki for the content management, we would have the bt, cal and forums tabs as normal.  I was playing around with having a PM (pm needs some cleanup) and SEARCH tabs for advanced search and for project managing oacs based activities by those of us that want to use that tool.


3.  The oacs logo was stripped of the alex graphic.  It was kinda goofy and I'm going to try to work on something and see what I come up with.  Maybe we can holda contest for the logo ... the joomla team ended up with a pretty cool logo as a result.


4.  I will create a sample site layout here and make it available online live for evaluations by everyone.


5.  Here is the sample i was playing around with:

OpenACS Proposal - Sample

Created by Ryan Gallimore, last modified by Gustaf Neumann 01 May 2020, at 11:36 AM

OpenACS – Open Source Software Initiative

OpenACS has a proven suite of collaboration tools that are in current use by nonprofits, educational institutions and commercial companies worldwide.  Internationalization (I18n) is currently being completed by Heidelberg University.  Building on the strength of OpenACS, this project can focus on making the tools work effectively for NGOs rather than tool creation.  New features or feature enhancement will be developed when needed, but emphasis will be placed on using existing code and resources.

This project will customize the user interface and information architecture of existing OpenACS functionality to support multi-national grassroots communication.  It will also create an easy to install version of OpenACS based on these customizations.  Combined with enhanced and specific documentation it will make a very sophisticated multi-lingual community system available and accessible to XXX and other NGOs alike.  Finally, the project will also create educational marketing material aimed at multi-national grassroots NGOs to make them aware of this new resource.


Unified Toolset

On-line collaboration typically uses a variety of tools.  A well-constructed application uses them efficiently.  The figure below was created for marketing purpose to educational institutions; nonetheless it is a good image for understanding existing and planned OpenACS functionalities.



Modularity is wonderful for quickly assembling exactly the application you need.  Maintainability is enhanced in OpenACS when similar modules share the same basic functionality.  Thus, from a more technical perspective OpenACS is a layered architecture with many packages that provide diverse functionality to end users; it relies on common underlying structural packages such as the content repository, notifications, date-time space, authentication, and context search.  This structured approach allows the easy creation  of specialized, yet unified, new functionality with a minimum of separate and new code. 

Mature Broad Based Developer Community

OpenACS traces its roots back to Philip Greenspun, a Computer Science Professor at MIT, and his work on starting in 1995 and Philip and Alex’s Guide to Web Publishing in 1998.  The code base has always emphasized collaboration and management of geographically diverse online communities.  The underlying engineering was supported by millions of dollars of venture capital spent on hiring PhDs in Computer Science from MIT, CalTech and other major universities across the Atlantic.

OpenACS has proven its durability and utility by surviving the death of its parent company (ArsDigita) to grow into a vibrant grassroots collection of independent consultants and small companies implementing diverse and complex web solutions around the globe for fun, philanthropy, and profit.

Example OpenACS Implementation - dotLRN

dotLRN is an application built on top of OpenACS specifically targeted for universities.  A consortium lead by the Sloan School of Management at MIT and Heidelberg University has significantly improved enhanced OpenACS.  In many ways this project will be philosophically modeled after dotLRN.  It will create an application built on top of OpenACS that is specifically targeted to NGOs needing web based community tools in a multi-lingual environment.

This project will also build directly upon functionality implemented by dotLRN. Especially important for this project is the strong emphasis on groups, subgroups and distributed administration.  In Learning Management Systems (LMS) it is very important that instructors have extensive control over membership, content and presentation.  Designated XXX leaders will reuse this functionality extensively to allow the project to have self-managing geographically diverse and common-interest groups and subgroups that can be managed locally without extensive time commitment from the parent organization.

One goal of this project is to deliver a code base that has significant overlap with dotLRN.  This is desirable from a sustainability and maintenance point of view because enhancements and bug fixes made to the dotLRN community will be available to the NGO community as well.  OpenACS’ layered package system is designed to support this type of code reuse and make it possible to have specialized code easily segregated from customized code for enhanced maintainability.

Case studies on dotLRN can be found at: 


Active Development

OpenACS is continually being improved, often in ways that will be useful to nonprofits and NGOs. Currently there is active development of the following features.

  • E-Commerce G2
  • Xowiki
  • dotLrn

Although many of these features will not be immediately used in the XXX site, they will be vital for the future sustainability and expandability of this project, giving the project the ability to be quickly extended to meet the needs of a multitude of NGOs.

Service Providers Available Globally

The product produced will be a custom installation of OpenACS that any OpenACS company or developer would be able to support.  Currently, there are consultants and companies that provide support for OpenACS in the following countries: Australia, Belgium, Brazil, Canada Denmark, Finland, Germany, Guatemala, India, Israel, Italy, Netherlands, Norway, Philippines, Spain, Sweden, Switzerland, UK, US,.

Standards Compliance and Interoperability

OpenACS has strong and continuing support of standards that will enable this project and future extensions to share content and interoperate with other systems.

The Simple Object Access Protocol (SOAP) web services – a way to create widely distributed, complex applications that run over the Internet, has already been incorporated into some OpenACS packages and research is underway at the University of Sydney into further uses of Web Services.

OpenACS also includes a RSS Support Design Module to support the RDF Site Summary (RSS), an XML-based, lightweight multipurpose extensible metadata description and syndication format.  RSS support positions OpenACS for future functionality requiring accepting and distributing syndicated news feeds and other RSS-compliant content.

The OpenACS WAP module supports the wireless access protocol (WAP), thus allowing easy deliver of content to WAP-enabled devices such as cell phones, PDAs, etc., as well as regular desktop browsers.  In fact, the simplicity of the OpenACS interface means it is well suited for use on mobile clients. 

OpenACS and its dotLRN consortium are committed to implementing the Sharable Content Object Reference Model (SCORM), Instructional Management System (IMS) and Open Knowledge Initiative (OKI) standards, all among the most widely used standards for learning object interoperability.


How to configure a Network Place under Windows XP to access file-storage via WebDAV

Created by Robert Taylor, last modified by Gustaf Neumann 01 May 2020, at 11:33 AM


How to configure a Network Place under Windows XP to access a WebDAV folder in file storage. 


Creating a Network Place will allow you to drag and drop multiple files and even folders from your machine to your OpenACS or .LRN  website. Once you have done these eleven (arguably ten) simple (really!) steps to create a permanent connection on your computer to your file storage location. The Network Place will be accessible through My Network Places.

Once you have established a Network Place to your File Storage documents, you can transfer multiple files, create/delete/edit folders, delete files. Creating and modifying files and folders through the Network Place is the same as you would do using Explorer. You can also open, edit and save files without the hassle of downloading, saving and uploading them on your machine!



Step 1: To create a Network Place, open Windows Explorer.

Then, right click on "My Network Places" and select Open.


Step 2: Under Network Tasks, Select "Add a Network Place."


Step 3: Click "Next" to start the Wizard.

Step 4: Highlight "Choose Another Network Location" (if it is not already) and click "Next."



Step 5: Copy the WebDAV URL listed in the file storage folder you want to access and paste it in as the "Internet or Network Address" for your connection.


Step 6: Select "Yes" when you are prompted with the Security Alert dialog.


Step 7: Enter the email address you use to log into the site (or username if your site uses usernames) and password in the "Connect to:" dialog box. This establishes your connection to the Network Place.


Step 8: Create a name for the new Network Place or accept the default and then click "Next."


Step 9: Leave "Open this network place when I click Finish" checked.

Click "Finish" to complete the Wizard.


Step 10: The first time you do this, you may be prompted again with the Security alert and a login screen. Please say "Yes" to the alert.

Step 11: You may also need to login again using your site email address and password. (This is a Microsoft thing, not a bug and we can't do anything about it.)

Voila! Your new Network Place will open and you will see the folders as they appear in file-storage on your site. You can now open Explorer and select, drag and drop multiple files or folders from your machine into SloanSpace. After you do this, refresh your browser to see the files/folders.

The Network Place is permanent, so you only need to set it up once and reconnect to it when you need to (through My Network Places.



Created by Emmanuelle Raffenne, last modified by Gustaf Neumann 01 May 2020, at 11:20 AM

Package Specification Summary for Package: calendar

Summary: Personal and shared event calendars.
Description: Manage group and shared calendars with download.
Documentation: Package Documentation
Maturity: Mature
This package depends on: attachments acs-datetime acs-events acs-lang notifications ref-timezones acs-tcl acs-templating
Packages that depend on calendar: calendar-includelet calendar-portlet evaluation project-manager
Package parameters:
Allow Files to be Uploaded (default 0, type number, scope instance)
The default list for this instance of calendar: one of day, list, week, month. Defaults to day. (default day, type string, scope instance)
Period of time that is shown in the calendar by default [in days]. Can be changed by admin for each community. Defaults to 30. (default 30, type number, scope instance)

Bug Tracker Summary for Package: calendar

Open Bugs: 14
All Tracked Issues: 96
Latest Bug Opened: 2018-04-02 orphan acs_activities and recurrences
Latest Bug Fixed: 2018-03-20 Calendar fails automated test: Test case acs_tcl__tcl_file_syntax_errors.
Top Bug Submitters: Nima Mazloumi (10) Caroline Meeks (10) Dirk Gomez (6) Carl Robert Blesius (6) Eduardo Pérez (5)
Top Bug Fixers: Dirk Gomez (43) Emmanuelle Raffenne (12) Lars Pind (9) Peter Marklund (5) Don Baccus (4) Gustaf Neumann (4) Deirdre Kane (4)

Code Metrics Summary for Package: calendar

# Tcl Procs 54
# Tcl Lines 1485
# Tcl Blank Lines 254
# Tcl Comment Lines 159
# Automated Tests 2
# Stored Procedures PG: 10 ORA: 12
# SQL Lines PG: 845 (blank 127 comments 138) ORA: 914 (blank 144 comments 160)
# ADP pages 18
# ADP lines 655
# Include pages (calendar/lib/) 0
# Documentation pages 3 (Package Documentation)
# Documentation lines 652
Browse Source API-browser


Suggestions for improvement (from /forums/message-view?message_id=432244 ):

  • different colors for different calendar sources
  • easy and nice printout of week and monthly calendar
  • Possibility to link one calendar item to many classes or community on creation or editing
  • Attach files
  • Change of repeating events after creation (if you have a different repeating sequence there is no way of changing the sequence)
  • Site-wide calendar for holidays
  • Department-wide calendars.

Sync contacts with contact managers, palm pda's etc.

Note I see a small potential issue. Within one calendar it makes sense to color code by calendar types. When using dotLRN or otherwise aggregating calendars it makes sense to color code by calendar_id (source). It probably never makes sense to do it both ways on the same site. We may need to think this through. 

Text taken from Dirk document (2004)

Maintained by Dirk Gomez - last change on 22-Jan-2004.

I am tracking my work on calendar here. Please get in touch with me if you have comments.

Features Completed

  • Separated code and presentation
  • Notifications
  • Removed unused or duplicated code and database queries.
  • Proper use of OpenACS permissioning.

Features I am working on currently

  • Code clean up
  • Documentation of the data model

Features I will be working on

  • The calendar view templates take a lot of parameters some of which require knowledge of the inner workings of the respective template: e. g. currently the calling templates passes in a url_template which determines whether an action on a particular item can be executed. I'll move this to being proper and understandable parameters like create_p or edit_p.
  • New parameter Collaborative Calendar: a parameter that allows every user of a community to add, edit, and delete events if set to true.
  • New parameter in DotLrn: parametrize whether to show calendar lists for a whole term.
  • Allow users to store calendar preferences for example the user default view. The calendar_preferences table already exists, yet isn't used at all.
  • Add a toggle: "Show all my events/Only this package's or community's events"
  • Use a site-wide categories package to do away with the calendar types and the multiple calendars per package.
  • Reminder - make it possible that a user sets a particular time on a calendar item to receive a reminder email
  • Multi-day events
  • iCal format compatible. Ideally, import/export to Outlook/iCalendar/etc.. via iCal format (by Jade)
  • Ability to map any sort of date information in a database to the calendar, this means tickets, bugs, etc. perhaps via a service contract (by Jade)
  • There should be any easy UI for specifying what is shown. Both the user and the admin should be able to select these things (the admin sets the range of what is possible, the user can select from those choices) (by Jade)
  • Events should be able to span more than a day. Ideally, the UI for this should look good. (by Jade)
  • An ability to be able to add data via the calendar as well. Anything that implements the service contract should allow you +to add information on that date as well. For example, add a ticket due that day, or add an event for that day, etc.. (by Jade)
  • The calendar needs to be printable (at least for where I work - Jade)
  • Desktop and Handheld support - cross-browser and cross-platform compatible (ryan-g2)
  • Filters by calendar, keyword, object (e.g. Show all bug deadlines) 
  • Public event submission (unauthenticated) approved by an admin (ryan-g2)
  • Invite people to events (ryan-g2)
    • auto-book invitees if preference enabled, otherwise, require confirmation
    • if there is a conflict among registered users' schedules, the systems suggests possible times to the inviter.
    • people external to the system can be invited.
  • Resource Scheduling - Booking (ryan-g2)
    • Schedule one resource (room, car, laptop) per calendar
    • Non-simultaneous booking (no overlapping times)
    • Book an item: suggest alternate times across multiple calendars if asset is unavailable.  Example: 5 Smart Cars for rent each have their own calendar; if all are booked from 10 - 11 AM, suggest 9-10 or 11-12 across all calendars.
    • Optional bill for booked time (connect with ecommerce module)

Data Model Suggestions

Calendar items should map arbitrary objects (perhaps only content items) to a given calendar and given acs-events. We shouldn't have to derive special types from cal item type in order to attach it to a calendar (nor should we have to duplicate content to attach it to two calendars as we do now) If we restricted the mapping to content items (i.e. calendar info some sort of content type) we could use the CR's ability to map a template to a given content type or item to make it possible for the calendar package to display calendar item details using that facility, giving the package adding something to the calendar control over how it is displayed. Much more general.

Is it possible to optionally link any acs_object to an acs_event object (event)? Examples:

  • People attached to a meeting event
  • Bug item attached to a deadline
  • Location attached to a meeting event [google maps integration]
  • Project item attached to a deadline
  • Simple time and description (for booking an asset) -- unattached to an object
  • Multiple objects: Rent a car C from Time A to Time B and pick it up at Location L (Event linked to two objects C and L). See

From above: "Use a site-wide categories package to do away with the calendar types and the multiple calendars per package."


Features I started work on

I'm listing stuff here on which I am already working, but whose completion is nowhere near finished and there is not even an estimation when it may be finished.

  • Integrate libical into AOLserver
  • Lift as much as possible from Brandeis' Calendar, see this forum thread

Interesting Links



June 12, 2006 - Solution Grove worked on an AJAX calendar month view that has colors by calendar_types, has mouse overs for item details for each date, and changes months without refreshing the pages. They hope to contribute it at some point. Contact Caroline or Hamilton from Solution Grove if you need an advanced copy.

previous May 2020 next
Sun Mon Tue Wed Thu Fri Sat
26 27 28 29 30 (9) 1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 (1) 21 22 23
24 25 26 27 28 29 30
31 1 2 3 4 5 6

Popular tags

17 , 5.10.0 , 5.9.0 , 5.9.1 , ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bootstrap , bugtracker , CentOS , COMET , compatibility , CSP , CSRF , cvs , debian , emacs , engineering-standards , fedora , FreeBSD , guidelines , host-node-map , hstore , includelets , install , installation , installers
No registered users in community xowiki
in last 30 minutes