Concepts

Concepts are user-facing units of functionality, following Daniel Jackson's concept design. Each entry records a concept's purpose, operational principle, state, actions and misfits.

Patterns act on concepts. The concept is what the system does and what the acts mean, and the pattern is what the maker should do about it in a situation.

  • Assigning roles
    Let what a member may do in a shared space be given and understood by a named role, instead of action by action for each member.
  • Assisting
    Offer a member a proposal for the next step of their own work, which they are free to take or leave.
  • Authorising
    Let another party act for a member on things the member controls, within limits the member sets.
  • Automating
    Have a piece of work carried out each time its occasion comes, without the member asking for it.
  • Bookmarking
    Make it easy for a member to return to an item later.
  • Commenting
    Let people attach remarks to a passage of shared material and settle them.
  • Conversation for action
    Bring a request made of another party to a close that both sides have agreed.
  • Deferring
    Put something off until a named time and have it come back then without anyone having to remember it.
  • Document keeping
    Keep a body of written or uploaded material in a place where members can find it and revise it.
  • Filtering
    Show only the items in a collection that meet conditions the member states.
  • Following
    Let a member receive updates from the sources they choose.
  • Grouping members
    Let access be given to a named group of members at once, so that joining or leaving the group changes what each of them can reach.
  • Joining
    Make a person a member of a space, with a role and a level of access.
  • Labelling
    Attach labels to items so the items can be found again by label.
  • Notifying
    Tell an actor about something that happened while they were not looking.
  • Quoting
    Lift a passage out of a document so it can be kept, referred to and found on its own.
  • Remembering
    Carry what the system has learned about a member and their work from one session into later ones, so they do not have to say it again.
  • Running a project
    Hold a bounded piece of shared work from its start to its outcome, so members and their tasks have a place to belong to.
  • Session keeping
    Hold the turns, attached context and working state of one piece of work together and apart from other work, so it can be continued and returned to.
  • Signing in
    Mark that a member is present, so what they do is theirs and what happens meanwhile can be told to them later.
  • Staging
    Move an item through an ordered set of states so everyone can see where it stands.
  • Task tracking
    Record a piece of work to be done so it can be found, picked up and finished.
  • Trashing
    Let a member take back a deletion.
  • Versioning
    Keep past states of an item so a member can find one and bring it back.