Updates to collection and umbrella projects
Today we are releasing a couple updates to the newest types of projects - collection and umbrella projects. We first launched these new project types in April, shortly before the City Nature Challenge, to address a few common feature requests for traditional projects.
The most significant difference of collection and umbrella projects compared to traditional projects is the new types do not require observations to be added to a project, rather they automatically feature observations matching the criteria of the project. One downside of the automatic nature of these projects is there is nothing stored in our database saying which projects an observation belongs to. So, since launch, observation details pages have not shown which collection or umbrella projects include an observation. This has been one of the most requested features since the launch of these projects, and starting today you will now be able to see collection and umbrella projects that include an observation from the observation detail page.

Another difference in collection and umbrella projects is they were only able to be “followed” and not “joined” like traditional projects. There were a few reasons for this - mainly that membership to traditional projects only provides a few benefits, most of which don’t apply to collections and umbrellas. For example there is no observation submission for new projects, so obviously the membership-based submission rule of traditional projects does not apply. New projects also do not allow access to private and obscured coordinates, which traditional projects allow via settings on a users’ membership settings.
The second change we are making is a move from the “following” model to a “membership” model just like traditional projects. Membership to new projects still does not allow for the same features as traditional projects (no rules for observation submission, and no access to private or obscured coordinates). But membership sets us up to enable new features in the future, and makes new projects more consistent with traditional projects. One feature consistent across all projects is members can choose to receive updates from the project or not. Essentially a user can now be a “member” of a new project without “following” the project.
These two changes (observation pages show new projects, and projects have members not just followers) are complementary. Since anyone can create a collection project to include any observations they want, it's possible a user’s observations are included in a project they aren’t involved with. So we are limiting the new projects shown on the observation details page to only the projects the observer has joined. This makes the project shown more relevant to the observer, and prevents the observation details page from being “spammed” by undesirable or mis-configured projects.
These changes came out of user feedback on the new project types released in April. We are continuing to improve projects based on your feedback, and will notify you as changes are released. Thanks for your patience and please let us know if you encounter any bugs (of the software kind).
















