1. Describe the high-level use case(s) your Hyrax system needs to support
2. Describe the type(s) of users your Hyrax system will support
- 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?
- are the users occasional/one time users or power users?
3. Describe the type(s) of content your Hyrax system will support
- is the content homogeneous or varied?
- are the access control needs varied or homogeneous?
- 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?
- will deposited items go to certain admin sets or collections based on worktype? (customization)
4. Describe any workflow needs
- always use same workflow?
- need multiple workflows?
- need custom workflow?
5. Describe any visibility or embargo policy needs
- same visibility for all works?
- visibility policy based on legal access to works?
- visibility depending on type of work?
6. Describe any needs around discoverability
- are there limits on what can be discovered?
- should all works be discoverable?
- are there limits on who can make works discoverable?
- how do you want to be able to discover works or collections?
- what facets do you want in the hyrax app? (ex. defaults: title, author, worktypes, resource type)
- how can you use facets to make groups of works discoverable if not using collections?
- considerations:
- default facets may not be sufficient
- admin sets are not discoverable
- some collection types may be configured to not be discoverable
- considerations:
- are there discovery requirements for outside discovery
- do you need to optimize for google scholars (e.g. required metatags which may not come out of the box for hyrax)
- do you want schema.org metadata?
- considerations:
- work type becomes schema.org type
- considerations:
7. Describe any needs around relationships
- Is nesting need?
- for collections?
- for works?
- 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?
8. How will works be grouped together?
- do all users have the ability to group works?
- are there visibility policies effecting groups of works?
- how do users select admin set to apply the policy
- are there different workflows for different sets of works?
- how do you determine which workflow is right for a work?
- are groupings driven by a need for hierarchical organization?
- do different users have access to different sets of grouping features (e.g. nesting, branding, sharing, discoverability)?