| Wiki Markup |
|---|
*Story:* User can choose terms from an existing flat vocabulary, for use in a form. E.g., the Acquisition Method section in [the Acquisition wireframe|Wireframes+-+Acquisition]. _Note: Should this specify all the forms we put this into, or should it have a story per form, or something |
...
See also: ...
- Services Stories (not already supported)
- Application Layer Stories (example guesses)
...
else?_
h6. User Story
{indent}
User can select from among terms in a flat vocabulary that has been associated to a given field in a form.
{indent}
*See also*:
Note: This assumes that the field has been configured for use with the vocabulary. This assumes that there are terms in the vocabulary. If the related story about adding terms to a flat vocabulary is complete, then this sotry should be able to use a new term (even if tentative) in the form.
h6. Related User Stories:
* [Configure a flat vocabulary for use with a field]
* [Add Term to Flat Vocabulary]
h6. Derived Stories:
{indent:1}
*Service Layer Stories*
{indent}
{indent:2}
Service Story: Service consumer can reference a vocabulary term from a CollectionObject, Intake or similar record. This should not involve the use of a relation or association service, but should function like a scalar value that references a vocabulary term.
Service Story: Service consumer can get a vocabulary reference from a given term reference.
Service Story: Service consumer can validate a vocabulary term reference.
{indent}
{indent}
{indent:1}
*Application Layer Stories*
{indent}
{indent:2}
Application Story: TBD
{indent}
{indent}
{indent:1}
*UI Layer Stories*
{indent}
{indent:2}
UI Story:TBD
{indent} |