Technology – Page 5 – Open Objects

And so it begins: day two of OWOT

Day two of One Week, One Tool. We know what we're making, but we're not yet revealing exactly what it is. (Is that mean? It's partly a way of us keeping things simple so we can focus on work.) Yesterday (see Working out what we're doing: day one of One Week, One Tool) already feels like weeks ago, and even this morning feels like a long time ago. I can see that my posts are going to get less articulate as the week goes on, assuming I keep posting. I'm not sure how much value this will have, but I suppose it's a record of how fast you can move in the right circumstances…

We spent the morning winnowing the ideas we'd put up for feedback on overnight down from c12 to 4, then 3, then 2, then… It's really hard killing your darlings, and it's also difficult choosing between ideas that sound equally challenging or fun or worthy. There was a moment when we literally wiped ideas that had been ruled out from the whiteboard, and it felt oddly momentous. In the end, the two final choices both felt like approaches to the same thing – perhaps because we'd talked about them for so long that they started to merge (consciously or not) or because they both fell into a sweet spot of being accessible to a wide audience and had something to do with discovering new things about your research (which was the last thing I tweeted before we made our decision and decided to keep things in-house for a while). Finally, eventually, we had enough of a critical mass behind one idea to call it the winner.

Personally, our decision only started to feel real as we walked back from lunch – our task was about to get real. It's daunting but exciting. Once back in the room, we discussed the chosen idea a bit more and I got a bit UX/analysty and sketched stuff on a whiteboard. I'm always a bit obsessed with sketching as a way to make sure everyone has a more concrete picture (or shared mental model) of what the group is talking about, and for me it also served as a quick test of the technical viability of the idea. CHNM's Tom Scheinfeldt then had the unenviable task of corralling/coaxing/guiding us into project management, dev/design and outreach teams. Meghan Frazer and Brian Croxall are project managing, I'm dev/design team lead, with Scott Kleinman, Rebecca Sutton Koeser, Amy Papaelias, Eli Rose, Amanda Visconti and Scott Williams (and in the hours since then I have discovered that they all rock and bring great skills to the mix), and Jack Dougherty is leading the outreach team of Ray Palin and Amrys Williams in their tasks of marketing, community development, project outreach, grant writing, documentation. Amrys and Ray are also acting as user advocates and they've all contributed user stories to help us clarify our goals. Lots of people will be floating between teams, chipping in where needed and helping manage communication between teams.

The Dev/Design team began with a skills audit so that we could figure out who could do what on the front- and back-end, which in turn fed into our platform decision (basically PHP or Python, Python won), then a quick list of initial tasks that would act as further reality checks on the tool and our platform choice. The team is generally working in pairs on parallel tasks so that we're always moving forward on the three main functional areas of the tool and to make merging updates on github simpler. We're also using existing JavaScript libraries and CSS grids to make the design process faster. I then popped over to the Outreach team to check in with the descriptions and potential user stories they were discussing. Meghan and Brian got everyone back together at the end of the day, and the dev/design team had a chance to feed back on the outreach team's work (which also provided a very ad hoc form of requirements elicitation but it started some important conversations that further shaped the tool). Then it was back over to the hotel lobby where we planned to have a dev/design team meeting before dinner, but when two of our team were kidnapped by a shuttle driver (well, sorta) we ended up working through some of the tasks for tomorrow. We're going to have agile-style stand-up meetings twice a day, with the aim to give people enough time to get stuck into tasks while still keeping an eye on progress with a forum to help deal with any barriers or issues. Some ideas will inevitably fall by the wayside, but because the OWOT project is designed to run over a year, we can put ideas on a wishlist for future funded development, leave as hooks for other developers to expand on, or revisit once we're back home. In hack day mode I tend to plan so that there's enough working code that you have something to launch, then go back and expand features in the code and polish the UX with any time left. Is this the right approach here? Time will tell.

#owot dev team is hard at work. #fb pic.twitter.com/Zj5PW0Kj2a
— Brian Croxall (@briancroxall) July 31, 2013

Working out what we're doing: day one of One Week, One Tool

Hard at work in The Well

I'm sitting in a hotel next to the George Mason University's Fairfax campus with a bunch of people I (mostly) met last night trying to work out what tool we'll spend the rest of the week building. We're all here for One Week, One Tool, a 'digital humanities barn raising' and our aim is to launch a tool for a community of scholarly users by Friday evening. The wider results should be some lessons about rapidly developing scholarly tools, particularly building audience-focused tools, and hopefully a bunch of new friendships and conversations, and in the future, a community of users and other developers who might contribute code. I'm particularly excited about trying to build a 'minimum viable product' in a week, because it's so unlike working in a museum. If we can keep the scope creep in check, we should be able to build for the most lightweight possible interaction that will let people use our tool while allowing room for the tool to grow according to uses.

We met up last night for introductions and started talking about our week. I'm blogging now in part so that we can look back and remember what it was like before we got stuck into building something – if you don't capture the moment, it's hard to retrieve. The areas of uncertainty will reduce each day, and based on my experience at hack days and longer projects, it's often hard to remember how uncertain things were at the start.

Are key paradoxes of #owot a) how we find a common end user, b) a common need we can meet and c) a common code language/framework?
— Mia (@mia_out) July 29, 2013

Meghan herding cats to get potential ideas summarised

Today we heard from CHNM team members Sharon Leon on project management, Sheila Brennan on project outreach and Patrick Murray-John on coding and then got stuck into the process of trying to figure out what on earth we'll build this week. I don't know how others felt but by lunchtime I felt super impatient to get started because it felt like our conversations about how to build the imaginary thing would be more fruitful when we had something concrete-ish to discuss. (I think I'm also used to hack days, which are actually usually weekends, where you've got much less time to try and build something.) We spent the afternoon discussing possible ideas, refining them, bouncing up and down between detail, finding our way through different types of jargon, swapping between problem spaces and generally finding our way through the thicket of possibilities to some things we would realistically want to make in the time. We went from a splodge of ideas on a whiteboard to more structured 'tool, audience, need' lines based on agile user stories, then went over them again to summarise them so they'd make sense to people viewing them on ideascale.

#owotleaks #owot – we're building a tool that converts whiteboard brainstorming notes into fully developed applications
— Jack Dougherty (@DoughertyJack) July 29, 2013

So now it's over to you (briefly). We're working out what we should build this week, and in addition to your votes, we’d love you to comment on two specific things:

How would a suggested tool change your work?
Do you know of similar tools (we don’t want to replicate existing work)?

So go have a look at the candidate ideas at http://oneweekonetool.ideascale.com and let us know what you think. It's less about voting than it is about providing more context for ideas you like, and we'll put all the ideas through a reality check based on whether it has identifiable potential users and whether we can build it in a few days. We'll be heading out to lunch tomorrow (Viriginia time) with a decision, so it's a really short window for feedback: 10am American EST. (If it's any consolation, it's a super-short window for us building it too.)

Update Tuesday morning: two other participants have written posts, so go check them out! Amanda Visconti's Digital Projects from Start to Finish: DH Mentorship from One Week One Tool (OWOT), Brian Croxall's Day 1 of OWOT: Check Your Ego at the Door and Jack Dougherty's Learning Moments at One Week One Tool 2013, Day 1.

DHOxSS: 'From broadcast to collaboration: the challenges of public engagement in museums'

I'm just back from giving at a lightning talk for the Cultural Connections strand of the Digital.Humanities@Oxford Summer School 2013, and since the projector wasn't working to show my examples during my talk I thought I'd share my notes (below) and some quick highlights from the other presentations.

Mark Doffman said that it's important that academic work challenges and provokes, but make sure you get headlines for the right reasons, but not e.g. on how much the project costs. He concluded that impact is about provocation, not just getting people to say your work is wonderful.

Gurinder Punn of the university's Isis Innovation made the point that intellectual property and expertise can be transferred into businesses by consulting through your department or personally. (And it's not just for senior academics – one of the training sessions offered to PhD students at the Open University is 'commercialising your research').

Giles Bergel @ChapBookPro spoke on the Broadside Ballads Online (blog), explaining that folksong scholarship is often outside academia – there's a lot of vernacular scholarship and all sorts of domain specialists including musicians. They've considered crowdsourcing but want to be in a position to take the contributions as seriously as any print accession. They also have an image-match demonstrator from Oxford's Visual Geometry Group which can be used to find similar images on different ballad sheets.

Christian von Goldbeck-Stier offered some reflections on working with conductors as part of his research on Wagner. And perfectly for a summer's day:

Christian quotes Wilde on beauty: "one of the great facts of the world, like sunlight, or springtime…" http://t.co/8qGE9tLdBZ #dhoxss
— Pip Willcox (@pipwillcox) July 11, 2013

My talk notes: 'From broadcast to collaboration: the challenges of public engagement in museums'

I’m interested in academic engagement from two sides – for the past decade or so I was a museum technologist; now I’m a PhD student in the Department of History at the Open University, where I’m investigating the issues around academic and ‘amateur’ historians and scholarly crowdsourcing.

As I’ve moved into academia, I’ve discovered there’s often a disconnect between academia and museum practice (to take an example I know well), and that their different ways of working can make connecting difficult, even before they try to actually collaborate. But it’s worth it because the reward is more relevant, cutting-edge research that directly benefits practitioners in the relevant fields and has greater potential impact.

I tend to focus on engagement through participation and crowdsourcing, but engagement can be as simple as blogging about your work in accessible terms: sharing the questions that drive your research, how you’ve come to some answers, and what that means for the world at large; or writing answers to common questions from the public alongside journal articles.

Plan it

For a long time, museums worked with two publics: visitors and volunteers. They’d ask visitors what they thought in ‘have your say’ interactives, but to be honest, they often didn’t listen to the answers. They’d also work with volunteers but sometimes they valued their productivity more than they valued their own kinds of knowledge. But things are more positive these days – you've already heard a lot about crowdsourcing as a key example of more productive engagement.

Public engagement works better when it’s incorporated into a project from the start. Museums are exploring co-curation – working with the public to design exhibitions. Museums are recognising that they can’t know everything about a subject, and figuring out how to access knowledge ‘out there’ in the rest of the world. In the Oramics project at the Science Museum (e.g. Oramics to Electronica or Engaging enthusiasts online), electronic musicians were invited to co-curate an exhibition to help interpret an early electronic instrument for the public.

There’s a model from 'Public Participation in Scientific Research' (or 'citizen science') I find useful in my work when thinking about how much agency the public has in a project, and it's also useful for planning engagement projects. Where can you benefit from questions or contributions from the public, and how much control are you willing to give up?

Contributory projects designed by scientists, with participants involved primarily in collecting samples and recording data; Collaborative projects in which the public is also involved in analyzing data, refining project design, and disseminating findings; Co-created projects are designed by scientists and members of the public working together, and at least some of the public participants are involved in all aspects of the work. (Source: Public Participation in Scientific Research: Defining the Field and Assessing Its Potential for Informal Science Education (full report, PDF, 3 MB))

Do it

Museums have learnt that engaging the public means getting out of their venues (and their comfort zones). One example is Wikipedians-in-Residence, including working with Wikipedians to share images, hold events and contribute to articles. (e.g. The British Museum and Me, A Wikipedian-in-Residence at the British Museum, The Children's Museum's Wikipedian in Residence).

It’s not always straightforward – museums don’t do ‘neutral’ points of view, which is a key goal for Wikipedia. Museums are object-centric, Wikipedia is knowledge-centric. Museums are used to individual scholarship and institutional credentials, Wikipedia is consensus-driven and your only credentials are your editing history and your references. Museums are slowly learning to share authority, to trust the values of other platforms. You need to invest time to learn what drives the other groups, how to talk with them and you have to be open to being challenged.

Mean it

Done right, engagement should be transformative for all sides. According to the National Co-ordinating Centre for Public Engagement, engagement ‘is by definition a two-way process, involving interaction and listening, with the goal of generating mutual benefit.’ Saying something is ‘open to the public’ is easy; making efforts to make sure that it’s intellectually and practically accessible takes more effort; active outreach is a step beyond open. It's not the same as marketing – it may use the same social media channels, but it's a conversation, not a broadcast. It’s hard to fake being truly engaged (and it's rude) so you have to mean it – doing it cynically doesn't help anyone.

Asking people to do work that helps your mission is a double win. For example, Brooklyn Museum's 'Freeze Tag' ask members of their community to help moderate tags entered by people elsewhere – they're trusting members of the community to clean up content for them.

Enjoy it

My final example is the National Library of Ireland on Flickr Commons, who do a great job of engaging people in Irish history, partly through their enthusiasm for the subject and partly through the effort they put into collating comments and updating their records, showing how much they value contributions.

Almost by definition, any collaboration around engagement will be with people who are interested in your work, and they’ll bring new perspectives to it. You might end up working with international peers, academics from different disciplines, practitioner groups, scholarly amateurs or kids from the school down the road. And it’s not all online – running events is a great way to generate real impact and helps start conversations with potential for future collaboration.

You might benefit too! Talking about your research sometimes reminds you why you were originally interested in it… It’s a way of looking back and seeing how far you’ve come. It’s also just plain rewarding seeing people benefit from your research, so it's worth doing well.

—
Thanks again to Pip Willcox for the invitation to speak, and to the other speakers for their fascinating perspectives. Participation and engagement lessons from cultural heritage and academia is a bit of a hot topic at the moment – there's more on it (including notes from a related paper I gave with Helen Weinstein) at Participatory Practices.

'An (even briefer) history of open cultural data' at GLAM-Wiki 2013

These are some of my notes for my invited plenary talk at GLAM-Wiki 2013 (Galleries, Libraries, Archives, Museums & Wikimedia, #GLAMWiki), held at the British Library on April 12-13, 2013. I don't think I stuck that closely to them on the day, and in the interests of brevity I've left out the 'timeline' bits (but you can read about some of them in a related MuseumID article, 'Where next for open cultural data in museums?') to focus on the lessons to be learnt from changes so far. There were lots of great talks and discussion at the event, you can view some of the presentations on Wikimedia UK's YouTube channel.

A (now very) brief history of open cultural data

Firstly, thank you for the invitation to speak… This morning I want to highlight some key moments of change in the history of open cultural data – a history not only of licenses and data, but also of conversations, standards, and collaborations, of moments where things changed… I've included key moments from funders, legislative influences and the commercial sector too, as they create the context in which change happens and often have an effect on what's considered possible. I'll close by considering some of the lessons learnt.

[Please help improve this talk]

A caveat – there may well be a bias towards the English-speaking world (and to museums, because of my background). If you know of an open GLAM (gallery, library, archive, museum) data source I've missed, you can add it to the open cultural data/GLAM API wiki… or Lotte's Belice's list of open culture milestones timeline.

Definitions

'open cultural data' is data from cultural institutions that is made available for use in a machine-readable format under an open licence. But each word in open, cultural, data is slightly more complicated so I'll unpack them a little…

Open

Office clerks, FNV. Voorlichting.

While the degree of openness required to be 'open' data can be contentious, at its simplest, 'open' refers to content that is available for use outside the institution that created it, whether for school homework projects, academic monographs or mobile phone apps. 'Open' may refer to licences that clarify the permissions and restrictions placed on data, or to the use of non-proprietary digital technologies, or ideally, to a combination of both open licences and technologies.

Ideally, open data is freely available for use and redistribution by anyone for any purpose, but in reality there are often restrictions. GLAMs may limit commercial use by licensing content for 'non-commercial use only', but as there is no clear definition of 'non-commercial use' in Creative Commons licences, some developers may choose not to risk using a dataset with an unclear licence. GLAMs may also release data for commercial use but still require attribution, either to help retain the provenance of the content, to help people find their way to related content or just because they'd like some credit for their work. GLAMs might also release data under custom licences that deal with their specific circumstances, but they are then difficult to integrate with content from other openly-licensed datasets.

Hybrid licensing models are a pragmatic solution for the current environment. They at least allow some use and may contribute to greater use of open cultural data while other issues are being worked out. For example, some institutions in the UK are making lower resolutions images available for re-use under an open licence while reserving high resolution versions for commercial sales and licensing. Or they may differentiate between scholarly and commercial use, or use more restrictive licences for commercially valuable images and release everything else openly.

I think this type of access is better than nothing, particularly if organisations can learn from the experience and release more data next time. Because these hybrid models are often experimental, their reception is important, and it's helpful for GLAMs to be able to show they've had a positive impact and hopefully helped create relationships with groups like Wikipedia.

Cultural

Cultural data is data about objects, publications (such as books, pamphlets, posters or musical scores), archival material, etc, created and distributed by museums, libraries, archives and other organisations.

Data

It's a useful distinction to discuss early with other cultural heritage staff as it's easy to be talking at cross-purposes: data can refer to different types of content, from metadata or tombstone records (the basic titles, names, dates, places, materials, etc of a catalogue record), to entire collection records (including data such as researched and interpretive descriptions of objects, bibliographic data, related themes and narratives) to full digital surrogates of an object, document or book as images or transcribed text. Some organisations release open metadata, others release all their data including their images. If you can't do open data (full content or 'digital surrogates' like photographs or texts) then at least open up the metadata (data about the content) as e.g. CC0 and the rest with another licence. Releasing data may involve licensing images, offering downloads from catalogue sites; 'content donations', APIs and machine-facing interfaces; term lists, etc. Much of the data that isn't images isn't immediately interesting, and may be designed for inter-collections interoperability or mashups rather than media commons.

Why is open cultural data important?

Before I go on, why do we care? Open cultural data is the foundation on which many projects can be built. It helps achieve organisational goals, mission; can help increase engagement with content; can create 'network effect' with related institutions; can be re-used by people who share your goals around access to knowledge and information – people like Wikipedians.

Some key moments in open cultural data

Events I discussed included the founding of Wikimedia, Europeana and Flickr Commons, previous GLAM-Wiki conferences, changes in licences for art images, library catalogue records and museum content, GLAM APIs and linked data services and the launch of the Digital Public Library of America next week.

Lessons learnt

Many of the changes are the results of years of conversation and collaboration – change is slow but it does happen. GLAMs work through slow iterations – try something, and if no-one dies, they'll try something else. We are all ambassadors, and we are all translators, helping each domain understand the other.

Contradictory things GLAMs are told they must do

Give content away for the benefit of all
Monetise assets; protect against loss of potential income; protect against mis-use of collections; conserve collections in perpetuity; protect the IP of artists; demonstrate ROI on digitisation

It's not easy for GLAMs to release all their data under an entirely open licence, but they don't do it just to be annoying – it's important to understand some of the pressures they're under. For example, GLAMs usually need to be able to track uses of their data and content to show the impact of digitising and publishing content, so they prefer attribution licences.

The issue of potential lost income – imaginary money that could be made one day if circumstances change, or profit that someone else makes off their opened data – is particularly difficult as hard to deal with [and here I ad-libbed, saying that it was like worrying about failing to meet the love of your life because you got on a different tube carriage – you can't live your life chasing ghosts]. Ideally, open data needs to be understood as an input to the creative economy rather than an item on the balance sheet of an individual GLAM.

GLAMs worry about reputational damage, whether appearing on the front page of a tabloid newspaper for the 'wrong' reasons, questions being asked in Parliament, or critique from Wikipedians. Over time, their mindset is changing from keeping 'our data' to being holders, custodians of our shared heritage.

Conversations, communities, collaborations

Conversations matter… we're all working towards the same goal, but we have different types of anxieties and different problems we have to address.

GLAMs are about collections, knowledge, and audiences. Unlike most online work, they are used to seeing the excitement people experience walking through their door – help GLAMs understand what Wikipedians can do for different audiences by making those audience real to them. GLAMs are also used to being wined and dined before you lay the hard word on them. Just because you don't need to ask for permission to use content doesn't mean you shouldn't start a conversation with an organisation. There are lots of people with similar goals inside organisations, so try to find them and work with them. Trust is a currency, don't blow it!

Being truly collaborative sometimes means compromising (or picking your battles) and it definitely means practising empathy. Open data people could stop talking about open data as something you *do* to GLAMs, and GLAMs could stop thinking open data people just want to make your life difficult.

The role of higher powers

Government attitudes to open data make a big difference and they can also change the risks associated with publishing orphan works. Governments can also help GLAMs open up their content by indemnifying them against the chance that someone else will monetise their data – consider it not a failure of the GLAM but a contribution to the creative and digital economy.

Things that are better than a poke in the eye with a sharp stick

Kittens (and puppies)
Cultural data that's available online but isn't (yet) openly licensed
Cultural data online that is licensed for non-commercial use

Yes, the last two aren't ideal, but they are great deal better than nothing.

Into the future…

GLAMs and Wikipedians may move at different paces, and may have different priorities and different ways of viewing the world, but we're all working towards the same goals. Not everything is as open, but a lot more is open than it used to be. I sensed yesterday [the first day of the conference] that there are still some tensions between Wikimedians and GLAMers, moments when we need to take a deep breath and put empathy before a pithy put down, but I loved that Kat Walsh's welcome yesterday described how Wikipedia used to focus on how different from others but now focuses on reaching out to others and figuring out how we're the same.

GLAMs and Wikipedians have already used open cultural data to make the world a better place. Let's celebrate the progress we've made and keep working on that…

GLAM-WIKI 2013 Friday attendees photograph by Mike Peel (www.mikepeel.net).

Congratulations to everyone who helped make it a great event, but particularly to Daria Cybulska and Andrew Gray (@generalising) for making everything work so smoothly, and Liam Wyatt (@wittylama) for the original invitation to speak.

Notes from THATCamp Feminisms West #tcfw

I'm just back from ten days in the US where I attended two events, both closely related to digital history, feminist digital humanities and women's history (whether intellectual, science, education, etc related). I'm posting to mark the moment and to collect some links – I think I'm still digesting the many conversations and moments of insight.

THATCamp Feminisms West #tcfw

A THATCamp is a technology+humanities unconference, a format much loved in the digital humanities world. This one was conceived from a twitter conversation and organised by the wonderful Jacque Wernimont of Scripps College in Claremont, California for March 14-15. Two other THATCamp Feminisms were held simultaneously in the south and east. I was invited over to do a workshop, and thought 'data visualisation as a gateway to programming' would be useful – I prepared two exercises, one of which involved thinking about how to match visualisation types to the structure of the selected content in ManyEyes, while the other was more about learning about how code works by playing with a pre-coded (and heavily, chattily commented) working visualisation that used SIMILE's JavaScript libraries – 'view source' and save the file to your hard drive to get started. It was a good chance to talk about the issues that messy humanities data create for generic visualisation tools, the risks in the 'truthiness' of visualisations, the importance of thinking critically about algorithms and issues around primary sources and women's history, etc, with people who'd thought deeply about some of these issues and could make their own contributions to the workshop.

The day started with the #tooFEW Wikipedia editathon (storify of results), which gave everyone a chance to learn and try out something new before the THATCamp had even officially started. It was a nice way to ease into things and achieve something together before working out the THATCamp programme as a group.

Over the day and a half I went to sessions including Feminist digital pedagogy and Feminist Collaboration. After a week of further travel across the US and another conference, the sessions are blurring into one, but overall they were a great chance to think about what a feminist digital humanities might be like (see for example Transformative Digital Humanities projects or read Toward an Open Digital Humanities from an earlier THATCamp for things to move towards or be careful of), to ask questions like 'what would a feminist Digging into Data look like?', to ask 'does it matter if feminist projects are made with people who don't share their politics'? (Probably not, though academic work might be attractive to people who value work/life balance.) What's the right mix of openness and shared authority, how collaborative can a class be, and how can we help students fail safely in the cause of experimenting (especially when using public technologies like YouTube or Twitter)? It's important to remember that, as Alex Juhasz said, feminism is about process (or praxis), doing and making things, which in turn made me realise that one reason I value teaching coding is that it gives people DIY tools to make things that suit their own research needs and styles (see 'Why learning to code isn’t as important as learning to build something' but please also read Code: Craft and Culture and the comments below it). I also loved Alex's statement that she's 'less interested in feminism that starts from danger than feminism that starts from agency' and being fearless about taking up space.

The value of meeting in person was an underlying theme of the event, and eventually a conversation about Building a DH Regional Hub, and the difficulties in collaborating between institutions and organising in-person meetings with the huge geographic coverage of the Los Angeles area lead to the invention of Mindr: 'Grindr for travelling DHers – who's nearby and what do they want to chat about?', or as @laurenfklein described it, a 'geo-aware interface to DH Answers', an app that lets you know when someone with similar scholarly interests is nearby and might be up for a chat. I would *love* this to actually happen, and who knows, if someone is able to shepherd the enthusiasm for it, it might.

Beyond the value in the discussion, just being surrounded by people who were digitally savvy and were also aware of the effects of implicit biases and tech-as-a-meritocracy, the role of disciplinary gatekeepers, assumptions about gendered work, emotional labour and the pressure to be 'nice' as well as the peculiarities of academia was brilliant. It was also a bit intimidating at first as I don't feel hugely qualified to comment on feminist issues (it's a long time since I've been caught up on theory and 'feminism' online has probably made it sound scarier than it really is) unless conversation moved to 'women in tech' issues or I could contribute observations on my experience of academia and workplaces in the UK. Perhaps that's one reason I was encouraged by discussion about possible models of feminist scholarship and mentoring (including asking male allies for help) – I don't have to figure this out on my own. That said, as Anne Cong-Huyen said:

'At an event like this one, where we come together to address or at least share about gender and sexual equality in dh and the academy it leaves us to ask: Where does the burden of addressing that inequity fall? […] And how about those of us who are junior faculty, adjuncts, or graduate students (like myself) who have even less power within the academy?'

Or in Amanda Phillips' words:

In this way, THATCamp Feminisms felt a bit different than other THATCamps I’ve attended. The infectious enthusiasm of DH was tempered here by the political, professional, and market realities that disproportionately affect marginalized communities.

I think it's important that those realities are widely understood and shared, or some of the promise of the digital humanities will have failed to blossom. Creating space for those hard questions perhaps highlights how positive, supportive and constructive the environment at THATCamp Feminisms West was. I don't have a witty or concise conclusion, except to say that I met a bunch of amazing women and came away encouraged and inspired, and you should definitely go to a THATCamp Feminisms if you ever get a chance. Or run one yourself and see what happens. To quote Alex Juhasz again:

To me it is was less the DH, or even the digital, that made this conversation matter, but the feminist: because we shared values, the will and capacity to be critical as well as intellectual while being supportive and trying to distribute authority and voice around the room all the while working, quick.

New challenges in digital history: sharing women's history on Wikipedia – my talk notes

I'm at The Albert M. Greenfield Digital Center for the History of Women's Education at Bryn Mawr College for the inaugural Women's History in the Digital World Conference. Since I'm about to speak and ask historians to share their research and write history in public, I thought I should also be brave and share my draft talk notes (which I've now updated with formatted references, though Blogger is still re-formatting things slightly oddly).

Introduction: New challenges in digital history: sharing women's history on Wikipedia

[slide – title, my details]
Hi, I'm Mia. I'm actually doing a PhD on scholarly crowdsourcing, or collaboratively creating online resources, and, thinking about the impact of digitality on the practices of historians, so this paper is indirectly related to my research but isn't core to it.
I proposed this paper as a deliberate provocation: 'if we believe the subjects of our research are important, then we should ensure they are represented on freely available encyclopedic sites like Wikipedia'. Just in case you're not familiar with it, Wikipedia is a free online encyclopedia 'that anyone can edit.' It contains 25 million articles, over 4 million of them in English, but also in 285 other languages, and has 100,000 active contributors[1].

'Brilliant Women' at the National Portrait Gallery

The genesis of this paper was two-fold. The 2008 exhibition 'Brilliant Women: 18th Century Bluestockings' at the UK National Portrait Gallery, made the point that 'Despite the fact that 'bluestockings' made a substantial contribution to the creation and definition of national culture their intellectual participation and artistic interventions have largely been forgotten'. As a computer programmer, reinventing the wheel and other inefficient processes drive me crazy, and I began to think about how digital publishing could intervene in the cycle of remembering and forgetting that seemed to be the fate of brilliant women throughout history. How could historians use digital platforms to stop those histories being lost and to make them easy for others to find?

[Screenshot – Caitlin Moran quote from How to be a woman: 'Even the ardent feminist historian, male or female – citing Amazons and tribal matriarchies and Cleopatra – can't conceal that women have done basically f*ck-all for the last 100,000 years']
A few years later, by then a brand-new PhD student, I attended the Women's History Network conference in London in 2011 and learnt of so many interesting lives that challenged conventional mainstream historical narratives of gender. I wished that others could hear those stories too. But when I asked if any of these histories were available outside academia on sites like Wikipedia, there was a strong sense that editing Wikipedia was something that other people did. But who better to make a case for better representation of women's histories than the people in that room? Who else has the skills, knowledge and the passion? Some academic battles may have been won regarding the importance of women's histories, but representing women's histories on the sites where ordinary people start their queries is hugely important. The quote on this slide illustrates why – even if it was meant in jest, it represents a certain world view.

WikiWomen's Collaborative

[slide – logos from http://en.wikipedia.org/wiki/Wikipedia:WikiWomen%27s_History_Month http://meta.wikimedia.org/wiki/WikiWomen%27s_Collaborative ]
Of course, I'm not the first, and definitely not the most qualified to make this point. I would also like to acknowledge the work of many groups and individuals, particularly within Wikipedia, that's preceded this.[2]

[slide – Scripps editathon, #tooFEW]
Things move fast in the digital world and we're at a different moment than the one when I proposed this paper. Gender issues on Wikipedia had been discussed for a number of years but there's been a recent burst of activity, including the #tooFEW ('Feminists Engage Wikipedia') editathons – 'a scheduled time where people edit Wikipedia together, whether offline, online, or a mix of both' – [3], held online and in person across four physical sites.[4] [5] I was going to be provocative and ask you to create Wikipedia entries about the histories you've invested so much in researching, but some of that is happening already. As a result, this is version 2 of this paper, but my starting question remains the same – assuming we believe that women's history is important, what's wrong with our current methods of research dissemination and dialogue?

The case of the Invisible Scholarship

[slide – outline of section]
Cumulative centuries of archival and theoretical work have been spent recovering women's histories, yet much of this inspiring scholarship might as well not exist when so few people have access to it. Sadly, it's currently the case that scholarship that isn't deliberately made public is invisible outside academia. The open access movement, with all its thorny complications, is one potential solution. Engaging in new forms of open scholarship and disseminating research on sites where the public already goes to learn about history is another.

If it's not Googleable, it doesn't exist.

[slide – screenshot of unsuccessful search for Ina von Grumbkow]
Most content searches start and end online. The content and links available to search engines inform their assumptions about the world, and they in turn shape the world view presented on the results screen. If the name of a historical figure doesn't show up in Google, how else would someone find out about them? While college students might be heavy users of Google's specialist Google Scholar search, it's unlikely that people would come across it accidentally, not least because there's a 'semantic gap' between the language used in academia and the language used in everyday speech. Writing for Wikipedia means writing in everyday language, and the site is heavily indexed by search engines – it doesn't take long for content created on Wikipedia – even on a user's talk page and not the main site – to show up in Google results. So one reason to take history on Wikipedia seriously is that it affects what search engines know about the world.

'Did you mean… hegemony?'

Search for 'Viscountess Ranelagh', Google says 'Did you mean Viscount'. No.

[slide – screenshot of search for 'Viscountess Ranelagh and the Authorisation of Women's Knowledge in the Hartlib Circle', Google says 'Did you mean Viscount'. No.]
Scholarship and sources contained in specialist online archives and repositories are often off-limits to the Google bots that crawl the web looking for content to index. Because search engines normalise certain assumptions about the world, getting more content about women's histories in publically accessible spaces will eventually have an effect in the algorithms that determine suggestions for 'did you mean' etc. Contributions to sites like Wikipedia can eventually become contributions to the 'knowledge graphs' that determine the answers to questions we ask online.

If it's behind a paywall, it only exists for a privileged few

[Slide – Screenshot of blocked attempt to access 'Wives and daughters of early Berlin geoscientists and their work behind the scenes']
Specialist users will be able to find academic research via Google Scholar, but any independent scholars in attendance will be able to speak to the difficulties in gaining access to journal articles without membership of an institutional library. Journal articles obviously have a lot of value within academic communities, but the research they represent is only available to a privileged few.

Why does Wikipedia matter?

[slide: For some, Wikipedia is the font of all wisdom]
Wikipedia is one of the most visited websites in the world. As one commentator said, 'people turn to Wikipedia as an objective resource' but ' it's not so objective in many ways.'[6]

However, as the free online encyclopedia 'that anyone can edit', it also provides the ability to take direct action to fix the under-representation of women's history. President of the AHA, William Cronon said, 'Wikipedia provides an online home for people interested in histories long marginalized by the traditional academy'[7] – this may not be entirely true yet, but we can hope.

Wikipedia is not yet encyclopedic

[Slide – Ina screenshot]
The English version of Wikipedia has over 4 million articles but it still has some way to go to become truly encyclopedic. Martha Saxton has noted the absence of women's history content on Wikipedia and was distressed by 'its superficiality and inaccuracies when present [8]'. Just as female assistants, secretaries, collectors, illustrators, correspondents, translators, salonists, cataloguers, text book writers, popularisers, explorers, pioneers and colleagues have been left out of traditional academic histories and gradually reclaimed by historians, they are often still invisible on Wikipedia. This may be partly because not enough women edit Wikipedia – as Wikipedia User Gobonobo says, 'editors often contribute to topics they are familiar with and that concern them […] This systemic bias has the potential to exacerbate an historical record that already gives undue emphasis to men.' [9]

The under-representation of women's history undermines Wikipedia's claim to be encyclopedic. Issues include missing entries or omissions in coverage for existing topics, entries with inaccurate content, a failure to represent a truly 'neutral point of view', and a representation of 'male' as the default gender.

Many notable women have been buried in pages titled for their husbands, brothers, tutors, etc. In 1908 Ina von Grumbkow undertook an expedition to Iceland. She later made significant contributions to the field of natural history and wrote several books but other than passing references online and a mention on her husband's Wikipedia page, her story is only available to those with access to sources like the ' Earth Sciences History' journal[10][11].

[Slide: 'Main articles: List of Fellows of the Royal Society and List of female Fellows of the Royal Society '.]
Some of the categories used in Wikipedia posit the default gender as male. For example, there's a ' List of Fellows of the Royal Society ' and ' List of female Fellows of the Royal Society'.

Wikipedia and the challenges of digital history

Writing for Wikipedia encapsulates many, but not all, of the challenges of digital history.

New forms of writing

Writing for Wikipedia calls upon historians to write engaging, intellectually accessible, succinct text that still accurately represents its subject. It not only means valuing the work and skills in writing public history, it requires the ability to write history in public.

Writing for a 'neutral point of view' – one of the key values of Wikipedia – is challenging for historians. Many may find difficult to believe that it's even possible, and it's difficult to achieve [12].

Unlike traditional historical scholarship, characterised by 'possessive individualism' [13] and honed to perfection before publication, Wikipedia entries are considered a work in progress, and anyone who spots an issue is asked to fix it themselves or flag it for others to review.

It won't advance your career

While it might have a large public impact, editing Wikipedia is work that isn't credited in academia, and it takes time that could be used for projects that would count for career advancement. More importantly from Wikipedia's point of view, you can't promote your own work on the site, so writing about your own research interests is not straightforward if not many people have published in your area of expertise.

“On the internet, nobody knows you're a professor”

In a comment with 'pointers for academics who would like to contribute to Wikipedia' on a Chronicle article, commentator 'operalala' said, '"On the internet nobody knows you're a professor." If you're used to deferential treatment at your home institution, you'll be treated like everybody else in the Wide Open Internet.'[14] Or in William Cronon's words, you must 'give up the comfort of credentialed expertise'.[15] Anyone can edit, re-shape or even delete your work.

Just like academia, Wikipedia has ways of establishing the credibility and reputation of a contributor, and just like any other community, there are etiquettes and conventions to observe. As newcomers to the community, Claire Potter warns that it's important not to think of Wikipedia as 'another realm for intellectuals to colonize and professionalize'.[16]

The opportunities and challenges of women's history as public history on Wikipedia

Opportunities

#WomenSciWP editathon at the Royal Society

Wikipedia uses red links to represent entries that could be created but don't yet exist. Women's history editathons often create lists of red-linked names as suggested topics that could be created [17] . Projects on and outside Wikipedia, and events at institutions like the Smithsonian and Royal Society and just last weekend at three THATCamps across the United States might be part of a critical mass of people learning how to edit Wikipedia to better include women's history.

Compared to the lengthy process of writing for academic publication, a new Wikipedia entry can be created in a few hours, allowing for time to structure the content and format the references as necessary to pass the first quality bar. An existing entry can be corrected in minutes. Each editathon or personal edit improves the representation of women's history, and there's something very satisfying about turning red links blue.

Ina von Grumbkow's name red-linked on her husband's Wikipedia page

Adding the brackets that turn a piece of text into a red link, suggesting the possibility of an entry to be created is a small but potentially powerful intervention. Red links can render the gaps and silences visible.

Resistance

Creating or editing entries on women's history may be relatively easy, but making sure they stay there is less so. There are countless examples of women having to fight to keep changes in as other editors revert them, argue about their choice of sources, the significance or notability of their topic. Wikipedians are zealous in preventing spammers and crackpots polluting the quality of the site, which explains some of the rapid 'nominations for deletion', but some pockets of the site are also hostile to women's history or to women themselves.

Saxton said editing Wikipedia is 'not for the faint of heart' and 'a lesson in how little women's history has penetrated mainstream culture'. There's work to be done in sharing and normalising an understanding of the historical circumstances and cultural contexts that created difficulties for women. We might know that, as Janet Abbate said, 'The laws and social conventions of a given time and place strongly shape the kinds of technical training available to women and men, the career options open to them, their opportunities for advancement and recognition' [18] but until other Wikipedians understand that, there will continue to be issues around 'notability'. Having those conversations as many times as necessary might be tiring and uncomfortable or even controversial, but it's part of the work of representing women's history on Wikipedia.

Tensions

'Reliable sources'

Wikipedians may have different definitions of 'reliable sources' than scholarly researchers. As one academic discovered:
"Wikipedia is not 'truth,' Wikipedia is 'verifiability' of reliable sources. Hence, if most secondary sources which are taken as reliable happen to repeat a flawed account or description of something, Wikipedia will echo that."' [19]

The same gatekeepers matter

As some academics have found, 'Wikipedia differs from primary-source research, from scholarly writing, and how it privileges existing rather than new knowledge' [20] [21] Wikipedia is not the place to redress fundamental issues with silences in the archives or in the profession overall, not least because on Wikipedia, primary research is bad and secondary sources are good [22] . This puts the onus back on to traditional academic publishing in peer-reviewed journals and books that can be cited in Wikipedia articles, though other published works such as 'credible and authoritative books' and 'reputable media sources' can also be cited.

'Notability'

'A person is presumed to be notable if he or she has received significant coverage in reliable secondary sources that are independent of the subject. […] the person who is the topic of a biographical article should be "worthy of notice" – that is, "significant, interesting, or unusual enough to deserve attention or to be recorded" within Wikipedia as a written account of that person's life.' [23] 'The common theme in the notability guidelines is that there must be verifiable, objective evidence that the subject has received significant attention from independent sources to support a claim of notability.' [24] This creates obvious difficulties for some women's histories.

It's also difficult to judge where 'notability' should end. When does focusing on exceptional women become counter-productive? When do we risk creating a new canon? When does it stop being remarkable that a woman became prominent in a field and start being more accepted, if still not expected? [25] At what point should writing shift from individual entries to integration into more general topics?

Conclusion

Sometimes it's hard to tell whether Wikipedia lags behind academia's acceptance and general integration of women's history into mainstream history or whether it is representative of the field's more conservative corners. Recent digital history projects are doing a good job in explaining some of the issues with key sources for Wikipedia like the Oxford Dictionary of National Biography [26] , and I'd hope that this continues. As Martha Saxton said, 'integrating women's experience into broad subjects' is 'both more challenging intellectually and ultimately, more to the point of the overall project of bringing women into our acknowledged history'. [27]

But it's also clearly up to us to make a difference. If it's worth researching the life and achievements of a notable woman, it's worth making sure their contribution to history is available to the world while improving the quality of the world's biggest encyclopaedia. And it doesn't mean going it alone. It's still just Women's History Month so it's not too late to sign up and join one of the women's history projects, or to plan something with your students. [28] [29] [30]

I'd like to close with quotes from two different women. Executive Director of the Wikimedia Foundation, Sue Gardner: 'Wikipedia will only contain 'the sum of all human knowledge' if its editors are as diverse as the population itself: you can help make that happen. And I can't think of anything more important to do, than that.' [31]

And to quote Laura Mandell's keynote yesterday: 'Let's write and publish about each other's projects so that future historians will have those sources to write about. … Nothing changes through thinking alone, only through massive amounts of re-iteration'. [32]

[Update: based on questions afterwards, you may want to get started with Wikipedia:How to run an edit-a-thon, or sign up and say hello at Wikipedia:WikiProject Women's History. You could also join in the Global Women Wikipedia Write-In #GWWI on April 26 (1-3pm, US EST), and they have a handy page on How to Create Wikipedia Entries that Will Stick.

And update April 30, 2013: check out 'Learning to work with Wikipedia – New Pages Patrol and how to create new Wikipedia articles that will stick' by the excellent Adrianne Wadewitz.

Update, June 9: if you're thinking of setting a class assignment involving editing Wikipedia, check out their 'For educators' and 'Assignment Design' pages for tips and contact points. June 18: see also Nicole Beale's 'Wikipedia for Regional Museums'.

Update, August 21, 2013: content on Wikipedia appears to have had an additional boost in Google's search results, making it even more important in shaping the world's knowledge. More at 'The Day the Knowledge Graph Exploded'.

New link, February 2014: Jacqueline Wernimont's Notes for #tooFEW Edit a thon based on a training session by Adrianne Wadewitz are a useful basic introduction to editing.]

References

[1] Various. ‘Wikipedia’. 2013. Wikipedia. http://en.wikipedia.org/wiki/Wikipedia.

[2] See for example http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Women%27s_History http://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Feminism http://en.wikipedia.org/wiki/Wikipedia:Meetup/DC_30

[3] https://en.wikipedia.org/wiki/Wikipedia:How_to_run_an_edit-a-thon

[4] http://en.wikipedia.org/wiki/Wikipedia:Meetup/Feminists_Engage_Wikipedia

[5] Barnett, Fiona. 2013. ‘#tooFEW – Feminists Engage Wikipedia’. HASTAC. March 11. http://hastac.org/blogs/fionab/2013/03/11/toofew-feminists-engage-wikipedia.

[6] Gobry, Pascal-Emmanuel. 2011. ‘Wikipedia Is Hampered By Its Huge Gender Gap’. Business Insider. January 31. http://www.businessinsider.com/wikipedia-is-hampered-by-its-huge-gender-gap-2011-1#.

[7] Cronon, William. 2012. ‘Scholarly Authority in a Wikified World’. Perspectives on History, American Historical Association. February 7. http://www.historians.org/perspectives/issues/2012/1202/Scholarly-Authority-in-a-Wikified-World.cfm.

[8] Saxton, Martha. 2012. ‘Wikipedia and Women’s History: A Classroom Experience’. Writing History in the Digital Age. http://writinghistory.trincoll.edu/crowdsourcing/saxton-etal-2012-spring/.

[9] Gobonobo. 2013. ‘User:Gobonobo/Gender Gap Red List’. Wikipedia. https://en.wikipedia.org/wiki/User:Gobonobo/Gender_Gap_red_list

[10] Various.. ‘Hans Reck’. Wikipedia. https://en.wikipedia.org/wiki/Hans_Reck

[11] Mohr, B. A. R. 2010. Wives and daughters of early Berlin geoscientists and their work behind the scenes. Earth Sciences History 29 (2): 291–310.

[12] As commenter Operalala suggested, one challenge is recognising ‘the difference between the plurality of academia and the singularity of a Wikipedia article’. Comment http://chronicle.com/article/The-Undue-Weight-of-Truth-on/130704/#comment-437781354 on Messer-Kruse, Timothy. 2012. ‘The “Undue Weight” of Truth on Wikipedia’. The Chronicle of Higher Education. February 12. http://chronicle.com/article/The-Undue-Weight-of-Truth-on/130704/.

[13] Rosenzweig, Roy. 2006. ‘Can History Be Open Source? Wikipedia and the Future of the Past’. The Journal of American History 93 (1) (June): 117–46. https://chnm.gmu.edu/essays-on-history-new-media/essays/?essayid=42

[14] Operalala on Messer-Kruse, 2012 [15] Cronon, 2012.

[16] Potter, Claire. 2013. ‘Looking for the Women on Wikipedia: Readers Respond’. The Chronicle of Higher Education. March 14. http://chronicle.com/blognetwork/tenuredradical/2013/03/looking-for-the-women-on-wikipedia-readers-respond/

[17] For example, https://en.wikipedia.org/wiki/User:Gobonobo/Gender_Gap_red_list https://en.wikipedia.org/wiki/User:T._Anthony/Women_in_Red https://en.wikipedia.org/wiki/User:Dsp13/Redlinks/Women

[18] Janet Abbate, "Guest Editor's Introduction: Women and Gender in the History of Computing," IEEE Annals of the History of Computing, vol. 25, no. 4, pp. 4-8, October-December, 2003

[19] Messer-Kruse, 2012.

[20] Anderson, Jill. 2013. ‘A Supposedly Fun Thing I’ll (Probably) Never Do Again’. True Stories Backward. http://girlhistorian.wordpress.com/2013/03/16/a-supposedly-fun-thing-ill-probably-never-do-again/

[21] Messer-Kruse, 2012.

[22] Various. 2013. ‘Wikipedia:No Original Research’. Wikipedia. https://en.wikipedia.org/wiki/Wikipedia:No_original_research

[23] Various. 2013. ‘Wikipedia:Notability (people)’. Wikipedia. http://en.wikipedia.org/wiki/Wikipedia:Notability_(people)

[24] Various. 2013. ‘Wikipedia:Notability’. Wikipedia. https://en.wikipedia.org/wiki/Wikipedia:NOTE
[25] Or as Christie Aschwanden says when proposing the 'Finkbeiner test' for contemporary journalism about women in science, 'treating female scientists as special cases only perpetuates the idea that there’s something extraordinary about a woman doing science'. Aschwanden, Christie. 2013. ‘The Finkbeiner Test’. Double X Science. March 5. http://www.doublexscience.org/the-finkbeiner-test/

[26] For a recent example, see ‘An Entry of One’s Own, or Why Are There So Few Women In the Early Modern Social Network?’ 2013. Six Degrees of Francis Bacon. March 8. http://sixdegreesoffrancisbacon.com/post/44879380376/an-entry-of-ones-own-or-why-are-there-so-few-women-in and ‘Gender and Name Recognition’. 2013. Six Degrees of Francis Bacon. March 20. http://sixdegreesoffrancisbacon.com/post/45833622936/gender-and-name-recognition

[27] Saxton, 2012

[28] http://en.wikipedia.org/wiki/Wikipedia:WikiWomen%27s_History_Month

[29] Potter, Claire. 2013. ‘Prikipedia? Or, Looking for the Women on Wikipedia’. The Chronicle of Higher Education. March 10. http://chronicle.com/blognetwork/tenuredradical/2013/03/prikipedia-looking-for-the-women-on-wikipedia/
[30] For advice, see: Wikimedia Outreach. 2013. ‘Education Portal/Tips and Resources’. Wikipedia Outreach Wiki. http://outreach.wikimedia.org/wiki/Education_Portal/Tips_and_Resources
[31] A comment on Gardner, Sue. 2010. ‘Unlocking the Clubhouse: Five Ways to Encourage Women to Edit Wikipedia’. Sue Gardner’s Blog. November 14. http://suegardner.org/2010/11/14/unlocking-the-clubhouse-five-ways-to-encourage-women-to-edit-wikipedia/
[32] Mandell, Laura. 2013. "Feminist Critique vs. Feminist Production in Digital Humanities." Keynote presented at the Women’s History in the Digital World conference, Bryn Mawr College, Pennsylvania March 22 2013

If an app is the answer…

…what was the question?* And seriously, what questions should museums ask before investing in a mobile or tablet app?

First, some background. In We’re not ‘appy. Not ‘appy at all., Tom Loosemore of the Government Digital Service (GDS) gives examples of the increases in mobile traffic to UK government sites, including up to 60% mobile visits to site with complex transactions like booking driving tests.

For a cultural heritage perspective: as part of the Culture24 Let's Get Real project, I looked at the percentage of mobile visits (and visitors) to 22 cultural websites for Jan 1, 2012 – September 2, 2012 (an extended time to try and reduce the effect of the Olympics) and found that on average, museums and arts organisations were already seeing an average of 20% mobile visits. I also reported the percentage change from the same period last year so that people could get a sense of the velocity of change: on average there was a 170% increase in mobile visits to cultural websites compared to the same period in 2011.

We'll re-run the stats when writing the final report in July, but in the meantime, there's a recent significant increase in web traffic from tablet devices to take into account. In BBC iPlayer: tablet viewing requests nearly double in two months the Guardian reported BBC figures:

"Tablets' share of total iPlayer requests grew from just 6% (TV only: 7%) in January 2012 to 10% (12%) in November and 15% (18%) last month. Smartphone requests have seen similar growth from 6% (TV only: 6%) of the total a year ago to 16% (18%) in January. [… ]A spokesman said it is thought the rise of the "phablet" – smartphones that are almost as big as a tablet, such as the Samsung Note – that have driven the surge."

Some museums are reporting seeing 40-50% increases in tablet traffic in the past few months. So, given all that, are apps the answer? Over to Loosemore:

"Our position is that native apps are rarely justified. […] Apps may be transforming gaming and social media, but for utility public services, the ‘making your website adapt really effectively to a range of devices’ approach is currently the better strategy. It allows you to iterate your services much more quickly, minimises any market impact and is far cheaper to support."

Obviously there are exceptions for apps that meet particular needs or genres, but this stance is part of their Government Digital Strategy:

"Stand-alone mobile apps will only be considered once the core web service works well on mobile devices, and if specifically agreed with the Cabinet Office."

So if your cultural organisation is considering an app, perhaps you should consider the questions the GDS poses before asking for an exemption to the requirement to just build a responsive website:

Is our web service already designed to be responsive to different screen sizes? If not, why not?
What is the user need that only a native/hybrid app can meet?
Are there existing native/hybrid apps which already meet this user need?
Is our service available to 3rd parties via an API or open data? If not, why not?
Does meeting this need justify the lifetime cost of a native or hybrid app?

What questions should we add for cultural heritage, arts and educational organisations? (My pet hate: are you creating amazing content that's only accessible to people with the right device?) And since I know I'm being deliberately provocative – what exceptions should be allowed? What apps have you seen that could only work as an app with current technology?

* I can't claim credit for the challenge 'if an app is the answer, what was the question', it's been floating around for a while now and possibly originated at a Let's Get Real workshop or conference.

Museum technologists redux: it's not about us

Recently there's been a burst of re-energised conversations on Twitter, blogs and inevitably at MW2012 (Museums on the Web 2012) about museum technologists, about breaking out of the bubble, about digital strategies vs plain old strategies for museums. This is a quick post (because I only ever post when I should be writing a different paper) to make sure my position is clear.

If you're reading this you probably know that these are important issues to discuss, and it's exciting thinking about the organisational change issues museums will rise to in order to stay relevant, but it's also important to step back and remind ourselves that ultimately, it's not about us. It's not about our role as museum technologists, or museums as organisations.

Museum technologists should be advocates for the digital audience, and guide museums in creating integrated, meaningful experiences, but we should also make sure that other museum staff know we still share their values and respect their expertise, and dispel myths about being zealots of openness at the expense of other requirements or wanting to devalue the physical experience.

It's about valuing the digital experiences our audiences have in our galleries, online and on the devices they carry in their pockets. It's about understanding that online visitors are real visitors too. It's about helping people make the most of their physical experiences by extending and enhancing their understandings of our collections and the world that shaped them. It's about showing the difference digital makes by showing the impact it can have for a museum seeking to fulfil its mission for audiences it can't see as well as those right under its nose.

I'm a museum technologist, but maybe in my excitement about its potential I haven't been clear enough: I'm not in love with technology, I'm in love with what it enables – better museums, and better museum experiences.

Geek for a week: residency at the Powerhouse Museum

I've spent the last week as 'geek-in-residence' with the Digital, Social and Emerging Technologies team at the Powerhouse Museum. I wasn't sure what 'geek-in-residence' would mean in reality, but in this case it turned out to be a week of creativity, interesting constraints and rapid, iterative design.

When I arrived on Monday morning, I had no idea what I'd be working on, let alone how it would all work. By the end of the first day I knew how I'd be working, but not exactly what I'd focus on. I came in with fresh questions on Tuesday, and was sketching ideas by lunchtime. The next few days were spent getting stuck into wireframes to focus in on specific issues within that problem space; I turned initial ideas into wireframes and basic copy; and put that through two rounds of quick-and-dirty testing with members of the public and Powerhouse volunteers. By the time I left on Friday I was able to handover wireframes for a site called 'conversations about collections' which aims to record people's memories of items from the collection. (I ran out of time to document the technical aspects of how the site could be built in WordPress, but given the skills of the team I think they'll cope.)

The first day and a half were about finding the right-sized problem. In conversations with Paula (Manager of the Visual & Digitisation services team) and Luke (Web Manager), we discussed what each of us were interested in exploring, looking for the intersection between what was possible in the time and with the material to hand.

After those first conversations, I went back to Powerhouse's strategy document for inspiration. If in doubt, go back to the mission! I was looking for a tie-in with their goals – luckily their plan made it easy to see where things might fit. Their strategy talked about ideas and technology that have changed our world and stories of people who create and inspire them, about being open to 'rich engagement, to new conversations about the collections'.

I also considered what could be supported by the existing API, what kinds of activities worked well with their collections and what could be usefully built and tested as paper or on-screen prototypes. Like many large collections, most of the objects lack the types of data that supports deeper engagement for non-experts (though the significance statements that exist are lovely).

Two threads emerged from the conversations: bringing social media conversations and activity back into the online collections interfaces to help provide an information scent for users of the site; and crowdsourcing games based around enhancing the collections data.
The first was an approach to the difficulties in surfacing the interesting objects in very large collections. Could you create a 'heat map' based on online activity about objects to help searchers and browsers spot objects that might be more interesting?

At one point Nico (Senior Producer) and I had a look at Google Analytics to see what social media sites were sending traffic to the collections and suss out how much data could be gleaned. Collection objects are already showing up on Pinterest, and I had wild thoughts about screen-scraping Pinterest (they have no API) to display related boards on the OPAC search results or object pages…

I also thought about building a crowdsourcing game that would use expert knowledge to data to make better games possible for the general public – this would be an interesting challenge, as open-ended activities are harder to score automatically so you need to design meaningful rewards and ensure an audience to help provide them. However, it was probably a bigger task than I had time for, especially with most of the team already busy on other tasks, though I've been interested in that kind of dual-phased project since my MSc project on crowdsourcing games for museums.

But in the end, I went back to two questions: what information is needed about the collections, what's the best way to get it? We decided to focus on conversations, stories and clues about objects in the collections with a site aimed at collecting 'living memories' about objects by asking people what they remember about an object and how they'd explain it to a kid. The name, 'Conversations about collections' came directly from the strategy doc and was just too neat a description to pass up, though 'memory bank' was another contender.
I ended up with five wireframes (clickable PDF at that link) to cover the main tasks of the site: to persuade people (particularly older people) that their memories are worth sharing, and to get the right object in front of the right person. Explaining more about the designs would be a whole other blog post, but in the interests of getting this post out I'll save that for another day… I'm dashing out this post before I head out, but I'll update in response to questions (and generally things out when I have more time).

My week at the Powerhouse was a brilliant chance to think through the differences between history of science/social history objects and art objects, and between history and art museums, but that's for another post (perhaps when if I ever get around to posting my notes from the MCN session on a similar topic).

It also helped me reflect on my interests, which I would summarise as 'meaningful audience participation' – activities that are engaging and meaningful for the audience and also add value for the museum, activities that actually change the museum in some way (hopefully for the better!), whether that's through crowdsourcing, co-curation or other types of engagement.

Finally, I owe particular thanks to Paula Bray and Luke Dearnley for running with Seb Chan's original suggestion and for their time and contributions to shaping the project; to Nicolaas Earnshaw for wireframe work and Suse Cairns for going out testing on the gallery floor with me; and to Dan Collins, Estee Wah, Geoff Barker and everyone else in the office and on various tours for welcoming me into their space and their conversations.

Photo: behind the scenes at the (then) Powerhouse Museum, Sydney

Report from 'What's the point of a museum website' at MCN2011

A really belated report from the 'What's the point of a museum website?' panel I was part of with Koven Smith (@5easypieces), Eric Johnson (@ericdmj), Nate Solas (@homebrewer) and Suse Cairns (@shineslike) at last November's Museum Computer Network (MCN2011) conference. I've written up some of my own thoughts at Brochureware, aggregators and the messy middle: what's the point of a museum website? – this post is about the discussion during the panel itself. There was a lot of audience participation (in the room and on twitter), which made tackling a summary of the discussion really daunting, so I've given up on trying to capture every thread of conversation and am just reporting from the notes I took at the time.

It's all bit of a blur now so it's hard to remember exactly how the conversations went, but from my notes at the time, it included: Clay Shirky on social objects as a platform for conversation; games and other online experiences as big draws for museum sites (trusted content is a boon for parents); the impact of social media making the conversations people have always had about exhibitions and objects visible to curators and others; and the charisma of the physical object. From the audience Robin White Owen mentioned the potential for mobile apps to create space, opportunity for absorption and intimate experiences with museum content, leading me to wonder if you can have a Stendhal moment online?

Is discoverability is the new authority for museum websites? As Nate said, authority online lies in being active online, though we also need to differentiate between authority about objects and narratives, and cite our sources for statements about online collections. (See also Rob Stein on the difference between being authoritarian and authoritative). But maybe that's challenging too – perhaps museums aren't good at saying there is no right answer because we like to be the one with the right answer. Someone mentioned 'communities of passion' gathered around specific objects, which is a lovely phrase and I'm sorry I can't remember who said it. Someone else from the audience wisely said, it's 'not how do I drive people to my collection, but how do I drive my collection to them'. Andrew Lewis talked about 'that inspiration moment' triggered in a museum that sends you hurrying back home to make art or craft something.

I talked about my dream of building a site that people would lose themselves in for hours, just as you can do on Wikipedia now after starting with one small query. How can we build a collections online site where people can follow one interesting-looking object or story after another? We can't do that without a critical mass of content, and I suspect this can only be created by bringing different museum collections together digitally (or as Koven called it, digital repatriation), which also gets around the random accidents of collecting history that mean related objects are isolated in museums and galleries around the world. Also, we're only ever part of the audience's session online – we might be the start, or the end, but we're more likely to be somewhere in the middle. We should be good team players and use our expert knowledge to help people find the best information they can.

Looking back, a lot of the conversation appears to be about how to create the type of rich experience of being in the presence of an object – a moment in time as well as in space – from the currently flat experience of looking at an object in an online catalogue (particularly when the online environment has all the distractions of kitten videos and social media notifications). Can storytelling or bite-sized bits of content about objects act as 'hooks' to enable reflection and learning online? Hugh Wallace has used the phrase 'snackable content' for readily available content that fits into how people use technology, and I think (with my conversational, social history bias) that stories-as-anecdotes can be a great way of sharing information about collections while creating that self-contained moment in time. (And yes, I am side-stepping Walter Benjamin's statement that 'that which withers in the age of mechanical reproduction is the aura of the work of art'. Not that he was in the room, but he does tend to haunt these conversations.)

As with many conversations about online visitors, the gap between what we know and what we should know is frustratingly large, and we still don't know how large the gap between what (particularly) collections online are and what they could be. Someone said that we're (measuring, or talking about) what users currently do with what we give them, not what they really want to do. Bruce Wyman tweeted, 'current visitors most frequently give *incremental* ideas. You need different folk to take those great leaps forward. That's us'. Rob Stein said he didn't care about measuring time online, but wanted to be able to measure epiphanies – an excellently provocative statement that generated lots of discussion, including comments that epiphany needs agency, discourse, and serendipity. Eric said we murder epiphany by providing too much information, but others pointed out that epiphanies are closely tied to learning, so maybe it's a matter of the right information at the right time for the right person and a good dose of luck.

So (IMO) it was a great panel session, but did we come up with an answer for 'what's the point of a museum website'? Probably not, but it's clearly a discussion worth having, and I dare say there were a few personal epiphanies during the session.

I'm collecting other posts about the session and will update this as I find them (or let me know of them in the comments): Suse's Initial takeaways from MCN2011. I also collated some of the tweets that used the session hashtag 'wpmw' in a document available (for now) via my dropbox.

Finally, thank you to everyone who attended or followed via twitter, and particular thanks to my fellow panelists for a great discussion.