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].
Note: Should this specify all the forms we put this into, or should it have a story per form, or something else? Current thinking is that this does not require association, but is like a scalar value used in a schema. Nevertheless, to capture the work we need to specify this per form, until we have all the underlying stories complete and can gloss over the details.
User Story
User can select from among terms in a flat vocabulary that has been associated to a given field in a form.
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.
Related User Stories:
- Admin can configure a flat vocabulary for use with a field - XML
- User can add Term to Flat Vocabulary (Controlled List)
Derived Stories:
Service Layer Stories
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.
Application Layer Stories
Application Story: TBD
UI Layer Stories
UI Story:TBD
Add Comment