Jump to content

2022 European GLAMwiki Coordinators meeting/Capacity workshop notes

Add links
From Meta, a Wikimedia project coordination wiki

Capacity building session @ GLAMwiki Coordinators meeting, Prague, Sep 14, 2022

(Notes copied from the session etherpad.)

1. GLAM capacity


How to get partnerships:

   Long relationship exercise. You get partnerships from partnerships

  • Decision-makers being involved

General awareness raising in specific sector


How to maintain partnerhips?

  • -Maintain may be easier if there is already a strong agreement or history of work together
  • -Having a reputation (where partners seek you)
  • -Very active Wikipedians in Residence - within the institutions.


Methods to build capcities:

  • -People within the institutions training GLAM professionals.
  • -Include Wiki word within wider capacity building programs.
  • - If you can get it formalised it is even better.  UK case - Job roles formalised where Wikidata is part of their job.
  • Wiki in Residence programs to train GLAM professionals  
  • -GLAM partners interested can be suppored with some funding from Wikimedia Affiliates (Italy is doing this).
  • -Capacity you build in British Library, it can help take it to other places because of the peer network.
  • - We are dedicating residencies in big GLAM instittutions, but often at the expense of smaller institutions?  Should we have a criteria to define support for different GLAMs?
  • -An option coule be to get big organisations to finance some of the capacity building support that the affiliate offers.

How to communicate to GLAM in non-Wiki way:

- Basic principals are not so hard to explain to institution

You have to address some of the desinformation around Wikimedia projects. From this point to actually cooperate is more difficult.

- Encouarge Wikidata capacity and interest: Have a query example. What quesitons could be answered by contributing.

- WMDE can support GLAM "pitches" to present about Wikidata and Wikibase.

It is possible, who is driving it? Driven by the newer affiliate. Those relationships need to be in existence.

Spain and UK have collaborated in this way to help prepare the call.

  • But we need better and more case studies:
  • Opportunities for external technical and financial support for research: Are the case studies we have today enough?
  • We need more in depth up to date is needed.
  • We need more up todate cases studies to address copyright issues (today use - Bunders archeive. Rijksmuseum).  
  • Two tpyes of case studies:
  •    General GLAM
  •   Small GLAM (challenges are different, resources, etc). Show examples in difficult funding contexts. Case studies in countries where funding for GLAM is difficult. Also better share the ones we have now.


We need to fund more long term case studies


Have good pool of resources of what opportunities there are:

GLAM Wiki handbook. These are the options that GLAM institutions can do (Italy does this).


What is in between residencies or edit-a-thon? Some ideas:

  - Smaller organisations have volutneers - how can they turn existing resources into Wiki activity (case UK with Science museum). Trying with an organisation with less capacity, they are too busy.

  - Italy: MOOC courses about GLAM contribution. We enable GLAM staff to train and contribute. With in person training they go to workshop but do not contribute. We hope with the MOOC we can support them more.

How to get partnerships:

  (later add): starting with small non-threatening projects, with small cluster on contents, and then showing that it was not so hard to do and how much impact it had

2. Community challenges

  • Put some "prizes"
  • Contest
  • Bigger volunteer base
  • Making events (museum tours and trying to get them more interested in GLAM that involve edit-a-thons, photo tours)
  • "Mixing" activities (WiR and edit-a-thons)
  • To make competitions for editors related to GLAM cooperations and activities
  • Giving them something "special" that usually you dont have an access to
  • Not focusing on metrics but on good experience
  • WiR: good training,


3. Documentation


Current painpoints:

  • International involvement
  • Translation of documentation
  • On multiple platforms and formats
  • Multiple partners have similar requirements


One idea is instead of using single-language Wikipedia project pages, we could use the multi-lingual meta functionalities to announce/document activities for worldwide availability, certainly for huge/large museums.

But this does not solve the Wiki-text restriction, although there is the Graphical Editor.


Learning patterns from GLAM - how to develop this experience-sharing exchange and talk also about failures, not only success.

https://meta.wikimedia.org/wiki/Learning_patterns/Wikimedian-in-residence_mentorship_model


Examples of a single-language page:

https://pl.wikipedia.org/wiki/Wikiprojekt:GLAM/Projekty

https://nl.wikipedia.org/wiki/Wikipedia:WikiProject_Wiki_Women_Design

https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Wiki_Women_Design

https://fr.wikipedia.org/wiki/Wikipedia:WikiProject_Wiki_Women_Design


Maybe having Wikidata as a base system to gather documentation, or links to documentation, and then have an application like e.g. Reasonator to present the content.


https://www.wikidata.org/wiki/Q2859916

https://reasonator.toolforge.org/?q=Q2859916&lang=en


4. Legal

Who can address these issues:

  • - Public policy, advocacy, copyright: In Europe it probably makes sense to organise around freedom of Panorama and Article 14. Wikimedia Europe seems like the obvious lead for this but they aren't very focused on open access/ culture and heritage. We also need to advocate within the movement to trust museums' judgement with regards to contributing orphan works.
  • - Training volunteers CC licences. Creative Commons would be the obvious lead here, especially since they developed the CC GLAM certificate. But it could be enhanced with a Wikimedia module. It is also relatively expensive and time-intensive. It might be useful to have an more introductory level as well as the full course.
  • - There was also a need for case studies that could be used in advocacy. Let's Connect could be the program to coordinate this.
  • - We didn't address the question of who could OTRS caapcity in our community. Or how to address legacy issues created by bot uploads.
  • - Working on advocacy and copyright is a long-term project so there is need for many partners and contributors so people can rest and recouperate.  
  • - Who is taking care of volunteers and organizers.
  • - Working with knowledge equity and marginalised topics can be more difficult, exposing. Support people that may be having difficulties.
  • - Also discussed the need for more flexibility/ unrestricted funding.
  • - WM France hotline for volunteers. It was very needed. People don't always feel safe.


5. Tech (mass uploads)

The post its were:

  • Lack of technical profiles (data upload)
  • Data helpline
  • Need help to set up Wikibase instance
  • Massive uploader easy to understand by volunteer, not just it-ers
  • Identifying gaps
  • Decentralized knowledge in the community - hard to find it (e.g. on metrics)
  • Batch upload skills
  • Learn to make videos


Current problems:

  • Affiliates often have lots of requests from GLAMs, and often not the right or enough volunteers to deal with them correctly
  • Institutions want affiliate to take care of the entire process - just give a harddrive
  • There are often not enough trainers in a community (eg for OpenRefine)


What would help:

  • A helpdesk with technical people who can handle the uploads (what WMSE is doing)
  • Interface that takes files and retrieves metadata, and then simply uploads to Commons. Wizard on top of OpenRefine?
  • Certified training program for volunteers (international, with badge/diploma). Also open for GLAMs. Building a visible pool of trainees
  • Training at scale: office hours, two hours sessions to answer questions.
  • Train the trainer program (in the native language)
  • Regular international sessions

6 Equity


7. Orphan


General notes:

   

Volunteers: have more engaging activites, fun. Building resources for volunteers.

Would it be interesting for new volunteers to connect with new volunteers in other places?

   

Documentation:

Translating documentation. Can restrict the way to write your documentation. Multiple partners can have similar requirements. Use meta as central platform for documenting. Tempalte on Meta to serve as a showcase.

Use more Wikidata. Use resonator to present the documentation in another way.


Learning patterns, can share their experience with specific questions. Knowledge is descentralised.

Ways to show the specific projects.


Story telling without breaking into something personal.

What are the incentives?


Helpdesk: Having support for mass uploads.

Training: certified program for GLAM staff. Badge and diploma - to be a "Wikimedia uploader". Have pool of traniners.

Conversation hours to talk about new features and tools.

Train the trainer program for Open Refine and in multiple languages.


Who could do this? stopped doing it for Open Refine. Hub could organise this type of conversation hours.

Retrieved from "https://meta.wikimedia.org/w/index.php?title=2022_European_GLAMwiki_Coordinators_meeting/Capacity_workshop_notes&oldid=23904618"