-
Notifications
You must be signed in to change notification settings - Fork 2
User Stories
User stories are a way to capture a system's functional requirements.
From Wikipedia
a user story is one or more sentences in the everyday ... language of the end user ... that captures what a user does or needs to do...
User stories are a quick way of handling customer requirements without having to create formalized requirement documents and without performing administrative tasks related to maintaining them.
For Ichabod, we write user stories to quickly and efficiently capture the 'who', 'what', 'where' and 'why' of a functional requirement.
We use two templates for writing our user stories. They are semantically the same, but some authors may prefer one or the other
- "As a who where, I what because why."
- "As a role where, I want goal/desire so that benefit."
- NYU Community
As a cataloger, I want to be able to input metadata for an asset, and then later, I want to be able to modify or delete that metadata, so that I can ensure the accuracy of the information I’m including.
As a cataloger, I want to have permission to edit only the metadata for which I am authorized, i.e., a particular collection’s metadata, so that I can protect my own metadata and others from inadvertent modification.
As a cataloger, I want to be able to add fields to a record whose canonical source resides elsewhere, so that I can provide additional information to the systems that require it.
As a DLTS developer, I want to obtain data in MODS format, so that I can publish the digital content represented by the metadata in question.
As a DLTS developer, I want to obtain the MODS data on the fly so that I always retrieve the latest information.
As a cataloger, I want to be able to create a new collection and begin adding metadata for objects in that collection.
As a DLTS developer, I want to be able to provide handles for objects whose metadata resides in this system, so that the discovery tool can link back to those objects. I want to be able to provide the handles at any point in the workflow, so that the cataloger is not dependent on me and can make his or her own schedule.
As a DLTS content creator (digitizer), I want to be able to extract information in the form of a “shoot sheet,” similar to what I can obtain from the Archivist’s Toolkit, so that I can digitize or process the content being described by the metadata and name it accordingly.
As a DLTS developer, I want to obtain unique identifiers for each metadata record, so that I can ensure that the records can be associated with the digital objects they represent.
As a DLTS developer, I want to know the digital object type of each object, so that I know which workflow to apply.