JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for MCG Archives


MCG Archives

MCG Archives


MCG@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MCG Home

MCG Home

MCG  August 2014

MCG August 2014

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Crowd sourcing: platforms, methodologies, business cases

From:

Stephen McConnachie <[log in to unmask]>

Reply-To:

Museums Computer Group <[log in to unmask]>

Date:

Thu, 14 Aug 2014 09:23:32 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (172 lines)

Thanks very much everyone for really helpful responses. 

Mia I would love to see the crowdsourcing design slides, yes please. Are they on slideshare?

I saw Waisda presented at (I think) the FIAT Metadata Seminar in Hilversum last year, really exciting of course, and in fact Johan Oomen has been in touch so I'm going to follow up with him.

Some slides from the FIAT event:
http://www.slideshare.net/mobile/beheerderbeeldengeluid

At that event I also saw Yves Raimond (then BBC R&D) talk about the World Service speech to text followed by Crowdsourcing initiative, ie:
http://www.bbc.co.uk/blogs/legacy/researchanddevelopment/2012/03/automatically-tagging-the-worl.shtml

That really struck a chord, and in fact I'm hoping to work with project Comma, which is emerging from that R&D work with the aim of generating a platform for cloud processing of media, eg metadata creation by automation models:
http://www.bbc.co.uk/rd/projects/comma

Anyway, thanks again MCG. I'll be following up individually too.

All the best
Stephen

Sent from my iPad

> On 28 Jul 2014, at 16:23, Mia <[log in to unmask]> wrote:
> 
> Hi Stephen,
> 
> if I may answer your questions with a few more questions and a bit of a
> brain dump...
> 
> What kinds of data are you looking to get back from the process? And who
> will be using that data, and for what purposes? Once you've got a firm list
> of data you could get back, you can think about designing different tasks
> for the different audiences that would be interested in helping with that,
> and think about platforms from there. Personally, gathering permanently
> useful knowledge seems like a more meaningful (and thus more engaging) goal
> than creating busy work generating data with uncertain value.
> 
> And to approach it from the other side, what kinds of information about
> your collections do your passionate audiences and communities already share
> with you? How do they use the collections, and where do they discuss them?
> The Zooniverse project proposals form e.g.
> http://conscicom.org/proposals/form/ also has useful prompts about what
> kinds of community outreach you can support.
> 
> I've reviewed a couple of hundred crowdsourcing projects for my PhD and I'd
> say three important lessons are: allow enough time for usability/UX testing
> and optimisation; budget in time for community conversation and outreach
> for every single week the project is running; and your project will
> inevitably change (usually for the better) after contact with participants.
> You might also want to consider starting with a 'niche' project as a pilot
> - for example, focusing on a particular topic, genre or collection as this
> seems to help communities of participants form, and it's also easier to get
> a sense of overall progress towards your goal.
> 
> Gamifying projects (competitive leaderboards, etc) encourages some
> audiences and discourages others. If you've got a good sense of what your
> current communities and audiences would find rewarding, can you translate
> some of that into appropriate rewards for contributions?
> 
> If you're looking at video content, you may already have seen Waisda? for
> transcribing audio-visual archives (http://woordentikkertje.manbijthond.nl/
> is in Dutch but Google Translate etc should give you the idea). The US
> National Archives are using a platform called Amara for transcribing videos
> http://blogs.archives.gov/online-public-access/?p=9222
> 
> The Public Catalogue Foundation/BBC's Your Paintings Tagger
> http://tagger.thepcf.org.uk uses various controlled vocabularies, which has
> similarly divided people - some love it, some find it adds to the
> complexity of the task. You may have noticed a running theme in that no one
> interface will suit every potential user! As Sarah said, there are many
> different 'crowds'. If you have the resources, you could experiment with
> structured vs unstructured transcription or tagging and see which works
> better for your crowds.
> 
> And on the off-chance you can get to Maryland next week, I'm teaching a
> week-long crowdsourcing workshop with Ben Brumfield at a Digital Humanities
> summer school (
> http://www.dhtraining.org/hilt/course/crowdsourcing-cultural-heritage/).
> Failing that, I can send you the slides I use in crowdsourcing design
> activities.
> 
> Cheers, Mia
> 
> --------------------------------------------
> http://openobjects.org.uk/
> http://twitter.com/mia_out
> 'Crowdsourcing Our Cultural Heritage'
> <http://www.ashgate.com/default.aspx?page=637&calcTitle=1&title_id=19663&edition_id=1209349602>
> is out in October!
> I mostly use this address for list mail; my open.ac.uk address is checked
> daily
> 
> 
> On 28 July 2014 15:02, Stephen McConnachie <[log in to unmask]>
> wrote:
> 
>> In the BFI we're starting to scope a crowd sourcing project based on BFI
>> National Archive moving image collections (and possibly photograph
>> collection).
>> 
>> We're at a very early stage. For example, we're still defining the
>> ambition: do we want to gather permanently useful knowledge - such as
>> geographic location for film scenes, annotated with timecode - for the
>> BFI's database; or do we simply want to engage existing audiences and
>> potentially new audiences in BFI activities / collections. Or both!
>> 
>> So I'm interested in learning from our peers in the museum sector, who are
>> farther down this path than we are. I'm particularly interested in any
>> Adlib users who have implemented crowd sourcing projects which write the
>> data to their Adlib system, either by API integration, or separate offline
>> workflow.
>> 
>> Maybe there's a great online resource describing the pitfalls, benefits,
>> methods, which I have missed? Collections Trust?
>> 
>> 1. platforms
>> Which platforms / websites / plugins are the obvious leaders in offering
>> data capture functionality to online users, and harvesting of that data for
>> use in a permanent repository?
>> 
>> Are there free options worth considering? Or plugins for leading
>> applications - eg Drupal, Wordpress?
>> 
>> Or is it better to find a developer budget / resource and just build a
>> bespoke layer to your website / collections search application?
>> 
>> 2. methodologies
>> Is it better to offer tightly controlled datasets for users to select (eg
>> genre / subject taxonomies), or is it more successful to offer more
>> freedom, and map / translate responses to your controlled datasets after
>> the fact?
>> (think I answered my own question, but: who has done it, by either
>> approach, and what lessons did you learn?)
>> 
>> Is it better to attempt a gamification / reward model, and if so, what has
>> worked and what has failed? For example: free tickets to physical domain
>> events? Badges for social media use? Is a tiered reward model better - ie,
>> contribute 100 responses and get this thing / contribute 1000 and get this
>> much better thing?
>> 
>> 3. business cases / benefits
>> If you have delivered a crowd sourcing project, how did you pitch and
>> demonstrate benefits to the organisation? Traffic to web resource? Survey?
>> Social media feedback?
>> 
>> Did you obtain funding help from any general research sources or specific
>> data sources? If so, practical tips on how that is achieved? If not, how
>> did you make the business case for internal resourcing?
>> 
>> Stephen
>> 
>> ****************************************************************
>>    website:  http://museumscomputergroup.org.uk/
>>    Twitter:  http://www.twitter.com/ukmcg
>>   Facebook:  http://www.facebook.com/museumscomputergroup
>> [un]subscribe:  http://museumscomputergroup.org.uk/email-list/
>> ****************************************************************
> 
> ****************************************************************
>    website:  http://museumscomputergroup.org.uk/
>    Twitter:  http://www.twitter.com/ukmcg
>   Facebook:  http://www.facebook.com/museumscomputergroup
> [un]subscribe:  http://museumscomputergroup.org.uk/email-list/
> ****************************************************************

****************************************************************
       website:  http://museumscomputergroup.org.uk/
       Twitter:  http://www.twitter.com/ukmcg
      Facebook:  http://www.facebook.com/museumscomputergroup
 [un]subscribe:  http://museumscomputergroup.org.uk/email-list/
****************************************************************

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager