User Story
As a collections manager I receive external research requests from several constituencies, including those who would like to conduct research at the museum. Prior to their formal submittal of a collections access request they must provide a list of the catalog numbers they want to view. I request search terms from the requester and run several searches to compile a list of potential items of interest. The list I send them assists in their winnowing down the number of objects they need to view. I typically send them an excel spreadsheet so they can sort the items by the categories that most interest them ( such as provenience, object type, collector, date). I then ask that they return a (now reduced) excel list of the catalog numbers they wish to view. The excel list allows me to, over a series of 3 steps involving Word, copy and paste the numbers into the database and get an object package of numbers they wish to view. The amount of catalog numbers requested range from 1 to 10,000. I use this list to produce a report of locations so I can pull those objects in preparation for the visit and note them as having been accessed by that specific person. The list is also useful later to note the objects as being published or photographed by the researcher.
h6. Related User Stories:
* _<link to a related User Story>_
* _<link to a related User Story>_
* ...
h6. Derived Stories:
These related stories are created or derived from the User Story described on this page. For example, Service Stories describe bits of functionality that a service might need to provide in order for the User Story requirement to be fulfilled. These stories are used to create, plan, and track specific development tasks in JIRA. If development has begun on one of these stories, there should be a link into JIRA describing the story and the related development tasks.
{indent:1}{*}Service Layer Stories{*} |
Service Story: The ability to output sortable reports
Service Story: The ability to compile lists from several different searches
Service Story: The ability to input large strings of catalog numbers that are not consecutive or obviously related (i.e. findable through a simple search) via a copy and paste type method in order to conduct a search.
Service Story:The ability to track research access to individual objects and photography/publishing of said items.
|
{*}Application Layer Stories{*} |
Application Story: Excel or equivalent compatibility
|
UI Story: Have pick lists of fields to export to excel.
UI Story: Have ability to create a new column in excel if the field has more than one value.
|