Donate | Contact | Search

*specific* use-cases (& tasks)

• Summary of operations (w/ more info below): link, copy, watch, review, synchronize, search
• making a site available on the network, safely only showing those things that are public unless one is logged in?
• sending links: to be able to easily refer another person to a part of any model they can both see. what flow, completely, for them?
• copying info of others, including the class & key related info as needed
• when someone copies/links to another instance, optionally tell the source instance owner "copied" or "linked"
• it should be able to search across local & remote, n in all ways if possible, treat them as if they were one, a single repo.
• and searching/finding things across what is available elsewhere (like, even if not yet integrated into own, can sch in a global inst, one can then link to?)
• subscribe/watch for updates/watching/monitor feature
• synchronizing info (updating from a copy or partial copy, including one's own eg mobile to cloud to pc, mbe other)
• integrating (if different/additional to synchronizing)
• allows discussing the links/poss synch/copies be4 *doing*. Or is the discussion just another datum to be shared (more likely)?
• marking with relative trust and sharing that info (the marking) (other notes on this are elsewhere) (or is just another datum to be shared?)
• controlling access
• where one tracks medical (or other) info, to share measurements w/ dr, vs. a public site where all is shared? How does each consumer manage each part?