USE CASE: Enable input forms

[kcoyle]

Creator: Karen Coyle

Problem statement

I'm creating a profile for data that will be created in an online form as staff process materials into an archive. It would be ideal if the profile could be used directly to populate the various entries in the form, and to be used to validate the data as it is being input (or when the form is saved). This would mean that there needs to be sufficient information in the profile for the following functions:

1. Valid data type (string, numeric, etc.)
2. Cardinality of the data element (mandatory, optional, repeatable, not repeatable, number of repetitions)
3. If a controlled vocabulary, a pick list to choose from
4. Optionally, if the controlled vocabulary is very large, a link to the vocabulary or a list of valid URI patterns
5. Length limits for strings
6. ?? Probably there is more

Stakeholders

The main stakeholders are the system developers, whose work will be made much easier if they can directly connect the profile to the actual system that uses it. Archive management benefits through time savings and presumed accuracy of the data that is created. Data creators benefit because the online forms will guide them in creating the correct input.

Links

Requirements

1. Profile must be machine-readable in a format that can be ingested by a web-page script
2. Profile must have a way to express validity constraints for data elements and their values

Comments

''Optional section for editorial comments, suggestion and their interactive resolution''