Skip to main content

Home/ Chandler Project/ Group items tagged structure

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Graham Perrin

Chandler Wiki : Browser Design - 0 views

chandlerproject.org/...BrowserDesign

004250 hierarchy

shared by Graham Perrin on 25 Jan 09 - Cached
  • computer file systems
  • book stores and supermarket aisles
  • hierarchical org charts
  • ...57 more annotations...
  • Trees abound in
  • trees prevail
  • they clearly limit us
  • Semi-lattices are non-polar, where do you start, where do you end?
  • Reality and the human brain's ability to grok it are far more complex than a tree
  • dumbing down isn't always a bad thing
  • you don't really understand something unless you can explain it in 5 words
  • Let's improve on the software
  • too strict, too dry, too simplistic
  • browse the same data via many different trees
  • visual information mapping hasn't already taken over the world
  • that break the tree
  • brains ARE really really good at seeing relationships
  • linear doublethink
    • Graham Perrin
      Graham Perrin on 25 Jan 09
       
      Graham: review!
  • stop-motion semi-lattice building
    • Graham Perrin
      Graham Perrin on 25 Jan 09
       
      Graham: review!
  • extremely adept at looking at the same data and reorganizing it into different trees in rapid succession
  • in one file cabinet, on one bookshelf, in one way
  • forcing us to look at our data
  • semi-lattii
  • Challenge: Find balance between trees
  • distorts the truth
  • expressive but often not communicative
  • same data in as many different kinds of trees as they want
  • start at any point in the tree
  • same data, different perspectives
  • rotate the tree
  • visual cues that seemed to burst forth with meaning begin to feel meaningless, random, disorienting
  • "watch" in "slow-motion" or user manipulated motion
  • future Chandler may have a richer graphical interface
  • different tree organizations of the same data
  • Overlaying the visualizations
  • composite semi-lattice
  • richness of semi-lattii
  • feed it to users in a way they can easily understand: trees
  • All parameters set in the browser are reflected in the Search bar
  • Saved rules
  • better than limiting users to a single tree
  • better than overwhleming users with a semi-lattice
  • "dumbing down" the data for the user
  • avoid UI shock via information overload
  • present users with the full-force and complexity of their information in a way that is understandable
  • possible, even within the confines of the 2-dimensional
  • easily walk from one tree to another
  • breaking away from hierarchy and how people used to hierarchies of folder are coping
  • http://weblog.edventure.com/blog/_archives/2004/4/19/36468.html
  • the freedom and amorphous-ness of a search-centric navigation paradigm
  • a little built in structure
  • Dashboard view / triage workflow as a point of entry
  • search to get within range
  • navigate using contextual clues to find the exact item
  • fixed hierarchies present a workflow bottlenck
  • we know what topic to file something under, but we don't know where that topic belongs in the hierarchy
  • pilers never bother to file
  • something new comes along to screw up the hierarchy
  • unwieldy taxonomies with duplication and confusion
  • Sometimes we don't know what we're looking for until we see it in context
  • brain's ability to use environmental clues to remember things
Graham Perrin

Chandler Wiki : The Element Of Time - 0 views

chandlerproject.org/...TheElementOfTime

004250

shared by Graham Perrin on 23 Dec 08 - Cached
  • Attaching semantics to items
  • organizing data, needs to be a separate workflow
  • separate UI affordances
  • ...3 more annotations...
  • adding structure to data
  • Getting to the root of the problem with user scenarios
  • The question remains: How do people get an eagle-eye view of their data?
Graham Perrin

Chandler Wiki : How The Cookie Crumbles Part I - 0 views

chandlerproject.org/...HowTheCookieCrumblesPartI

588008 588016 588445 588034 anatomy browse cookie data edible faux guide hierarchy impish jumbled kooky loop-de-loop messy naughty ontology organisation project quality result structure tagsonomies tagsonomy tags tag tagging time Uhuru Voovay wig xylophon

shared by Graham Perrin on 22 Dec 08 - Cached
  • hierarchies has been the designated one size fits all solution to all our organizational needs
  • we break our semantically pure hierarchies by overstretching their bounds
  • we end up with messy hierarchies that are unusable and unmaintainable
  • ...4 more annotations...
  • Stuff I need access to DOES NOT HAPPEN TO EQUAL the stuff at the top of the tree
  • Case study: Katie's OmniOutliner
  • http://www.shirky.com/writings/ontology_overrated.html
  • The following are images taken from: http://www.shirky.com/writings/ontology_overrated.html
Graham Perrin

Chandler Wiki : The Nature Of Tags - 0 views

chandlerproject.org/...TheNatureOfTags

tags tag hierarchy

shared by Graham Perrin on 22 Dec 08 - Cached
  • Tags multiply like rabbits!
  • Tags make items look like they're multiplying like rabbits
  • the ability to assign more than 1 tag to an item
  • ...17 more annotations...
  • becomes a cognitive quagmire when it comes time to get a grip on the scope of your data
  • ramplant multiplication of items showing up in multiple tag-groups can make a mountain out of a mole hill of data
  • Tags don't actually help you understand your data better
  • hierarchies visualize degrees of separation
  • in Tagsonomies, all neighbors are created equal
  • If what you're looking for doesn't exist in the tag or the intersection of tags you're currently looking at, you're out of luck
  • Without a visualization tool, tags are just as dumb if not dumber than hierarchies
  • 2 kinds of relationships
  • tags are either Related or Not related
  • Tagsonomies are too flexible for their own good
  • Some of the MIT Haystack studies asked users to "tag" URLs they found on the web with keywords
  • many of the users began to feel like the whole process pointless
  • they find it pointless to apply the keywords after a while
  • Tags are too generic
  • The notion of "related tags" is too generic
  • Tags are unable to store important metadata about both our data and the relationships that govern and structure that data
  • Tagged data sets quickly explode beyond human ability to extract narrative and scope from the data
Graham Perrin

Chandler Wiki : Vision - 0 views

chandlerproject.org/vision

004250

shared by Graham Perrin on 22 Dec 08 - Cached
  • Custom Attribute
  • Custom Attribute
  • The Chandler Knowledge Worker
  • ...42 more annotations...
  • Information is the substance of their work and more information is the output of their work: Research, proposals, priorities, direction and decisions?
  • knowledge is gained and shared
  • how people actually work
  • (too) many interesting things
  • There's something wrong with the way data
  • doesn't flow between the tools we use to manage, process, organize our information
  • software should be modeled around information
  • technological barriers
  • too much copying and pasting
  • false assumption that information management tasks are binary
  • false assumption underlying most productivity software that information and the organizational structures needed to manage that information are essentially static
  • A lone email languishes for a long time in your Inbox and then all of a sudden, blooms into an unending thread which dies down
  • the thread is revived and mushrooms into a full scale project
  • Three weeks later
  • you barely give it a thought
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      I tend to find myself involved in: at one extreme, very many varied small tasks, which are recorded/archived then intentionally forgotten; and at the other extreme: projects about which thought extends months or even years later. Between the two extremes: for me, things are hazy.
  • the same workflow hiccups show up again and again
  • an information management environment with built-in workflows that mirror what people hack together
  • three basic workflows everybody seems to construct for themselves, regardless of what tools they use
  • varying degrees of complexity and automation
  • These three workflows however, need to exist independently of each other
  • no complicated rule-builder
  • push-button interface
  • always assume a need for iteration and change over time
  • Peeling the Onion
  • Allow Organization to Change and Flow
  • the entire gamut of organizational affordances
  • Tagging
  • Filing, Rules, et cetera
  • won't ever be asked to decide between them
  • turn it into a Custom Attribute
  • Add semantics to a Tag
  • Custom Attribute
  • Drag a Tag or a Cluster to the sidebar
  • a Cluster: a way to thread items together, a way to reflect dependencies
  • Group collaboration systems exist in parallel with personal communication tools
  • does not scale down to work for small groups
  • the majority of the significant emails we send are sent while still in a draft-state
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      This is very thought-provoking.
  • Future
  • a well-defined end-user information model
  • by modeling the user experience around how people work today and the substance of that work, we can be more than just another software tool and instead aspire to be a system for information management: A smarter way to work. A better environment for collaboration
  • We want Chandler to be able to talk to other applications
  • As we make Chandler's end-user information model richer, the number of interesting applications to talk to will increase. This is one of the many areas where we hope that people in the community will help increase Chandler's ability to talk to other applications
1 - 5 of 5
Showing 20▼ items per page