...
- NOT nestable
- NOT discoverable
- CAN be shared
- can NOT have multiple membership
- DO require membership - enforces that a work must belong to at least one admin set; when combined with multi-membership off, this becomes one and only one
- CAN define workflow - allows the admin set to specify the workflow to use for works created in the admin set
- CAN define visibility - allows the admin set to specify default visibility settings for works created in the admin set
It is the last 3 settings that are currently unique to admin sets. They are consistent with the pre-extensions behaviors of admin sets. Those settings are disabled for regular collections types. This is were additional design would be needed to resolve how workflows and visibility settings would interact if they are defined on collections of various types and a work can belong to multiple of those collections.
There is a rake task that you run to create the User Collection and Admin set collection types. All other types are defined through the UI.
I have defined one other collection type call Exhibit with settings...
- NOT nestable
- IS discoverable
- CAN be shared
- can have multiple membership
So now let's take a look at the collections...
For the purpose of the demo, I have pre-created a number of collections by various users. I am currently logged in as an admin. When I click Dashboard → Collections, I see a list of collections I created. Because I am an admin, I also have an All Collections tab which will let me see all collections defined by any user in the repository. This index has had a UI refactor to where the list provides additional information like the collection type, number of items, and shows last modified instead of create date to give a sense of whether the collection is stagnant or actively changing. Not shown yet, but coming soon, this will also include filters that allow you to limit the set of collections by collection type and visibility. The refactor also added the ability to bulk delete collections.
In general, the UI/UX enhancements take an educational approach to the UI. For example, if you click Delete collections button without selecting anything first, you will get a dialog telling you to select something first.
Let's create a new collection. The process is the same for an admin user and a regular user.
When you are first creating a new collection, the only visible tab is the Description tab. From there you can set the required metadata, which by default is the title. To encourage the setting of the description, it was made a primary term, but not a required term. So it shows up without having to expand with the additional fields button, but you can save without setting it. The full range of attributes are available under Additional fields, but are hidden by default. Once you click Save, additional tabs appear based on the collection type settings. I chose a type that has all settings turned on so we can explore all the tabs.
Branding allows the user to specify a header image that is displayed at the top of the collection landing page. Additionally multiple logos can be uploaded. The landing page work is still in progress. But you can get a sense of where we are going from the mockup.