Title (Goal)DSpace should have an easy and intuitive interface for deposit by the end user
Primary ActorEnd User
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)

Sally has an article that was recently accepted that she wants to deposit into the repository. She logs in to the repository and clicks submit an item. She has the DOI for the article so she enters that and the metadata is automatically populated. She selects an embargo period on the same screen, and drags and drops the file into the repository, selects an appropriate license, and clicks submit. She gets a review screen that allows her to correct any errors and then confirms the submission. She is told what the persistent identifier is, and can then either view the item or add another item. She receives an email with a confirmation of the deposit and the identifier.

Sally has a technical report that she wants to submit into a specific collection in the repository. She goes to that collection and clicks submit item after logging in. She sees a single submission screen. Because this is a series some information is already filled in for her, so she quickly fills out the needed information (already designated), drags and drops the file, selects an appropriate license and clicks submit. She gets a review screen that allows her to correct any errors and then confirms the submission. She is told what the persistent identifier is, and can then either view the item or add another item. She receives an email with a confirmation of the deposit and the identifier.

Sally has several datasets that she wants to submit to a collection in the repository. She goes to that collection and clicks submit item after logging in. She sees a single submission screen. She quickly fills out the needed information, drags and drops the files, selects an appropriate license and clicks submit. She gets a review screen that allows her to correct any errors. She decides she needs to reorder the files and does so in the review screen. She then clicks submit to finish the deposit. She is told what the persistent identifier is, and can then either view the item or add another item. She receives an email with a confirmation of the deposit and the identifier.

See http://osc.universityofcalifornia.edu/wp-content/uploads/2013/09/osc-quickstart-guide1.pdf for an example.