Practices and Senses

They were an original data artifact and still fit well into the schema of an Experience, but focus shifted to other areas over the life of the project. The UI/UX for adding these no longer fits what the rest of the site does. The fact that they are on Experience Review is also a bit odd, they would be better placed on the Experience Form.

There is also no "item view" where one can see the details of a Sense or Practice that was already added.

Their existence as individual entities associated with an Experience is in question. Perhaps this should exist as a multi select area offered for an experience to offer the statement "Experience has sense Sense" or "Experience has practice Practice". We could offer a free field for experience or practice so it can be defined, with UI like

{Multi Select} {text input} so user could create a text value like "{Kneeling} {on ground}" or "{I see} {100 lit candles}". We could define an ontology for "hasSenses" and "hasPractices" where the value is expected to be an Array of Strings. "relatedSenses" and "relatedPractices" will still be in the LRDA schema waiting for more development on individual Practice and Sense types.

The issue names no files, tests, or entry points. Start by mapping the existing Experience Review and Experience Form UI and the Sense/Practice data model, then resolve whether these remain entities or become multi-select and free-text fields; done means an agreed design and implementation scope for creation, viewing, and schema behavior.

Written by the indexing model from the issue text.