Use Case: Self Deposit
- Repository Type: Institutional Repository
- Content Type: articles & data
- Key concepts:
- default admin set sufficient
- user collections only
- no workflow
- no visibility restrictions
- 1 worktype
- users deposit
- users can organize in private collections
Use Case: ETDs
- Repository Type: Institutional Repository
- Content Type: student papers
- Key concepts:
- mediated deposit workflow
- visibility restrictions: cannot set to embargo or lease
- 2 worktypes - thesis and dissertation
- 2 admin sets - for different visibility restrictions
- user deposit
- approval limited to certain staff
User Case: Exhibit
- Repository Type: Digital Repository
- Content Type: images
- Key concepts:
- two purposes in one repository
- different group curating each exhibit
- requires lease for certain materials
- general curation of content
- creation of public exhibits from curated content
Use Case: Multipurpose - combined content from previous 3 use cases
- Repository Type: mix
- Content Type: mix
- Key concepts:
- how do we combine the key concepts from all the use cases?
- Blocks
- Collection Types -
- 1 type - User Collections
- Admin Sets
- 1 - default
- Collections
- created by any user
- Work Types
- 1
- Works
- created by any user
- Filesets
- nothing new
- Collection Types -
- Key Questions
- What types of users will work with your repository?
- What types of content will the repository hold?
- Collection Types
- Admin Sets
- workflow strategy
- visibility strategy
- Collections
- Works Types
- Works
- Filesets
- What types of users will work with your repository?
- do users play different roles in the repository?
- are there limits on who can create collections or certain kinds of collections?
- are there limits on who can create works?
- are there limits on which collections a user can add a work?
- What types of content will the repository hold?
- What types of collections are needed beyond the predefined User Collections and Admin Sets?
- limits on who can create
- limits on discoverability (NOTE: can't control with an admin set)
- limits on other configurable settings (e.g. branding, nesting, sharing, membership restrictions, visibility restrictions, etc.)
- What admin set strategy is needed?
- multiple admin sets vs. just using the default
- do you need collection based permissions?
- one to one relationship between worktype and admin set? (customization)
- What workflow strategy is needed?
- always use same workflow?
- need multiple workflows?
- need custom workflow?
- What visibility strategy is needed?
- same visibility for all works?
- visibility policy based on legal access to works?
- visibility depending on type of work?
- What worktype strategy is needed?
- How many distinct worktypes do you need and what are they?
- Will everyone need to use them or should some people be able to use certain worktypes? (customization)
- Will worktypes be defined by user needs or metadata needs or both?
- Or deposit only to certain admin sets or collections? (customization)
- What relationship strategy is needed?
- Is nesting need?
- When will you use collections, parent/child, work/fileset relationships?
- Do you have metadata at the file level where child/nested works are needed or will you use filesets?
- How will performance be considered? (e.g. nested works vs filesets vs collections have different performance concerns)
- Do you need ordered relationships?
- What is your discoverability strategy?
- Do names of worktypes matter?
- In schema.org/google scholar?
- In the interface?
- What about resource types?
- Do names of worktypes matter?