Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Issue Type identified as “New Feature”

  2. Summary description of the feature requested in the format of “As [role]  I request [feature]” (The roles typically used in ArchivesSpace are System Administrator, Repository Manager, Project Archivist, Archivist, Advanced Data Entry Staff, Beginning Data Entry Staff, and Repository Patron)

    Info
    iconfalse

    Examples:
    As a repository manager, I would like to link event records to name records
    As a project manager, I would like the ability to declare default values comprehensively through the ArchivesSpace application
    As a repository patron, I would like to be able to view a broad range of digital content within the ArchivesSpace application


  3. A detailed description of the desired functionality

    Feature requests that include detailed Behavior Scenarios or Use Cases can be more easily reviewed and are more likely to be prioritized for development since these use cases provide more detailed information about the requested feature and improve the likelihood of a successful outcome in development.

    Note
    iconfalse

    Feature requests that include use cases that follow the Given/When/Then /When format or that include detailed specifications and descriptions are more likely to be selected for development.  


  4. Attached files, screenshots, or specifications that amplify the feature request.

...