It contains two new feeds called "Observation Campaigns" and "Community Tags".
The "Observation Campaigns" feed, as the name suggests, will contain events from special campaigns. At the moment the only campaign is the 'Slow Rotators' but I expect new campaigns to be added in the future and possibly I could migrate the feeds under the Lucky Star umbrella to also be part of this feed.
The "Community Tags" feed contains events that could be tagged by any one on OWC using one of the existing community tags. At the moment the only tag is 'Suspected Moons' for asteroids, as the name suggests, with suspected moons that need confirmation. If anyone wants to tag events with different community tags - these can be added.
The main difference between the two feeds is that "Observation Campaigns" will have a web-page with information about the campaign and the campaign will be more organized i.e. observations will need to be reported not only to the IOTA regional coordinators, but also to the people running the campaign, and those observations would typically be used in one or multiple papers, that will be the result of the campaign.
The Community Tags feed on the other hand include events of a particular scientific interest identified by out community, but there is no campaign associated with them. This is more of an experimental feed that I hope will help more people to get involved in identifying and tagging interesting events, for a particular reason, and also helping potential observers having to choose between a large number of potential targets, to know exactly how their observation of those events will be useful, outside of the standard astrometry and shape and size determination that is the main result of all other observations not included in a campaign feed.
After OW is updated, if you don't run OW as an administrator account, then make sure that you manually restart it after the update. In this release I still have not address the problem that when running OW as a non-admin account, after the update OW will be restarted with the admin account, and because OWs event database is stored per user, the events after the restart will be different. This is manually fixed by stopping OW and starting it again with your current user account. I hope to address this issue in a next OW update.