User Story
A registrar, collections manager, curator, or other duly authorized person should be able to add a "sticky note" to an object (or a group of objects) to indicate work that needs to be done to correct, complete, or expand the cataloging data for an object. Such sticky notes should only be visible to the same group(s) of users.
See also: Batch entry of object data
Rough Work Estimate:
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.
Service Layer Stories
Service Story: <Describe a bit of functionality from the perspective of the service consumer.>
Related JIRA Task: <Link to a JIRA tasks at issues.collectionspace.org>
Service Story: <Describe a bit of functionality from the perspective of the service consumer.>
Related JIRA Task: <Link to a JIRA tasks at issues.collectionspace.org>
Application Layer Stories
Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
Related JIRA Task: <Link to a JIRA tasks at issues.collectionspace.org>
Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
Related JIRA Task: <Link to a JIRA tasks at issues.collectionspace.org>
UI Layer Stories
UI Story: <Describe a bit of end-user functionality and interaction with UI components.>
Related JIRA Task: <Link to a JIRA tasks at issues.collectionspace.org>
UI Story: <Describe a bit of end-user functionality and interaction with UI components.>
Related JIRA Task: <Link to a JIRA tasks at issues.collectionspace.org>
Add Comment