Skip to end of metadata
Go to start of metadata

 

The ArchivesSpace community encourages requests for new features to be added to the ArchivesSpace application.  New features can increase the application’s suitability for supporting management of archival materials, as well as optimize the experience of the application’s users. 

 

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 unresolved feature requests logged in the ArchivesSpace development project to see if the feature has already been requested and, perhaps, prioritized for development. 

 

Once you have determined the feature does not already exist in the application or has not been already requested, then you can request a new feature, in one of three different ways:

1)      Directly to the Support JIRA (select Create issue)

2)      Indirectly via the “Report an Issue” link on the ArchivesSpace website

3)      Indirectly via the “Send Feedback or Report a Problem” option appearing at the bottom of pages in the ArchivesSpace application

 

All three pathways will load a form for reporting a bug: 

 

 

An actionable feature request requires the following:

1)      Project identified as “ArchivesSpace Support (AS)”

2)      Issue Type identified as “New Feature”

3)      Summary description of the feature requested in the format of “As [role]  I request [feature]”, e.g.,

    • 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
      [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]

4)      Email address of the person requesting the new feature (for the purpose of following up on the request if necessary)

 

The following optional information may be recorded in the request:

1)      A fuller description of the feature requested, describing any parts of it that might not be clear in the summary description

2)      Attached files, such as screen shots, specifications, or longer descriptions than amplify the summary description.  

  • No labels