Ability for Form Runner users to setup the values in selection controls

[avernet]

Use case

Nurses would like to set up the values in a "symptom" list, but the list should be only shared amongst nurses in the same department (i.e. in Orbeon Forms, part of the same group).

Implementation

• [ ] There is a reserved itemset form orbeon/itemset, which is part of the product
  • [ ] The form has a text field itemset-id and a repeat with the label/value
• [ ] A new XBL component is added:
  • [ ] It has configuration (in Control Details), to setup:
  • [ ] The appearance (select/select1, minimal/compact/full) :question: Is this actually how we want to do it?
  • [ ] Provide the itemset id (e.g. symptom) :question: Are we OK with this?
  • [ ] At runtime, the itemset is populated by:
  • [ ] Doing a search on orbeon/itemset with for data with the configured itemset id
  • [ ] See open questions for how to deal with multiple instances returned by the search
  • [ ] Then issues a GET on the data, and uses the values to populate the list
  • [ ] Has an Edit button next to do list:
  • [ ] When the button is pressed, a search is done to see if there is any data
  • [ ] If not, take the user to orbeon/itemset/new?itemset-id=symptoms
  • [ ] If there is, take the user to edit page for the form data that was found

More general configuration

• Form: app/form (e.g. daycare/child)
• Label: control name (e.g. full-name, calculated based on first-name and last-name)
• Value, either:
  • Other control name (e.g. ssn)
  • Document id
• Filter (optional) by control name and value (e.g. itemset-id and symptom)
• Order: latest first/last, alphabetical ascending/descending

Open questions

• Multiple itemsets for the same id
  • Issue: The permissions could allow multiple form data to exist. It doesn't seem that this can be fully prevented. How should we deal with this? Take only one; which one? Concatenate the items; in which order?
  • Possible solution: take all of them in a predictable order (e.g. as returned by search API), and concatenate the values.
• Multiple itemset created
  • Issue: What if two users click on the edit button at the same time when no data exists?
  • Possible solution: Create the data and save it right away to reduce the chance of this happening.
• Caching
  • Issue: If in fact two calls to the API are needed, and currently the first one is a POST, the result might not be cacheable very efficiently.
  • Possible solution: Allow search to be done through a GET, and even maybe a more fine-grained configuration to cache such itemsets (so we don't get a search call each time?).

[ebruchez]

Another open question is about caching: if in fact two calls to the API are needed, and currently the first one is a POST, the result might not be cacheable very efficiently. Needed:

• search as GET
• maybe more fine-grained configuration to cache such itemsets (so we don't get a search call each time?)

[avernet]

@ebruchez Good point; I added the issue of caching under open questions.