This is a work in progress. It is intended to summarize the work of the Display Set Working Group to date.
Overview
The existing approaches of collecting resources, Admin Sets and User Collections, are not adequate for the broad set of use cases expressed in the community. The Display Sets Working Group has been exploring an approach that will expand the functionality available to applications for grouping resources.
Unable to render {include} The included page could not be found.
A Vision of One Grouping to Rule them all
Things that make grouping difficult.
- As seen in the requirements chart above, there are characteristics of groupings that may not be compatible.
- This is further complicated by the fact that some apps may want more than one set of characteristics for their groupings, e.g. sometimes those of an Admin Set and sometimes those of a Display Set.
It is incredibly challenging to have 3 distinct type of groups play nicely together. What would it be like to have one and only one type of grouping that is configurable?
So you love admin sets and don't care about anything else...
AdminSet Configuration:
| Sitewide Setting | Can be overridden for specific set? | Comments | |
|---|---|---|---|
| multiple membership within type | OFF | ||
| nestable | OFF | ||
| browsable | OFF | ||
| branded landing page | OFF | ||
| ability controls | ON | user/group that fills each ability role is defined per set | |
| workflow controls | ON | workflow is identified per set | |
| APO controls | ON | visibility/discoverability is defined per set |
You want to control everything in admin sets and use display sets as exhibits
Create two collection types:
- AdminSet type collection with configuration same as above.
- DisplaySet type collection with configuration below.
DisplaySet Configuration:
| Can be overridden for specific set? | |||
|---|---|---|---|
| multiple membership within type | ON | YES | It would be uncommon for an exhibit to claim ownership of its works and not allow them to be in other exhibits. This would also prevent you from adding an existing work that is already part of another exhibit. |
| nestable | ON | YES | |
| browsable | ON | ||
| branded landing page | ON | ||
| ability controls | OFF | ||
| workflow controls | OFF | the work has to already exist and by definition be part of an admin set | |
| APO controls | OFF | the work has to already exist and by definition be part of an admin set |
You have a self-deposit system and want users to be able to organize their deposited materials
UserCollection Configuration:
| Can be overridden for specific set? | |||
|---|---|---|---|
| multiple membership within type | OFF | ON | optional (current behavior is ON) | |
| nestable | OFF | ON | optional (current behavior is OFF) | |
| browsable | OFF | ||
| branded landing page | OFF | ||
| ability controls | ON | SET FOR ALL: manager=CREATOR; depositor=ALL USERS; viewers=CREATOR | |
| workflow controls | OFF | the work has to already exist and by definition be part of an admin set | |
| APO controls | OFF | the work has to already exist and by definition be part of an admin set |
