Versions Compared

Old Version 17

changes.mady.by.user Jessica Crouch

Saved on

compared with

New Version 18

changes.mady.by.user Christine Di Bella

Saved on

Key

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

...

Note
iconfalse

Before requesting a new feature,

  • Upgrade to the latest release of the application and make sure the feature you want to request is not already present in the application, and 
  • Review feature requests logged in the ArchivesSpace development project to see if the feature has already been requested and, perhaps, prioritized for development.

...

  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/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.

...

Note
iconfalse

Ticket submitters and all other individuals interested in the development of the feature request are encouraged to remain vigilant of the ticket and respond to all requests for information.  Tickets that have a status of "awaiting more information" are unable to be prioritized or implemented until questions are resolved.