## Description Over-restrictive scope correlation caused the reduce processor to only include filters which matched the data type of the scope. Ironically, this allowed a superset of information to match, by evading the _all-match_ expectations of filter scopes. Also replaces the data category consts inside /details with the path category types, since those are acting as better canonical owners of data type identification throughout the app. ## Type of change - [x] 🐛 Bugfix ## Issue(s) * #890 ## Test Plan - [x] 💪 Manual - [x] ⚡ Unit test
Corso
Corso is the first open-source tool that aims to assist IT admins with the critical task of protecting their Microsoft 365 data. It provides a reliable, secure, and efficient data protection engine. Admins decide where to store the backup data and have the flexibility to perform backups of their desired service through an intuitive interface. As Corso evolves, it can become a great building block for more complex data protection workflows.
Corso supports M365 Exchange, OneDrive, SharePoint, and Teams. Coverage for more services, possibly beyond M365, will expand based on the interest and needs of the community.
Getting Started
TODO - Link to the appropriate page in the published docs.
Building Corso
# Build a binary. Will be placed in bin/
./build/build.sh
# Build a container image
./build/build-container.sh
Containers
Corso images are hosted on ghrc.io.
Rolling release
docker pull ghcr.io/alcionai/corso:{SHA} --platform linux/arm64
Contribution Guidelines
TODO
Code of Conduct
It's important that our community is inclusive and respectful of everyone. We ask that all Corso users and contributors take a few minutes to review our Code of Conduct
License
TODO `