User can define specific relationships between records
User Story
A user can create an explicitly defined relationship between two records or vocabulary terms. A sample set of relationships is below.
Relationship types (relationship listed first, reciprocal relationship listed in parenthesis if necessary):
Object to Object, Media to Media
has broader term (has narrower term)
has narrower term (has broader term)
references (is referenced by)
is associated with
Related records with relationship type "broader" should be placed above the primary record in a hierarchical view. Related records with relationship type "narrower" should be placed below the primary record in a hierarchical view.
Object to Procedure
falls within (contains)
is associated with
Object to Media, Procedure to Media, Authority to Media
documents (is documented by)
depicts (is depicted by)
is associated with
Procedure to Procedure
documents (is documented by)
references (is referenced by)
is associated with
Vocabulary Term to Vocabulary Term
has broader term (has narrower term)
has narrower term (has broader term)
references (is referenced by)
is associated with
use (use for)
Related records with relationship type "broader" should be placed above the primary record in a hierarchical view. Related records with relationship type "narrower" should be placed below the primary record in a hierarchical view.
Related User Stories:
- Record may not have more than one parent
- <link to a related User Story>
- …
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.