Configuring the Oticon Epoq’s Streamer with Windows Vista

Oddly, configuring audio Bluetooth devices with Vista has been turned into something of a convoluted process, but once you get the steps, it’s pretty straightforward. The steps below let me use both the audio and microphone tie-ins for the Streamer within Vista. Many thanks to this page for giving me the steps I needed to turn around and make this work properly.  This is not a perfect procedure; you may encounter hiccups with the Streamer losing connection or audio programs crashing.

First, place the Streamer into Bluetooth pairing mode by pressing and holding the Bluetooth button for seven seconds – you will hear one beep two seconds in and another once the pairing mode is activated.

Next, we have to pair the device with the laptop (note that this assumes said laptop has Bluetooth capacity and has the WIDCOMM drivers loaded – if it doesn’t, this sequence may not work).  Note that Dell’s Bluetooth devices are automatically installed on the machine using the correct WIDCOMM drivers, so they’re available as a download from them if needed via  If the Bluetooth icon is showing in the system taskbar, then you can simply right click and select “Add Devices”.  If not, you have to go to the “Start” menu, open the “Control Panel”, and select “Bluetooth Devices”, then click “Add Wireless Device” button along the top bar.

You are then prompted to select the device that you wish to pair (I turned off all other Bluetooth devices I had floating around to make sure the streamer didn’t get confused and try to do the wrong thing):

Click the “Next” button with the Streamer selected.  Next, you will be prompted to select an option for pairing the device.  You want to select the middle option, “Enter the device’s pairing code”:

On the next screen, enter the pairing code for the Streamer (0000 – all zeroes) and click “Next”:

The next screen you see prompts to select the type of hands-free device being connected – take the default option:

Next, open the “Bluetooth Devices” option screen in the Control Panel if it hasn’t already opened for you and right click on the “Streamer” entry, then click on “Properties”:

When the Properties pane opens, select the “Services” tab and check all of the available checkboxes except for the “Remote Control” checkbox:

Click “OK” to close the Properties pane.  Along the top of the “Bluetooth Devices” window, select “Bluetooth Settings” from the toolbar:

On the “Bluetooth Radio Properties” pane, select the “Audio” tab.  If any of these devices list as connected, click on them and then click the “Disconnect” button. Select the “Bluetooth Stereo Audio” option and click the “Connect” button:

Open your Control Panel again and then click on “Sound”:

On the “Playback” tab, right click the entry that reads “Bluetooth Stereo Audio” and select “Set as Default Device”.  You may have to show disabled or disconnected devices (done via the right-click menu) to see the “Bluetooth Stereo Audio” option – if done correctly, that option should be there without having to do anything further.

Now open your favorite audio program and play away!

Note that I have not been able to resolve issues where iTunes (my music player of choice) may randomly decide to crash under this arrangement.  I also have noticed that the device itself sometimes will simply disconnect for no clear reason, which means trying to force it to reconnect using the “Bluetooth Radio Properties” dialog box above.

My Tribulations in Dell’s Universe: How Twitter Saved Two Reputations

I’ve always been a faithful Dell customer. I’ve never, ever had a problem that Dell Support couldn’t fix; in fact, in college, I once sent my laptop in for depot service and got it back the next day. If that doesn’t make for an impressive and accurate customer service and a model to emulate, I’m not entirely certain what does.

So, of course, when it was time to upgrade my laptop again, it was a fairly obvious choice for me: Dell was automatically in the running. I ended up choosing a Dell XPS M1330, which I got for Christmas in 2007. The laptop worked incredibly well for several months — long enough that I was fairly convinced that I had made another good selection. In April of 2008, however, I started experiencing issues with the laptop’s power — the battery would take an abnormally long time to charge, losing a full charge faster than it would charge to begin with, abruptly slowing down significantly on random occasions when it was plugged into the wall, and spontaneously shutting down randomly. I, of course, opened a ticket with Dell fairly quickly when I identified this as a systemic problem — taking over 6 hours to charge from around 10% battery charge to a full charge seemed bad, somehow.

Little did I know what I was walking in to at the time.

Continue reading

Moodle UI hacking

I’ve been doing my own little bit of user interface hacking on Moodle for work, since the layout we had before (below) didn’t work well for our purposes; specifically, the issue we had was with the “Enrolment (remote) database fields” section, which is supposed to map values from a remote database tables into Moodle’s local database tables so that students can be automatically enrolled in courses.  Before, the screen looked like this:


My user interface tweaks below include a new mapping category done by our in-house web developer Lucian DiPeso so that the full name of the course could also be used locally.  The new section, relabelled “Data Mapping”, has eight text fields instead of the original six for precisely this reason.


The only issue with this layout change is that the help text on the right-hand side of the new table isn’t in line with the rest of the help text on the screen, which I expect to correct soon.

There is one other change that we will be implementing on this screen, but that won’t generate as substantial a user interface change as our need to re-envision the data mapping portion did.

We do intend to commit these changes back to the Moodle core, but we’ll see whether they are accepted or not (this won’t be done until we’re absolutely sure the code changes required across several Moodle files are completed).

Welcome to My New Home!

I’ve moved over to a new personal domain and redirected my old domain ( to this one. I’ll be holding on to for some time to come and have no plans to get rid of it. I feel like this new domain will offer me the ability to help build not only my online identity but my offline one as well. Some handy-dandy .htaccess wizardry let me do the redirect:

# BEGIN Redirect to new domain
Options +FollowSymlinks
RewriteEngine On
RewriteCond %{HTTP_HOST} [NC]
RewriteRule ^/*(.*)$1 [L,R=301]
RewriteCond %{HTTP_HOST} [NC]
RewriteRule ^/*(.*)$1 [L,R=301]
# END Redirect to new domain

Comments on this shift are, of course, greatly appreciated. Please do update your RSS readers if you are using the old domain (and update your links as well!)

Could Obama Mean Drastic Change for Social Media and Technology in Government?

With our new president-elect being heralded by the TV networks, could this mean a drastic shift in the way that technology is used in government?  We are seeing the end of an era:

Nov. 4, 2008, is a historic day because it marks the end of an economic era, a political era and a generational era all at once.

Economically, it marks the end of the Long Boom, which began in 1983. Politically, it probably marks the end of conservative dominance, which began in 1980. Generationally, it marks the end of baby boomer supremacy, which began in 1968. For the past 16 years, baby boomers, who were formed by the tumult of the 1960s, occupied the White House. By Tuesday night, if the polls are to be believed, a member of a new generation will become president-elect.

So today is not only a pivot, but a confluence of pivots.

— David Brooks, “A Date with Scarcity“, New York Times, November 3, 2008

Could this also mark a new beginning in the realization of technology usage in public government?  Obama’s grassroots campaign coordinated using the Internet, and it would be a significant oversight to lose that element of his work.  From Twitter to Facebook to his own web site, he utilized the tools of the 21st century to mobilize a huge following that pushed him to a landslide.

What if that following demanded accountability through social media?  What if Obama continued to tweet on the issue that he was considering, that mattered to the nation?  What if the grassroots movement he started was applied to the White House web site?  What if the change he promised continued to be a grassroots effort, with him taking the role of a peer who considers all angles, rather than one of Commander in Chief, whose decisions are final?  Obama has recognized the power of my generation – the “Net Generation” or the “Digital Generation”, whatever you choose to call us.  What if he continued to leverage that power?

What change could he achieve then?

Book Review: Wikinomics: How Mass Collaboration Changes Everything

Book Cover for Wikinomics

This review is cross-posted from Kevin Desouza’s blog "Ideas 4 Change: Thoughts from an Info Mgmt Class".

Wikinomics: How Mass Collaboration Changes Everything. Don Tapscott and Anthony D. Williams. New York: Portfolio, 2008. 315pp. $27.95 (ISBN 978-1-59184-193-7)

The essential premise of this work is that the business world as we know it has been changed irrevocably by bottom-up models of collaboration inspired and driven by the Internet. The authors, Don Tapscott and Anthony D. Williams, argue that businesses have two choices: yield to the power of distributed collaboration or die.

Wikinomics strives to set forth a new economic model that takes advantage of a collision of forces: the advent of cheap technologies that enable cheap, easy collaboration and a new generation of workers that have grown up in an increasingly digital world. It argues that collaboration itself has been redefined, that "[t]he new promise of collaboration is that with peer production we will harness human skill, ingenuity, and intelligence more efficiently and effectively than anything we have witnessed previously" (18). The pillars of wikinomics – openness, peering, sharing, and acting globally – replace a tired business method foundationally supported by the idea of the hierarchy and holding knowledge and creative power within companies, jealously guarding these resources as sacrosanct. Rather than companies dictating what they will and will not accept as goods and services to customers or suppliers, companies must now innovate and work alongside them. Organizations not working with the customer merely leads to customers circumventing organizations and designing their own products and services; the organization then misses out on an opportunity to vastly improve products and services and to innovate (149).

The core chapters of the book set forth seven competitive and growth models for corporate use, with an introductory overview, a discussion of what factors created the fundamental changes discussed within the book, one chapter devoted to addressing the arguments against the wikinomics model, and one chapter devoted to discussing how these models can be implemented in what the authors consider the organizations of old. The authors set forth the following seven models:

  • Peer producers, where individuals independently form groups to produce something (67);
  • Ideagoras, global marketplaces of ideas and innovations (98);
  • Prosumers, consumers that both consume and produce goods and services (126);
  • The New Alexandrians, embracers of the openness of today’s economies who construct new collaborative environments (156-7);
  • Open platforms, where companies open their wares for others to build upon (184);
  • The global plant floor, where companies no longer keep all their knowledge and talent in-house and instead farm out responsibility and risk to suppliers, who, in turn, become partners in invention (218);
  • And, finally, the wiki workplace, where openness, collaboration, sharing, and acting globally are creating a new workplace (240).

Elements of each of these models – which all bring outside resources into the center of organizational culture – can foster successful assimilation into the new open economy.

One of the major unacknowledged themes in Wikinomics is the idea that the modern worker suffers from an abundance of information overload, which is, in part, due to the way organizations operate. This is a particularly interesting thread from an information management perspective. In the Wiki Workplace chapter, the authors write that

. . . the vast majority of employees don’t do business processes anymore, at least not in the traditional sense. After years of optimizing supply chains, outsourcing, automation, and stripping costs and inefficiencies out of the back office, most employees spend very little of their day working on regularized activities. "What they do," says [Ross Mayfield, CEO and founder of Socialtext], "is they manage exceptions to processes. Even in the most mundane workplaces like a call center, people are constantly wrestling with new problems" (255, emphasis added).

Workers no longer deal with the routine; they deal with the rule-breakers, and that negotiation often ends up in a slew of information that is never documented or captured for organizational use (and in fact, often gets lost in the shuffle of daily e-mail) (256).

Open platforms really discuss empowering people with access to information that the companies themselves have only loose ideas of how to handle. Tapscott and Williams frame this along the lines of the adage in the Linux community known as "Linus’s Law" after Linux coordinator Linus Torvalds (which, surprisingly, given that they hold Linux up as a model of innovation, is never quoted in the book itself): "given enough eyeballs, all bugs are shallow". To restate this in the context of the book, given enough eyes, all solutions are shallow. Companies lack access to resources to realize all the potential that their data or inventions have – even if they had these resources, they would be unable to process the information. Thus, they are forced to open their walls and create scenarios where "ordinary people can create effective new information services that are more resilient than bureaucratic channels" with these "open platforms for innovation inviting unprecedented participation in value creation" (188).

So with all of the new information thrust upon us and with the advent of such broad-ranging technologies that enable collaboration cheaply and easily across geographic, technological, and ideological boundaries, what are organizations to do? Tapscott and Williams contend that the only things organizations can do – and the only way they survive – is to adapt themselves rapidly to the new models of sharing and cooperation that this "perfect storm of technology, demographics, and global economics" creates (54). The Net Generation, with drastically different norms than seen in business in the past – "speed, freedom, openness, mobility, authenticity, and playfulness" (54) – combined with cheap collaboration technology combined with a global economy that "demands and enables new kinds of economic cooperation and opens up the world of knowledge workers to every company seeking uniquely qualified minds to solve their problem" have created new and unusual problems for organizations to address (55). This storm means that "the new Web is inherently dangerous for the business models that depend on controlling the means of creation and distribution", and organizations must adjust (273).

This is a paradigm shift. Paradigms are mental models that constrain our thinking and are often based on assumptions so strong we don’t notice them. New paradigms cause disruption and uncertainty, even calamity, and are nearly always received with coolness, hostility, or worse. Vested interests fight against the change, and leaders of the old are often the last to embrace the new. Consequently, a paradigm shift typically causes a crisis of leadership (285).

Change management here is an essential trait. However, according to Tapscott and Williams, change management has to start from where companies are today, creating a map between what the company currently does and how it will innovate and collaborate in new economic waters (291). Companies must decide the extent to which they will release their reigns on their internal knowledge and intellectual property; however, the timing of this is vitally important (292). Failure to stage this transition correctly – or to release too much intellectual property – will send a company down in flames (177-8).

Most importantly, this sort of change starts from within. "When confronted with such an all-encompassing revolution in business most companies wonder where they should begin. Our answer is to start at home, by fostering collaboration in the workplace" (313). In addition,

Ignoring the cultural memes and norms of the organization is a common way to have the principles and practices of wikinomics discredited at initiation. Champions of this kind of change need to be sensitive to these concerns and structure their engagement with the enterprise in a way that allows the benefits of collaboration to manifest themselves in pilot projects that can be scaled up and help build further momentum for cultural change (313).

Tapscott and Williams clearly believe in the transformative powers of the innovations of Web 2.0. They recognize that a new generation of people raised with computers and electronics is fundamentally altering the economic landscape now and for years to come. This book made me think long and hard about some of the ideas they had for engaging the workplace in creation and change. They are, at least, realists who recognize that this sweeping change cannot and will not be immediate; for this, I give them a hefty dose of credit. They also recognize that there is a range of options that organizations can take to become more nimble in an economy that implements the ideas of wikinomics. One major challenge to their thinking is that they seem to frame the issue as if this generation were the first to realize the potential for drastic, sweeping change. There have been many instances in the past century where the idea of the old economy being swept away have presented themselves, with no particular action taken as a result. Wikinomics is not the be-all, end-all solution that it occasionally is presented as.

As a last note, I found myself strongly contesting one major theme of the book as I read. In talking about the "N-Geners" (people born between 1977 and 1996 inclusive, a generation that I am definitely part of), Tapscott and Williams assert the following:

N-Geners are not content to be passive consumers, and increasingly satisfy their desire for choice, convenience, customization, and control by designing, producing, and distributing products themselves . . . The ability to remix media, hack products, or otherwise tamper with consumer culture is their birthright, and they won’t let outmoded intellectual property laws stand in their way (52).

I took exception to these statements as I read, and I found myself reviewing the assertion throughout the book: it is unfair to paint the Net Generation in an "us vs. them" light, where the "them" is established cultural norms. This is a consistent theme throughout the book. I do not consider us at war, which this paragraph implicitly suggests. Instead, we are attempting to understand our place in the world as a generation, and increasingly, the answers have been evident in utilizing the existing culture in new ways. As a generation, we spur change not because we are rebellious or because we believe it us our birthright; rather, we do so because we know no better. Indeed, we do so because this perfect storm that Tapscott and Williams have described exists, and we are merely left to go along for the ride. We are simultaneously the instigators and the lost sheep that Tapscott and Williams discuss when they declare "the old multinational that creates value in a closed hierarchical fashion is dead" (214). We are as muddled, in many ways, as the organizations and corporate leaders that Wikinomics was written for: those trying to figure out how to stay afloat in an increasingly boundary-less society.

InfoCamp Notes – Day 2

Welcome Session (9:30, Theater)

Recaps of things learned yesterday:

  • Theory about why multimedia pods aren’t used in libraries: not social!
  • Creative Commons licensing – as soon as you put something online, it defaults to personal copyright unless licensing model is changed explicitly by the author
  • Legalese: “for when something gets really messed up” (hmm, what’s the lawyer to say to that?) – Complexity of language as a shield
  • Axure: “interesting” – Aaron Louie, a lot of interactions that can’t be represented:
  • Tamara Adlin: demoing Denim:
  • Privacy: it’s all about trust – user experience space hinges on the idea of trust

Plenary: Tamara Adlin: The Dirty Little Secret of User Experience (Theater)

  • “Things that you probably already know but that are too easy to forget”
  • Build something which provides information!  Therefore empowers users!
  • Problem: a lot happens before this is even possible, and all these things are handled by different people
  • If we don’t think about things that happen before design and build, we’ve lost a huge opportunity
  • We are Fish!
  • Waterfall method of designing software
  • Agile is actually “Agilefall”, since nobody’s actually doing agile, they just say they are
  • Information professionals (IP) should be there first understanding things and how they work before anyone else does anything
  • IP bring in their tools, but not much really works.  Why?  We throw our data into a hostile environment – nothing grows no matter what the IP does and no matter how good methods are
  • Environment: “executive staff” – if you don’t understand these, DOOM!
  • Dirty secret of UCD in real business: those that make the decisions haven’t decided what they want you to do! (there’s more to this.)
  • Executive: “Why the hell are you building X?  You should be building Y!” – they didn’t know they didn’t want X until they saw it.
  • Our job: help them figure out what they’re trying to do, then write it down!
  • In order to sell a process, someone has to admit that the current process is broken
  • Big honkin’ reports are still what we end up creating.  But data solves everything!  It’s totally the panacea!
  • We give big presentations with lots of bullet points, putting people to sleep – it’s our fault that they fall asleep!
  • Data solves nothing on its own.  Business speaks “Busineese”, you have to translate stuff in order to show them what’s obvious according to data
  • You can’t create great UX if the corporation is confused
  • In the absence of the forces of good, decisions will be made by a hippo – the (hi)ghest (p)aid (p)erson’s (o)pinion
  • Methods: doctor, heal thyself; make yourself usable to the people who are asking you to produce things.  Analyze your users, then create usable projects
  • Ask for business goals (usually have #s), brand goals (usually related to other brands, perception management), and customer experience goals (things you want to hear after people use your widget) – GET THEM APPROVED OFFICIALLY AT LEAST ONE LEVEL HIGHER THAN THE PERSON YOU’RE WORKING WITH!
  • Help customers get these three things written down – that’s your role as UX
  • Be the dumbest person in the room and apologize a lot.  Congratulate other people for your own ideas.  Remember that everyone in the room walks on thin ice and help them.  When you’re totally stuck remember that everyone else will think whatever you do next is the most inspired thing ever.
  • Do at least one exercise that forces people to play with sticky notes.  Put paper on the wall and sticky notes – it makes people feel important! (Adlin: “Maybe it’s because we deal with electronics all day and then they’re like ‘Ope, Paaaypeeer!'”)
  • Audience question: who needs to be in the room playing with the stickies?
  • If you pick the wrong persona, as long as you’re in the right neighborhood, you’re probably going to create something that’s better than you would have created otherwise.
  • Office: “At some point, someone’s going to want to put a pivot table on a birthday card!”
  • People who need to be in the room: those who care and the biggest pain in the rear available
  • Create personas, then show executives something that looks like Excel.  Create a persona-weighted feature matrix: ask people to weight the personas, then weight the features based on those personas
  • Get from business, brand, and customer experience goals through to actual features and functionality
  • You MUST be able to trace decisions back to the business goals
  • Hippos never go away, but if they sing the same tune, great!
  • When doing activities, go in cold – it shows confidence

Session 5: Geoinformatics: Why You Need the Science, Why the Scientists Needs You (Room 104)

  • Geoinformatics: geographic information systems, using GIS to describe environment – maps!  Find a spot on the surface and get information related to that location.
  • What’s going on with water quality, air quality, the amount of vegetation?  There’s not many piece of information about the environment at a particular location.  USGS has put together before and after imaging of different things – coastline lost, for instance
  • Discussion: we’re information consumers of this information – are we using interfaces to get information about our environment?  What opportunities exist for information professionals in geoinformatics?
  • Frustrations: people provide great data, but no underlying machine-readable files
  • We have precision to see this information, but the interface is bad – “Beautiful map, but we can’t interact with it”
  • UrbanSim:
  • Nat’l Weather Service relies on USGS data to provide things like flood warnings
  • There’s overlap and wasted resources because agencies work on the same issues.
  • Resistance to opening data to a specific standard: “I’m a GIS analyst and I use a complex system and I know that system well, so why should I turn around and give out the data?”
  • Does information get quashed out of fear?  USGS has no regulatory oversight duties – it doesn’t matter whether a volcano’s going to explode tomorrow, they present what’s happening
  • This is about information about the earth – what’s going on, not just what’s on the map
  • The data is completely meaningless without some hint of what that data is about – ideally, the structure given to that data self-narrates and describes what that data is about without additional documentation
  • There’s so much here and so much information that’s useful, but we’re so far down the road that there’s so much data in so many standards that it’s all very hard to start working with now that we’re actually interested in manipulating that data
  • “I want this data to be interoperable” – how do we get that to happen?  Contact USGS, congressperson, representative, anyone you can come up with – Department of the Interior
  • It’s not necessarily the data per se that people want, it’s the tool that interprets the data
  • Useful sites/resources: EPA SuperFund, Storet, National Water Information (NWIS), King County Parcel Viewer

Session 6: Some Database Design and Designing a Database About Everything (Theater), Quentin Christensen

  • How do we come up with a way that we can work with a lot of different diverse database sources?
  • First step: requirement gathering – what’s the data model we want?  What information do we need to have stored?
  • Relation: a table.
  • Normalization: 1st form: only one value; 2nd form: all rows have unique identifier (primary/candidate key); 3rd form: dependencies
  • Physical modeling: how much data do we have, how many times are operations performed, what types of operations?  These all have different costs – performance optimization!
  • Prototyping: create database tables, create operations, etc.
  • SSPiN: Wiki-inspired database system with different aspects that allow for linking generic aspects
  • User-generated content is great for the bottom line – you manage the infrastructure, but the users do all the work on giving your site data to work with

Session 7: Brainstorm: Solving the online identify crisis (Nick Finck) (Theater)

  • There’s you, your circle of friends, then groups of those friends (and networks that extend beyond that second degree)
  • Social networks: not really networks, but tools
  • Supposedly, UX builds these tools to help ease people’s lives… except we’re at the center of the hub and have to maintain all these tools
  • How do we manage all this information that these systems have that are not necessarily being shared but being used?  We really want to share this data across systems, connecting discrete pieces of information across systems.  These services are afraid to share data!
  • We need negotiators: things that take data and then share it with other systems – but systems are very protective against this.  OpenID is a translator, not a negotiator.
  • Common users aren’t programmers – they can’t get into APIs.
  • What happens if users can control and define data about social connections?
  • “I could go out and tell the system, ‘these are all my friends’, and it would just go out and figure out where all my friends are…”
  • We don’t want this kind of a system to be created by a company – we want it to be community-based.  There is no entity that we really want to give sole control over this sort of an idea.  Make it open source.
  • User should be able to control what data is used where and how it’s used – determine whether data should be shared.  System may be able to self-negotiate such a thing.
  • There’s no shared vocabulary that allows the definition of who is friends and other types of contacts
  • Next generation of social networks: it’s not just what’s connected, but the value and strength of those connections
  • If I’m connected to Bob and trying to connect to someone, it’d be interesting to know what that person has done as a result of creating that link.
  • Problem: APIs suck right now for social networks.  They just aren’t useful.
  • Creating separate identities for different purposes – one for professional interactions, one for “the dirt”
  • Services exist that combine all your phone numbers into one with various ways of manipulating where phone calls go
  • For gateway: first identify what accounts are yours, then categorize the accounts – note that some stuff would have to be stored by the gateway service – “the less, the better”
  • Forget CRMs, we need IMs – identity managers.
  • Challenge is where the borders lie: what information do you want/need to be different across services?
  • Define mappings between services, as well as mapping directionality: “this group on LinkedIn maps to this group on Facebook, and this is what I want copied”
  • (perhaps we could call this protocol “identity management protocol” or IDMP…)
  • Build the system based on what exists
  • Biggest problem for this system: membership – how many users does such a system have?

5 Minute Madness (interesting ideas, what we’d like to do, etc.):

  • Delridge Cultural Center has a great Halloween party in its space!
  • Not many blogs linked to the wiki…
  • Sessions touched on a lot of different parts of how we create user-centered information and experiences – these conferences can be overwhelming with “why don’t I, why should I…”
  • Where is your niche?  Not everything everyone else is doing matches every business situation or personality – know your gift and let your particular gift shine
  • What we really need for student research is a central, free tool
  • Idea: Crowdsourcing weather forecasting – put a bunch of transmitters on cars, if windshield wipers are on, where are they?  Anonymous data.  Idea: Metro has transit broadcasters already for bus locations – piggyback?  Washington Ferries do this for marine weather…
  • Idea: GPS track peoples cats – apparently this is already done…
  • Northwest Tea Festival coming up!
  • Refresh Seattle in Fremont

Infocamp Notes – Day 1

Orientation Notes

  • Infocamp: Power to the people.  Enable the user to use technology (but what’s technology?)
  • Disciplines represented: IA, Libraries, HCI, usability, user centered design, technical communication.
  • 2 days, 45 minute presentations – we can react to stuff happening NOW (WaMu)

Keynote – Jacob Wobbrock

  • Degree in HCI
  • dub: University of Washington HCI/design group, stands for “design, use, build” – combines computer sciences, info school, technical communications, school of arts
  • Disability: contrast w/ ability.  Contrast standard parking handicapped sign with other graphics
  • Accessibility: not just for people in wheelchairs, curb cuts: bikers and strollers assist as well.  Curb cuts if built from the beginning save money.  Anticipating accessibility saves money in the long run.
  • Person pushing cart through sliding doors: situationally impaired
  • accessible design: talking about everyone, in different circumstances (situational components)
  • accessibility is usability for all.  It’s not about disability, it’s about what you can do.
  • We have a standard interface for computing that presents challenges to someone with non-standard abilities – we usually adapt the user to the technology, creating specialized technologies.  The assistive technology is a mediator.  But why?  Why not design smarter or adapt existing everyday input devices?
  • EdgeWrite: creates a limited input area to assist with drawing letters
  • Can leverage the properties of edges for more than just text entry – playing with using different input methods along edges of mobile devices, trying to aim for a specific spot in a screen
  • Isn’t the stylus dead due to multitouch?  Weellllll….
  • Reading screen with finger is much different than actually using a screen reader
  • “Why can’t my computer just do the right thing when I type?” – person with peripheral neuropathy
  • Demo TrueKeys: live spell checking as typing occurs.  Challenge: How do you allow someone to not have to verify that a corrected word was done properly?  Is there a way that you can always correct a miscorrected word without feeling pressured?
  • Let’s burden the machine: SUPPLE++ – can we automatically generate UI customized to a person’s individual abilities?  Yup.  Issue low-level tasks, model it, then generate an interface that minimize cost and user errors.
  • Forgotten input device: the microphone!  It can be used in creative ways.  Person painted with his voice using Dragon NaturallySpeaking and MS Paint!
  • Vocal Joystick – voice/vowel map so that vowel sounds force cursor to move in a specific direction.  Can map pitch or loudness.
  • Angular deviation for cursors: create larger or smaller targets for clicking as people use the computer.
  • Why don’t we see targets that expand as we approach them, gravity wells, “slippery slope” guidance to common targets?
  • “The world is a button” – Jake Wobbrock
  • “What if the world was a switch?”  Buttons we need to acquire a confined area – switches, not so much – we can overshoot a switch, it doesn’t change the interaction so long as the interaction crosses the plane of the switch.  The world we’ve created is all totally fake when it comes to technology.
  • Can we get rid of pointing and use something called “goal crossing”?
  • Why do we have to assume desktops are x/y grids?  What about polar coordinates or reels?
  • Start from center, when crossing an icon, bring up specific interactions
  • “Flipping the burden”/ability-based design – allow software to adapt to people’s ability.  Think about accessibility as a potentially better design for everyone.
  • Challenge: it takes a company with developers and infrastructure to really push stuff out!

Session 1: Help Me Turn Data into a New Design (Kristen) – Room 106

  • Wanted to learn what problems people were trying to solve using library web site and tried to figure out how to find that out
  • Used chat with a librarian feature transcript to get feedback on current layout
  • Generated lists of tasks performed and problems people encountered (tasks: locate something vs. searching for something, access a specific database, search for specific piece of information, etc.; problems: people can’t find information, people don’t know what they want, did not understand a policy or service, library doesn’t own resource, etc.)
  • Possibilities: tweak search results and training curricula for searching databases, federated search, map out “task paths” for the most common ways of doing certain tasks, overview of resources available, come up with vocabulary based on chat transcripts, make the main page more visual – MORE WHITESPACE!  If people are stuck, give them an “out” – a way to get help.  Create profiles of users so that professors can “target” content to users that they want to see used.

Session 2: Knowledge Management (Room 102)


  • Research (gleaning new ideas)
  • tacit KM – preserving knowledge in the workplace
  • expertise location
  • knowledge sharing
  • knowledge boundaries
  • information verification and security
  • capture verification
  • value page
  • Jeff Smith: How track experts and make findable, not just a tool?  How expose what you don’t know that you wish you knew?
  • defining wwdk
  • data visualization
  • personalization – tailoring how people receive or record knowledge


  • some of the items in the list above could be treated as inputs into the knowledge management process – information verification, security
  • what is a knowledge management system?  It may not be a system at all…
  • What is a knowledge management system, really? It may not even be a “system” per se – it may be an interaction between elements.
  • In fact, knowledge management isn’t systematic – capturing it is, but knowledge management is CULTURAL.
  • KMS are now just generic systems trying to model particular things.
  • explicit knowledge: universal, tacit knowledge: something that’s inside, can’t be vocalized/translated
  • sometimes we need to be able to push knowledge into the background, but it still needs to be accessible and actionable
  • KMS: what these systems try to achieve can be done much more efficiently by changing the culture to allow a daily interchange of information
  • Knowledge needs context
  • “Modern Society is Document Decadent”
  • knowledge management talked about in the context of organizational goals
  • Knowledge Management Maturity Model:
  • what is the difference between information and knowledge, or do we actually even care?

Session 3: Flat File vs. CMS (Room 106)

  • wants something simple and easy to maintain
  • plone – cms, has problems with web host providing it
  • task: figure out whether to stay with flat files or to move into cms
  • what’s the difference between the two methods?
  • theory: a lot of people want to be able to create and maintain content – what to do with volunteers?
  • “flat”: one HTML page per site
  • CMS: more refined management structure
  • 10-12 pages
  • sections of site may be more dynamic
  • 2-3 days reasonable turnaround time on changes
  • 3-4 people updating
  • consider using templates

Another simplified CMS/Flat file:

  • time consuming to maintain and update
  • 12 pages not dynamic
  • 3-4 people updating
  • jobs – HTML templates
  • knowledge of HTML
  • Seamonkey – HTML Mozilla editor
  • richer experience = more admin time
  • social media
  • users are STC, other orgs
  • share resources
  • timely info and info update problem – users news and events and jobs
  • updates w/o CMS


  • WYSIWYG editor
  • easy to change
  • anyone can do updates
  • events: time/place fields
  • content control and security control
  • set permissions correctly
  • CMS outlive person or person outlive CMS?
  • Instructional overhead/longer learning curve
  • CMS doesn’t necessarily imply web 2.0
  • content and system lives on
  • organizational commitment
  • institutional memory/institutional history of docs
  • distributed users***
  • resource limitations: time, $

Cross-boundary considerations:

  • Google Analytics
  • Culture of content sharing
  • Overall vision
  • users have certain expectations
  • Free stuff? Open source?
  • Do I need this NOW or forever?

Session 4: Structured vs. Unstructured Data (Room 102)

  • Goal of product: search through metadata, find metadata in certain systems and create different views of the information out of the system
  • Created series of products that allows metadata findability, but doesn’t work for unstructured information
  • Structured v. unstructured information definition: structured: database has fields and tables and schemas, the Sematic Web, etc.; unstructured: info that you don’t have access to or that isn’t ordered – photos, video, etc.
  • Types of unstructured data: photographs (inc. print), sound files, text, user input, files, logs, video, animation
  • Structure has to have meaning to someone; something can be very well structured, but if you can’t make sense of it, it’s useless.  You need to be able to UNDERSTAND information.
  • Context makes a big difference on how information ends up being structured.
  • Transforming physical unstructured data: requires physical interaction with objects to add structure on top of the physical data
  • virtually all user input is unstructured unless you can limit inputs

A Tribute to NP-Complete

Inspired by an xkcd comic, NP-Complete, and also because I was buying some DVDs from Amazon anyway, I decided that I wanted to place an order from Amazon that was as close to $100 worth of merchandise as possible after tax and shipping.

The rules:

  • The order must be as close to $100.00 as possible, including tax and shipping charges (note: using free shipping options is not considered cheating).
  • Items in the cart at checkout must be things that the buyer wants and will use. You cannot?????? simply select something that will round out the price tag.
  • All items must be sold by, not their resellers (this is because resellers tack on extra shipping costs for certain items).

This took a bit of work, especially since I already had three DVD box sets in the cart that I was buying via one of Amazon’s TV DVD sales. Values as follows:

  • Stargate Atlantis – The Complete First Season; DVD; $24.99
  • Stargate Atlantis – The Complete Second Season; DVD; $25.00
  • Eureka – Season One; DVD; $25.00

компютри втора употребаI tried first throwing stuff in from my wish list, originally throwing in a paperback copy of Weinberger’s Everything is Miscellaneous. After that, I realized that I had been looking for either a spork or a set of stainless steel chopsticks for home/travel use. I was able to add in a set of stainless steel chopsticks fairly cheaply. With the chopsticks, the book, and the three DVD sets, I got to $98.29 after tax and shipping – roughly $1.70 short.

I spent a bit of time trying to figure out if I could fill that extra $1.70 by buying something small, useful, and cheap – apparently Amazon doesn’t believe in selling individual packets of Post-its or M&Ms or something trivial like that (at least not without going through a reseller, which would break the rules).

I finally managed to get it to $99.75 total with free Super Saver shipping after swapping Weinberger’s book out with another book on my wish list. The breakdown looks like this:

  • Stargate Atlantis – The Complete First Season; DVD; $24.99
  • Stargate Atlantis – The Complete Second Season; DVD; $25.00
  • Eureka – Season One; DVD; $25.00
  • Serves One: Simple Meals to Savor When You’re on Your Own; Toni Lydecker; Paperback; $11.53
  • Global Decor Stainless Steel Chopsticks, 4 Pairs; Kitchen; $4.99

    Subtotal: 91.51
    Free shipping and handling
    Estimated Tax: $8.24
    Total for this Order: $99.75

This is actually an interesting exercise because it exposes information about what Amazon does and does not sell, and also gives some hints as to the usability of the site overall. While I was doing this, I was instant messaging a friend of mine that’s currently serving in Iraq (and coming home in the next couple weeks, I might add) – I originally described this as an “intellectual exercise in consumerism”; he shot back that this is actually interesting social commentary.

This was after calling me a geek/nerd/dork/weirdo/etc.

Old Blog Post

I wrote this for a class project around SharePoint in Fall, and I’m deleting the site, but it’s almost too good to let go of:

I Have “Blog Block”

There’s all this effort going into trying to figure out what I’m supposed to blog about. Drat it, I have no topic ideas. None. Zip. Nada.

And that, ironically, brings me to my topic – writer’s block. Writer’s block is a significant problem for many writers, especially in academic environments where the stakes are high. I suggest several ways of getting out of writer’s block:

  • Don’t write (at least not for a while) – give your brain time to recharge.
  • Consider freewriting for a set period of time – say, 20 minutes. Even if all you do is write the phrase “I have no topic” endlessly, at least you’re writing. When freewriting, don’t stop writing for any reason (unless your life depends on it – your house burning down around your ears is a good reason to stop).
  • Create a community of writers. Perhaps you’re not the only one experiencing writer’s block. Talk to others who might be having the same problem.