OKMInterfaceChanges

From MWCSWiki

• Thoughts about OKM interface

1. Default role!!
2. Probably be more aggressive in distinguishing "fields" from "relationships" in the user's mind. (Two different buttons, rather than just one "+Data" button.)
3. Actually implement relationship data (duh)
4. Make it more obvious that a relationship can involve further information (JWB-assassinated-AL in 1865, e.g.), probably by:
   1. displaying an icon near the relationship that is obvious to click on (rather than having to click on the predicate text)
   2. showing the relationship information inline on the object's page (i.e., on the JWB page, directly underneath the "JWB assassinated AL" relationship, indented and in a smaller font, show "in 1865," etc.)
5. Adopt different terminology for "fields" and "relationships." Ideas include:
   • For fields: properties, traits
   • For relationships: links, connections
   • We'll be using feedback from experiment 1 to determine the best terminology. Stay tuned.
6. We should not make the user actually populate the role of an object in a new relationship unless we can't reasonably guess it. To wit:
   • If the object has exactly one role that is known to match the predicate, we just populate it in the role drop-down, period. (The user can change it explicitly to make a schema change.)
   • If the object has no roles that are known to match the predicate, we populate nothing by default, but make the user type the role. Roles that are known to match the predicate are aggressively matched; others non-aggressively matched.
   • If the object has more than one role that is known to match the predicate, we populate nothing by default, but make the user type the role. Roles that are known to match the predicate and which the object already has are aggressively matched; others non-aggressively matched.
7. Add the ability to create a connection/link/relationship where the object in question is on the RHS instead of just the LHS.

Media:Example.ogg