Package collections make it easy to curate a specific set of packages for any arbitrary purpose that you might find beneficial. They are very useful for organizing and finding packages both for your own use and for others.
Every package collection has a curator - which is either an individual or an agency who is responsible for adding and removing packages from the collection. This means that every package in the collection is there intentionally and (at least in theory) aligns with the purpose of the collection.
When you create a collection, you can decide if you want it to be a public or a private collection. Once you have created a package collection, you cannot change whether it is public or private.
Public collections can be viewed by anyone. In addition to seeing the packages in the collection, they will be able to see who the curator is. You can add private packages to public collections but they will only be visible to users who already have permission to view the package.
Private collections can only be viewed by users with whom it has been shared. You can add private packages to private collections if you have permission to do so, but anyone who has access to the private collection will also have access to any private packages in the private collection. Furthermore, private collections can either be shared indefinitely or with an expiration date. This makes it easy to (for instance) use private collections to grant limited-time access to a suite of private packages.
By clicking on the heart icon next to a package collection, you can add it to your list of favorites. Marking a package as a favorite has two advantages:
You may have up to 100 favorite package collections before older collections will automatically be removed from your list of favorites.
Please fill out the form below with your feedback or any questions you may have after working through the "Package Collections" lesson.