The active wiki for the Samvera Community can be found here: https://samvera.atlassian.net/
This wiki space is archived. The active wiki for the Samvera Community can be found here: https://samvera.atlassian.net/
Also known as Display Sets.
|Management of Collections|
|Collection Config||Ability to configure global characteristics of Collections||1|
Configuration controls global characteristics about Collections including:
QUESTION: Should the ability controls really be optional? What is the use case for not allowing ability controls? If they are optional, then the default value for managers, depositors, and visitors would be the user who created the Collection.
QUESTION: Should there be types of Collections (e.g. User Collection, Curated Exhibit, etc.) that have different configurations? How would that look in the UI?
NOTE: There are open design issues on the implementation of having workflows for Collections. There is still a need for understanding how that would look in the UI, so workflows may appear in this document in a number of places.
|Manage Collections||List all existing Collections. Create and edit existing Collections and their metadata.||1|
NOTE: Management of Collections should have a UI that is consistent with management of Admin Sets. (See Administration → Administrative Sets in Sufia app)
|Works within a Collection|
|Add Existing Works||Select any work that is discoverable and accessible by (at least some) viewers of the repository can be selected to be part of a Collection||1|
How to convey the concept of one Collection owning a work and all other Collections with the same work as member have an alias relationship (or mapped relationship) with the work? Do we want to use the term ownership, or should it be something like 'primary' Collection. I will use 'own' in this document, but recognize that terminology may change.
For adding an existing work...
|Direct Work Creation||A single work can be created directly in a Collection.||2|
|Batch Upload||Multiple works can be created directly in a Collection via batch upload process.||3||Same notes as for Work Creation|
|Remove Work||Remove a work from a Collection.||1|
This action requires the user to be an admin or depositor for the Collection.
Question: If the last work is removed, should the user be prompted to delete the Collection if they are a manager? Should managers be notified of empty Collections?
|Delete Work||Delete a work from the repository.||1|
This action requires the user to have edit access to the work.
NOTE: Could be a prompt when selecting Remove Work that asks whether this is a remove from this Collection or a permanent delete?
|Work - Link to All Locations||The show page for a work links to any Collections in which it is a member||2|
NOTE: On the show page for a work, it lists all Collections and other collectors (i.e. Admin Sets, User Collections) where the work also lives AND that the user has access to view.
QUESTION: Is this functionality already in place and we just need to make sure the extended collections are showing up in it without change to the UI/UX?
|Nestable||Select any Collection that is discoverable and accessible by (at least some) viewers of the repository to be part of a Collection||1|
|Direct Collection Creation||A single Collection can be created directly in a Collection.||4|
Mockup NOTE: Probably same as for New/Edit Work form so likely low hanging fruit and possibly done when New/Edit Work form is changed if they share partials.
|Browsing and Discoverability|
|Landing Page||Show branded landing page for a Collection||1||Milestone 1: Make use of title, description, header image, and logo to make a public landing page.|
Milestone 2: Show all collections in which this collection is a member.
|Hierarchical Browse||Browse from top most Collections to member Collections and Works|
This is how the public user will primarily interact with Collections. It would be nice to have several ideas of what the entry point into the Collections would look like. We need a good default browse implementation that sites can override depending on the focus of their app.
Mockup NOTE: Hierarchical browse needs more information on how to identify the top most set of collections.
|Discovery||Collections and member works can be discovered through regular app wide search.||1|
How would the results be displayed?
What facets would be needed?
|Search within Collection||Search results are limited to works in a Collection and any of its member Collections|
Milestone 1: Limit results to the Collection
Milestone 2: Limit results to the Collection and all member Collections