Where does Web 2.0 live in your organisation?

Last night Lynda Kelly left a comment that pointed me to her audience research blog and to an interesting discussion on fresh + new back in June last year; which in turn lead me to Organizational Barriers to Using Web 2.0 Tools. This post quoted a 'nonprofit user' who:

…pointed out to me that while she sees that social media tools make it easier for non-technical types to integrate technology into their workflow, at the same time there's an ongoing organizational message that says "Leave the technology stuff to the IT department."

Interestingly, (and this is in part based on my experience in different organisations over the years) sometimes the IT department are given the message "leave the web to the marketing department" or the education department, or to the curators…

Given that social technologies are not, by definition, traditional publications like official 'brand' and venue messages or rigorous academic research, and may not yet have a place in the organisational publication program, what is the practical effect of the ownership of web projects in a cultural heritage organisation?

And what happens if the 'participatory web' falls in an organisational limbo, with no-one able to commission or approve applications or content? More importantly, how can we work around it?

I think this is where some of the frustrations Frankie Roberto expressed come in – different departments have different priorities and working practices and are more or less risk-averse (and have different definitions of 'risk).

(However, I don't think you can underestimate the urge to archive and curate that many museum people feel. That archival urge possibly just goes along with the kinds of personalities that are drawn to work in museums. I have it myself so maybe I'm too sympathetic to it.)

Recommendations for AJAX and accessibility

A new Webcredibles article, AJAX accessibility for websites, highlights some of the potential benefits and disadvantages of AJAX technologies.

The section on recommendations for AJAX and accessibility was particularly useful, and a lot of the advice probably applies to non-traditional browsers such as mobile phone users. Basically:

  • Inform users early in the page that dynamic updates will occur
  • Highlight the areas that have been updated
  • Don't change the focus
  • Offer the option to disable automatic updates
  • Ensure the site works if JavaScript isn't enabled

Museum technology project repository launched

MCN have announced the launch of MuseTech Central, a project registry where museum technologies can 'share information about technology-related museum projects'. It sounds like a fabulous way to connect people and share the knowledge gained during project planning and implementations processes, hopefully saving other museum geeks some resources (and grey hairs) along the way.

I'd love to see something like that for user evaluation reports, so that institutions with similar audiences or collections could compare the results of different approaches, or organisations with limited resources could learn from previous projects.

More on cultural heritage and resistance to the participatory web

I've realised that in my post on 'Resistance to the participatory web from within the cultural heritage sector?', I should have made it clear that I wasn't thinking specifically of people within my current organisation. I've been lucky enough to meet a range of people from different institutions at various events or conferences, and when I get a chance I keep up with various cultural heritage email discussion lists and blogs. One way or another I've been quietly observing discussions about the participatory web from a wide range of perspectives within the cultural heritage and IT sectors for some time.

Ok, that said, the responses have been interesting.

Thomas at Medical Museion said:

This are interesting observations, and I wonder: Can this resistance perhaps be understood in terms of an opposition among curators against a perceived profanation of the sacred character of the museum? In the same way as Wikipedia and other user-generated content websites have been viewed with skepticism from the side of many academics — not just because they may contain errors (which encyclopedia doesn’t?), but also because it is a preceived profanation of Academia. (For earlier posts about profanation of the museum as a sacred institution, see here and here.). Any ideas?

I'm still thinking about this. I guess I don't regard museums as sacred institutions, but then as I don't produce interpretative or collection-based content that could be challenged from outside the institution, I haven't had a vested interest in retaining or reinforcing authority.

Tom Goskar at Past Thinking provided an interesting example of the visibility and usefulness of user-generated content compared to official content and concluded:

People like to talk about ancient sites, they like to share their photos and experiences. These websites are all great examples of the vibrancy of feeling about our ancient past.

For me that's one of the great joys of working in the cultural heritage sector – nearly everyone I meet (which may be a biased sample) has some sense of connection to museums and the history they represent.

The growth of internet forums on every topic conceivable shows that people enjoy and/or find value in sharing their observations, opinions or information on a range of subjects, including cultural heritage objects or sites. Does cultural heritage elicit a particular response that is motivated by a sense of ownership, not necessarily of the objects themselves, but rather of the experience of, or access to, the objects?

It seems clear that we should try and hook into established spaces and existing conversations about our objects or collections, and perhaps create appropriate spaces to host those conversations if they aren't already happening. We could also consider participating in those conversations, whether as interested individuals or as representatives of our institutions.

However institutional involvement with and exposure to user-generated content could have quite different implications. It not only changes the context in which the content is assessed but it also lends a greater air of authority to the dialogues. This seems to be where some of the anxiety or resistance to the participatory web resides. Institutions or disciplines that have adapted to the idea of using new technologies like blogs or podcasts to disseminate information may baulk at the idea that they should actually read, let alone engage with any user-generated content created in response to their content or collections.

Alun wrote at Vidi:

Interesting thoughts on how Web 2.0 is or isn’t used. I think one issue is a question of marking authorship, which is why Flickr may be more acceptable than a Wiki.

I think that's a good observation. Sites like Amazon also effectively differentiate between official content from publishers/authors and user reviews (in addition to 'recommendation'-type content based on the viewing habits of other users).

Another difference between Flickr and a wiki is that the external user cannot edit the original content of the institutional author. User-generated content sites like the National Archives wiki can capture the valuable knowledge generated when external people access collections and archives, but when this user-generated content is intermingled with, and might edit or correct, 'official' content it may prove a difficult challenge for institutions.

The issue of whether (and how) museums respond to user-generated content, and how user-generated content could be evaluated and integrated with museum-generated content is still unresolved across the cultural heritage sector and may ultimately vary by institution or discipline.

Open Source Jam (osjam) – designing stuff that gets used by people

On Thursday I went to Google's offices to check out the Open Source Jam. I'd meant to check them out before and since I was finally free on the right night and the topic was 'Designing stuff that gets used by people' it was perfect timing. A lot of people spoke about API design issues, which was useful in light of the discussions Jeremy started about the European Digital Library API on the Museums Computer group email list (look for subject lines containing 'APIs and EDL' and 'API use-cases').

These notes are pretty much just as they were written on my phone, so they're more pointers to good stuff than a proper summary, and I apologise if I've got names or attributions wrong.

I made a note to go read more of Duncan Cragg on URIs.

Paul Mison spoke about API design antipatterns, using Flickr's API as an example. He raised interesting points about which end of the API provider-user relationship should have the expense and responsibility for intensive relational joins, and designing APIs around use cases.

Nat Pryce talked about APIs as UIs for programmers. His experience suggests you shouldn't do what programmers ask for but find out what they want to do in the end and work with that. Other points: avoid scope creep for your API based on feature lists. Naming decisions are important, and there can be multilingual and cultural issues with understanding names and functionality. Have an open dialogue with your community of users but don't be afraid to selectively respond to requests. [It sounds like you need to look for the most common requests as no one API can do everything. If the EDL API is extensible or plug-in-able, is the issue of the API as the only interface to that service or data more tenable?] Design so that code using your API can be readable. Your API should be extensible cos you won't get it right first time. (In discussion someone pointed out that this can mean you should provide points to plug in as well as designing so it's extensible.) Error messages are part of the API (yes!).

Christian Heilmann spoke on accessibility and make some really good points about accessibility as a hardcore test and incubator for your application/API/service. Build it in from the start, and the benefits go right through to general usability. Also, provide RSS feeds etc as an alternative method for data access so that someone else can build an application/widget to meet accessibility needs. [It's the kind of common sense stuff you don't think someone has to say until you realise accessibility is still a dirty word to some people]

Jonathan Chetwynd spoke on learning disabilities (making the point that it includes functional illiteracy) and GUI schemas that would allow users to edit the GUI to meet their accessibility needs. He also mentioned the possibility of wrapping microformats around navigation or other icons.

Dan North talked about how people learn and the Dreyfus model of skill acquisition, which was new to me but immediately seemed like something I need to follow up. [I wonder if anyone's done work on how that relates to models of museum audiences and how it relates to other models of learning styles.]

Someone whose name I didn't catch talked about Behaviour driven design which was also new to me and tied in with Dan's talk.

Another way to find out what's being said about your organisation

If you're curious to know what's being said about your institution, collection or applications, Omgili might help you discover conversations about your organisation, websites or applications. If you don't have the resources for formal evaluation programs it can be a really useful way of finding out how and why people use your resources, and figure out how you can improve your online offerings. From their 'about' blurb:

Omgili finds consumer opinions, debates, discussions, personal experiences, answers and solutions. … [it's] a specialized search engine that focuses on "many to many" user generated content platforms, such as, Forums, Discussion groups, Mailing lists, answer boards and others. … Omgili is a crawler based, vertical search engine that scans millions of online discussions worldwide in over 100,000 boards, forums and other discussion based resources. Omgili knows to analyze and differentiate between discussion entities such as topic, title, replies and discussion date.

Online participation at the EU – vote on the new euro coin

It seems the EU is taking online participation seriously: Help us choose the design of the new euro coin

To celebrate the 10-year anniversary of the launch of Economic and Monetary Union (EMU) and the creation of the euro, all euro-area countries will issue a commemorative 2-euro coin with a common design. It will be available at the beginning of 2009.
A design competition between the mints of the euro area has resulted in the pre-selection by the Mint Directors of 5 designs, presented here. The final winning design will be selected exclusively by your votes via this web page.

The selection is open to all EU citizens and residents. Each person may only vote once. A prize of a set of high-value euro collector coins will go to a participant chosen at random from those who voted for the winning design. Voting will be closed on 22 February 2008.

You can view the designs without registering – just click on the 'VOTE NOW' button.

You have to give an physical address and list your country but while the site says "This information is used to validate and record your choice, and to contact you in the event you are selected as a prizewinner", it doesn't say how it will check that you're an EU citizen or resident, or how they'd prevent people voting with other email addresses.

Still, it's an interesting experiment, especially as it will result in a very evident real world outcome.

Resistance to the participatory web from within the cultural heritage sector?

Various conversations I've been having over the past few weeks have given me the idea that resistance to the 'participatory web' (Web 2.0/social networking sites/user-generated content) could in part be based along disciplinary lines – I'd love to follow that up and find out if art historians are more resistant than social historians, for example.

Or does it depend on the context – whether the user-generated content occurs in or outside the official website, or whether the audience is an unknown mass of the general public or a community of specialists, educators or peers? Does it depend on the age of the individual? Is it about control? Or fear that we are making unknown content appear 'trustworthy' through its association with our institutions? Is it seen as unprofessional, or as pandering to the lowest common denominator?

I'm also interested in how this resistance is demonstrated – is it active (people within the institution refuse permission) or passive (people just don't produce content)?

Is user-generated content more acceptable in some contexts than others? Does it matter whether visitors are commenting on existing content with clear lines between institutional- and user-generated content (perhaps on Flickr) or editing the curators opinion (perhaps on the National Archives' Your Archive wiki)? Are reminiscences ok when other forms of user-generated content aren't? Does the ability to relate content back to a user profile make a difference?

At this point all I have is a lot of questions. If you have any experiences of resistance to or cooperation with participator web projects of your own, or know of research in this area, I'd love to hear from you.

As an aside, I suspect it doesn't help that lots of institutions block Facebook, YouTube, etc. I've always thought people should at least be able to view whatever 'timewasting' sites they like in their own lunchbreak, and it would mean that staff are more likely to be familiar with the environments in which their content might appear.

Personal blogs in cultural heritage and museums on Flickr

I meant to mention this at the e-learning group's 'Wine, Web 2.0' event on Thursday when someone asked about official blogs written from personal (rather than marketing or institutional) viewpoint: the British Library's Breaking the Rules blog strikes me as very personal – maybe not compared to the blogosphere as a whole, but compared to other 'work' blogs within the cultural heritage sector.

Also, the East Lothian Museums have been using Flickr (http://www.flickr.com/photos/eastlothian/ to display some of their 25,000 items. It's worth checking out if you're thinking about how you might use Web 2.0 sites or if you're curious about their content. FWIW, they're also blogging.