Info |
---|
DRAFT outline of user-facing documentation, where users may be:
Some caveats:
|
DSpace administrator role
- Community and collection management
- Create and edit a community (Create a top level community, Create a subcommunity, Edit the metadata associated with a Community; Upload a new image to a Community page);
- Create, edit and delete a collection; Edit the metadata associated with a Collection
- Manage permissions for a community or collection
- Content management
- Edit an item
- Metadata
- Bitstreams
- Manage access to an item
- Version an item
- Move an item
- Map an item from one collection to another
- Withdraw and reinstate an item
- Delete an item
- Embargo an item
- Lease an item
- Export collection
- Export metadata as csv, reimport
- Batch import (think this is documented in technical?) (Upload a batch through the web interface, Upload a metadata batch (CSV only, no file zip) through the web interface)
- Edit an item
- User management
- Add or update an eperson
- Create or update a group
- Impersonate a user
- Registry management
- Metadata
- Format
- Other admin functions
- Administrative search
- Perform curation tasks
- Manage active workflows
- Access / manage processes
DSpace submitter role
Use "MyDSpace" to
- Submit a new item (does this need to be broken down at all?)
- View past submissions
- Perform workflow tasks
DSpace end user (reader) role
- Create and manage account, log in
- Contact service administrators
- Subscribe to content updates (RSS, email)
- Search DSpace
- Browse DSpace
- View an item
- Special cases readers may encounter
- Restricted item (embargo or lease)
- Restricted item (permissions)
- Versioned item
- View usage statistics
- Link to DSpace content (hint: use the handle)