New in Bedework 3.10

Bedework 3.10 contains many enhancements.  Among them:

• A largely-revamped public client, which features:
  • Responsive design - the public client will display reasonably on almost any screen size.
  • More powerful and flexible left-hand navigation - in just a few clicks, site visitors can ask for the "Arts events and Films taking place on West Campus"
  • Event filtering by string. – ex., “Arts events and Films on West Campus that include 'Sherlock' ".
  • An endless stream of events - All events that match the criteria are presented, starting with today's events (or any other date specified), and advancing into the future.   An initial group of events are displayed on the page, and when scrolled towards the bottom of the page, the next group is presented.
  • Improved performance with fewer page reloads - most operations, such as adding/removing a filter, are done "in-page" (using Ajax calls).  
    
    
• Enhancements to indexing  
  • Bedework 3.10 has a new search engine – ElasticSearch.  In the Bedework context, ElasticSearch, provides better remote management of indexes,  better scalability options, and much simpler configuration than Solr. ElasticSearch is used by, among others,  Wikimedia, Foursquare Etsy, and GitHub.
  • Improved performance and scalability by directing most queries to an ElasticSearch index rather than directly to the database engine
    
    
• More real-time site configuration
  • All configuration settings are now set through the JMX console, eliminating the need for rebuilds to reconfigure
    
    
• An improved Quickstart 
  • A smaller (~40%) Quickstart - obsolete code and unused JBoss components have been removed  

• Miscellaneous bug fixes and enhancements
  
  

Bedework 3.10.2 is a major enhancement to Bedework 3.10.  Updates include:

1. Performance Improvements

• numerous updates to correct for bottlenecks and other performance issues allowing for significant load and large-scale deployments
  
  

2. External Subscriptions

• significant improvements to external subscription handling

• better handling of contacts and categories for public calendaring
  
  

3. Workflow (public calendaring)

• new author and approver roles allowing for moderated publishing of events by administrative groups
  
  

4. Cross-Suite Suggestions (public calendaring)

• new suggestion mechanism allowing different calendar suites to suggest and accept (or reject) events across teams
  
  

5. Event Registration (public calendaring)

• significant improvements to event registration features

• addition of custom fields to any registration form and a form builder for constructing and managing custom forms (extra text inputs, checkboxes, radio buttons, and select boxes)

• email notifications (see Notifications)
  
  

6. Notifications (public calendaring)

• In public calendaring, administrative users now receive notifications of actionable items (workflow approval requests, suggestions from other groups, and responses to each)

• In event registration, the notification engine is used to communicate with registrants concerning registration, waitlisting, and event cancellation
  
  

7. Self Registration

• Allowing users to register with the calendaring system so that they may register for public events
  
  

8. Web Client Improvements

• Improvements to the public administration client

1. locations can be broken into locations and sub-locations (e.g. buildings and rooms)

2. Rooms can be added on-the-fly during event creation

3. improved location and contact look-up during event creation

4. Numerous other stylistic and usability enhancements in the administrative client

• Improvements to the public web client

1. improvements to ADA compliance
   
   

9. Bug fixes