Collections and Admin Sets
- Bill Branan
Collections and Administrative Sets
- We need this discussion for Hydramata
- Administrative sets exist in Avalon
Definitions:
- User Collection
* Display sets (for presentation)
* E.g. "favorites"
- Administrative Sets
* a.k.a. admin collections
* a.k.a. managed collections
* A group of items that are managed together
* Items that have a common behavior
"Owner" can be a user (person) or a group (organization)
Avalon has:
- Unit (holding library, department, etc)
* Name is the only attribute
* No roles associated with it
* Associated with Blacklight facet
- Administrative Set / Collection (all items must exist in a collection)
* Default access control settings
* Roles (manager, depositor, editor)
* Name
* Description
* Unit
Avalon does not have self-deposit (although they may head in that direction)
Hydramata will need to support self-deposit
Pivot points:
- Who is depositing
- What collection is it being deposited into
- What is being deposited
Provisional principles for administrative sets:
- Items have to belong to a collection
- Items can only belong to one collection
- Access control is not inherited by default
Grid of terms versus properties:
Properties
----------
Term (1) (2) (3) (4) (5) (6)
----
Admin Sets yes _ _ [a] _ _
User Collections _ _ yes [b] _ _
Display Set (curated) _ yes _ _ _ _
Properties
----------
(1) Conveys rights to items
(2) Can be used as a facet
(3) Anybody can create one
(4) Institution is responsible
(5) Canonical
(6) Hierarchical
Notes
-----
[a] Can belong to more than one
[b] Must belong to one & only one
Approaches:
- Configurator approach
- Opinionated approach
Action Item:
- Determine how admin sets relate to items
- Fill in the grid of terms properties [Hydramata POs]
- Northeastern, Northwestern (Avalon), Penn State (ScholarSphere), Cincinnati (DSpace) demos of how their implementations work
-- Ray Lubinsky
-- Manager, Software & Systems Engineering
-- University of Virginia Library Information Technology