Bedework - Bedework has been the name of this project since its inception, roughly 3.5 years ago, and is the preferred name going forward. The Venerable Bede, from whom Bedework takes its name, was a highly influential monk and scholar from the area of No
Profile
Legal
Community
Governance
Alignment
Infrastructure
Profile
Legal
Community
Governance
Alignment
Infrastructure
Description
Initial Committers
Mike Douglass (RPI) - doulgm@rpi.edu
Arlen Johnson (RPI) - johnsa@rpi.edu
Jeremy Bandini (Duke) - jeremy.bandini@duke.edu
Technology Overview
At the buzzword level, Bedework is Apache Struts MVC, CalDAV, Cascading Style Sheets (CSS), Java Servlet API, RFC 2445...2447, RFC 4791, CalDAV Scheduling, Java Server Pages (JSP), JSR-168, XHTML, XML, XPath, XSLT , iCal4j, Lucene, hibernate, jquery.
Bedework is architected and implemented to be agnostic in the following dimensions:
• DBMS
• Application server
• Authentication
• Presentation
Bedework is architected and implemented to be standards compliance, scalable, and to support Internationalization / localization of the event data and applications.
In practice, Bedework does a reasonably good job of achieving these objectives.
Community Description
Who's using Bedework is a difficult question to answer to definitively. Here are some of the organizations we know of that are currently deploying Bedework or planning to deploy Bedework:
Production - Bennington College (US), Bishop's University (Canada), Cornell University (US), Cornerstone University (US), Dalhousie University (Canada), Duke University (US),
Montana State University (US), Jahia Software (Switzerland), Juilliard (US), Montana State University (US), Public University of Navarra (Spain), Queens University (Canada)
Rensselaer Polytechnic Institute (US), University of British Columbia (Canada), University of Chicago (US), University of Kansas (US), University of Maine, Fort Kent (US)
University of Maryland, College Park (US), University of North Carolina at Chapel Hill (US), University of Washington (US)
Development - Brown University (US), JiscMail (UK), Stockholm University (Sweden), Yale University (US)
Bedework is embedded in at least one commercial product, perhaps more.
JASIG Relationships
Bedework is open source, implemented in Java, and in use by at least 7 Jasig member institutions. Calendaring is an important component of most if not all portal implementations. Bedework could also be intergated with other OSS projects of interest to Jasig, such as Sakai
Benefits to Higher Education
• Bedework Integrates with extant campus directories
• Bedework Integrates with extant campus authentication
• There are no license or usage fees
• Bedework uses hibernate to accommodate a range of DBMS systems
• Web designers can change the look and feel of Bedework without the assistance of programmers or system administrators.
• Bedework supports many different kinds of feeds - RSS, Javascript, arbitrary XML, JSON, etc - allowing calendar data to be fed to other systems, such as digital signage, departmental web sites, etc
• Departmental calendars can be individually "skinned" to integrate into departmental web sites. JSON feeds can be used to pull events into a static web page and present them in context as the web designer chooses, including within the context of a local website
• Bedework provides distributed administration with access control
• Bedework is JSR-168 (portal) "friendly", or as friendly as anything is.
• Bedework's design point is to promote interoperability between systems, and assumes that Bedework is not likely to be the only calendaring system on campus. Bedework places great emphasis on standards compliance.
• Bedework could be integrated with other campus systems such as R25, Sakai, etc.
• Bedework calendar data can be access with "non-native" CalDAV clients such as Mozilla Lightning, Apple ical, EMClient, ZideOne Outlook plug-in
• Bedework developers are almost from higher education, looking to meet the needs of higher education.
References
http://bedework.org
http://rit.mellon.org/projects/Bedework.pdf/view
http://www.news.duke.edu/2009/03/bedework.html
Incubation Checklist on wiki: http://www.ja-sig.org/wiki/display/INCU/Bedework+Incubation+Check+List
Activity
Show:
SusanBramhall
May 20, 2010 at 7:44 PM
BedeWork is now a Jasig project. Some incubation tasks must still be completed. Deadline is release 3.7.
SusanBramhall
March 30, 2010 at 7:14 PM
COMPLETE
Sponsored Project
Details
Details
Assignee
Jonathan Markow
Jonathan MarkowReporter
Gary Schwartz
Gary SchwartzProject Preface
Bedework
Project Lead
Gary Schwartz
Gary SchwartzFix versions
Created April 15, 2009 at 2:32 PM
Updated May 20, 2010 at 7:44 PM
Resolved May 20, 2010 at 7:44 PM
Bedework is an open-source, enterprise calendar system designed to conform to current calendaring standards. Intended (but not exclusively) for higher education and built in Java, Bedework has a centralized server architecture allowing immediate update of public and personal calendaring information.
Bedework's preoccupation with standards and interoperability is in large part recognition that in many organizations, Bedework is unlikely to be the only calendaring product in an enterprise. The ability to share and exchange data with other calendaring products and environments is an important key to Bedework's future well-being as a product and a project.