-
Add documention detailing project-specific terms and their meaning
-
We've converged on terms to use to refer to various types of incidents and events and on terminology for GRIP in general. We need to start updating the website consistently. This requires chats with t…
-
- [ ] Change "**Manifests**" to "**Resources**" in all occurences (including main menu, and Manifest creation).
The term Manifest is difficult for users to understand. We hesitated with Document, but…
-
We have tested editing Attribute Terminologies.
In CR8009, I changed code 98 - Other (not listed) to 99 - Others (not listed)
When I checked the Orchestrator, the codes haven't changed:
![im…
-
Currently, there are several terms that refer to the same concept in the repo:
- inner thoughts
- inner monologue
- internal monologue
To avoid confusion, these should be standardized to a single …
-
I've never been quite clear on the difference but I want to get it right in this episode (and throughout).
-
Clarify and decide on terminology eg: occupance, density, count, volume..
-
Currently: `xt.txs` is the table that makes the 'transaction log' accessible to users, but this name is likely too cryptic and means that `_id` requires explanation. It can also be confusing to type,…
-
I think it is necessary to provide definitions of terms used within V3 (and V1.3) and correlate to related and competing definitions. This is probably best added to the glossary when time to reorganiz…
-
Proposal for process in meeting on Oct 9 was as follows:
- Separate use cases and feature requests.
- Feature requests can be in the form of user stories, and link a feature to a purpose.
- T…