The DSpace community is encouraged to add use cases in the format detailed below by creating a new sub-page from this wiki page. In order to ensure that the community's needs are reflected in the software, this input is critical.
Also, please review the existing use cases here and comment on or "like" ones as you see fit.
Analysis of these use cases has begun on the Use Case Analysis page. But, feel free to continue to add or enhance these use cases, as we are "watching" any changes in this space.
|Title (Goal)||(E.g. "DSpace should allow for bulk uploads via the UI")|
|Primary Actor||(E.g. End User or Administrator or external system)|
|Scope||(Optional – notes the perceived design scope. For example, does this use case describe the needs of the overall system or an individual component)|
|Level||(Optional – a general categorization of whether the use case is a very high level summary or almost too low level)|
|Story (A paragraph or two describing what happens)||(Describe the use case, user needs, expectations in as much detail as you can)|
For each use case, add a sub-page from this wiki page (click the "Create" button at the top of this page). It will automatically appear in the below list.
NOTE: In order for the use case to appear under a category heading, you must apply a category label
|End User: use cases relating to how end users interact with the system (e.g. deposit, download, search)|
Administrative: use cases relating to administrative functions or activities within the system (e.g. Admin UI functions)
Statistics / Metrics: use cases relating to metrics or statistics around stored content and its usage
|Integrations: use cases relating to interactions with external systems (or programs), or providing the ability for external programs to integrate with DSpace|
Structure: use cases relating to the architecture/structure of content within DSpace
This is a listing of all recently updated use case child pages, all of which should be categorized above.