<?xml version="1.0" encoding="utf-8"?> <rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0" xml:base="https://lab.kb.nl/"> <channel> <title>KB LAB News</title> <link>https://lab.kb.nl/</link> <description/> <language>en</language> <item> <title>Presenting DutchDraCor: A new KB dataset for computational approaches to early modern Dutch theatre</title> <link>https://lab.kb.nl/about-us/blog/presenting-dutchdracor-new-kb-dataset-computational-approaches-early-modern-dutch</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;em&gt;From February to October 2024, I had the privilege of working as a researcher-in-residence at the National Library of the Netherlands. The aim of my residency was to prepare the early modern theatre editions available in the DBNL for computational studies of early modern Dutch drama. In this blogpost I present the first result of that effort: a corpus of 180 early modern Dutch plays, fully encoded and annotated in TEI XML according to the standards prescribed by the international theatre database developed by the Drama Corpora Project (DraCor).&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;In the last three decades, the access to digital theatre corpora has increased dramatically. Because institutions such as the Folger Shakespeare Library, the Bibliothèque nationale de France (BnF) and the National Library of the Netherlands (KB) were quick to digitise their theatre collections, digital reproductions of early modern theatre editions have been available on the web for many years. The online access to these editions has opened up Western theatrical heritage to students, scholars and other readers. For the Dutch context, the main collections of digital theatre editions can be found in the Digital Library for Dutch Literature (DBNL, maintained by the National Library of the Netherlands) and the Census Nederlands Toneel (Ceneton, which was developed and edited by Ton Harmsen at Leiden University). Thousands of students have first discovered the richness of plays by Joost van den Vondel, G.A. Bredero or Catharina Verwers through those collections.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;Recently, theatre scholars recognised the additional potential of the existing repositories for comparative research into historical theatre traditions. They applied methods and concepts from other fields, such as network theory (e.g. Moretti 2011), economics (Algee-Hewitt 2017) and the history of emotions (Leemans et al. 2017), to model features of the text and structure of those plays, such as character interactions, social composition of story worlds, or emotional expressions. Those abstractions enabled researchers to systematically compare hundreds or even thousands of plays. Including this larger scale of analysis in historical drama research is necessary to identify and describe patterns and developments across time periods and even (language) borders. A great introduction into the state of the art of this young research tradition can be found in the recently published collection &lt;em&gt;Computational Drama Analysis&amp;nbsp;&lt;/em&gt;(2024) edited by Melanie Adresen and Nils Reiter. For the Dutch context, my recent article on theatre society Nil Volentibus Arduum offers a good impression (Van der Deijl 2024).&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;The Drama Corpora Project&lt;/h3&gt; &lt;p&gt;Computational approaches to historical drama benefited significantly from the initiative by Frank Fischer, Peer Trilcke and everyone else from the Drama Corpora Project (&lt;a href="https://dracor.org/"&gt;DraCor&lt;/a&gt;) to create a so-called ‘programmable corpus’ of theatre editions from multiple European languages (Fischer et al. 2019). All editions included in the DraCor-database are fully encoded in TEI XML, which means that all structural elements in the play are labelled separately: acts, scenes, speech turns, speaker indications, stage directions et cetera. Moreover, the text from the editions is manually annotated with additional metadata. All speech turns are disambiguated with unique character IDs and all characters received a gender label. This step enables the extraction of speech turns by character or by gender group, for example. By introducing a cross-lingual standard for the encoding and annotation of theatre editions, DraCor facilitates and standardises computational analyses of dramatic texts from various linguistic and cultural backgrounds. Moreover, through its interoperable&amp;nbsp;API (Application Programming Interface; an entry point for computers), the database can be questioned and queried on various levels using programming languages.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;However, until recently there was no Dutch corpus available in the DraCor infrastructure. Due to this omission, Dutch-language theatre traditions have been a blind spot in current debates on computational drama research (with a few exceptions: Leemans et al. 2017; Debaene et al. 2024). The rich theatre culture from the Dutch language field thus tends to be overlooked, even though the DBNL and Ceneton already contain hundreds of high quality transcriptions of early modern theatre editions. Converting those editions to DraCor’s encoding standard would connect Dutch drama to other European theatre traditions, which have always been key to its development. As a response to this lack of a suitable Dutch theatre corpus, I collaborated with experts from the KB and with students from the University of Groningen to develop a first selection of 180 fully encoded Dutch plays. This corpus has been integrated in the DraCor infrastructure and will continue to grow in the future under the name of the Dutch Drama Corpus (&lt;a href="https://dracor.org/dutch"&gt;DutchDraCor&lt;/a&gt;). In this blogpost, I briefly describe the characteristics of this corpus at the moment of its second release in October 2024.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="image-alignment--text-image"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="row flex-start order"&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;DutchDraCor: characteristics and statistics&lt;/h3&gt; &lt;p&gt;In October 2024, DutchDraCor contains 180 fully encoded plays, with 2.117 speaking characters or character groups (including 1.364 male character (groups) versus 514 female character (groups)). The corpus includes over 2.3M words, 60.021 speech turns and 5.750 stage directions. 151 editions were derived from DBNL and 29 plays (the complete oeuvre of theatre society Nil Volentibus Arduum) were collected from Ceneton. There are 68 distinct first authors or author groups represented in the corpus, excluding translators. Some authors or groups are overrepresented in the corpus due to their large production and overrepresentation in the source collections, such as chamber of rhetoric De Pellicaen (39 plays), Joost van den Vondel (31), Nil Volentibus Arduum (29), and Jan Harmensz Krul (9). The corpus contains both plays originally written in Dutch and Dutch translations of plays written in other languages – mostly French, Latin and Spanish –&amp;nbsp; as translations and adaptations were an important part of the early modern literary production in the Low Countries.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-hidden field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/dracor1.png?itok=fIh8_eCE" width="283" height="380" alt="DutchDracor statistics"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;Coverage and representativeness&lt;/h3&gt; &lt;p&gt;Assessing the coverage of DutchDraCor is not straightforward, as it is not evident how to measure representativeness. In an ideal world, the corpus should contain a representative sample of all plays that were written, printed and staged in Dutch between 1500 and 1800. Since there are no reliable estimations of all plays that were once written and or performed in the early modern Low Countries, I cannot quantify the relationship between sample and ‘population’. Instead, I will point to a few important biases in the corpus in terms of year of publication, genre and author gender.&amp;nbsp;&lt;/p&gt; &lt;p&gt;First of all, plays from the sixteenth and eighteenth century are underrepresented. The bar chart below shows the number of plays written or printed per decade, confirming that DutchDraCor is especially useful for studies of seventeenth-century drama. Future additions to DutchDraCor will need to correct for this temporal imbalance.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/dracor2_numberofplays.png?itok=hTatMRxR" width="1300" height="608" alt="Dracor number of plays per decade"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="image-alignment--text-image"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="row flex-start order"&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;Secondly, the corpus is not balanced in terms of genre. The most frequent genre labels are tragedy (‘treurspel’), morality play (‘zinnespel’) followed by comedy (‘blijspel’) and farce (‘klucht’). There is also a temporal imbalance in this genre distribution, since most morality plays were written in the sixteenth century, whereas most tragedies were written and printed in the seventeenth and eighteenth century.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-hidden field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/dracor3_genres.png?itok=81MqqbQy" width="761" height="710" alt="Dracor genres"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;Finally, there is no equal gender balance among the authors represented in the corpus.&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;The vast majority of the authors in the corpus is male: only 18 plays (10%) were written by women: 7 by Katharyne Lescailje, 7 by Lucretia Wilhelmina van Merken, 3 by Catharina Questiers and 1 by Catharina Verwers. Like the biases concerning period and genre, this overrepresentation of male poets is partly caused by the imbalances in the used collections (DBNL and Ceneton) and in the extant source material digitised in those collections. Computational approaches of early modern Dutch drama based on DutchDraCor need to take these biases into account, including the stage in the history of the editions where the bias was introduced (from writing, to printing, collecting, archiving, digitisation and encoding).&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;Where to find DutchDraCor&lt;/h3&gt; &lt;p&gt;The full corpus is available through the&amp;nbsp;&lt;a href="https://dracor.org/dutch"&gt;DraCor infrastructure&lt;/a&gt;, which offers various downloadable representations of the plays and the metadata about the plays. The corpus can also be downloaded in full via GitHub. DutchDraCor will continue to grow in the future, but a standalone version of the corpus described here will become available via Zenodo. Enjoy!&lt;/p&gt; &lt;p&gt;In my next blog post, I will demonstrate the value of DutchDraCor by taking the gender balance in the corpus as a case study rather than a bias, questioning the position and visibility of female characters on the stages in the Low Countries.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;Acknowledgments&lt;/h3&gt; &lt;p&gt;DutchDraCor was created with the assistance of many contributors: Teun de Vries, Hinke van Minnen, Mirthe Wubs, Mirte Triezenberg, Jasmijn van Valkenburg, Hilde Bos, Marc Bos, Melissa Nijboer, Thirza Fokkens, Jarick van der Wal, Anna Lap, Maurice Eeftink, Annechien Hussem, Jens Klein, Jan de Vries, Hidde van Deemter, Ivar Czudar, Evi Dijcks, Alie Lassche. Special thanks to Willem Jan Faber, Suzan Boreel and everyone from the digital scholarship team at the KB.&lt;/p&gt; &lt;p&gt;For the creation of DutchDraCor Lucas van der Deijl was supported by the National Library of the Netherlands (&lt;a href="https://www.kb.nl/"&gt;KB&lt;/a&gt;) during a residency from February to October 2024 and by&amp;nbsp;&lt;a href="https://clsinfra.io/"&gt;CLS INFRA&lt;/a&gt; during a Transnational Access (TNA) fellowship at the University of Potsdam in April 2024.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;References&lt;/h3&gt; &lt;p&gt;Adresen, Melanie and Nils Reiter. &lt;em&gt;Computational Drama Analysis: Reflecting on Methods and Interpretations&lt;/em&gt;. Berlin, Boston 2024.&lt;/p&gt; &lt;p&gt;Algee-Hewitt, M. ‘Distributed Character: Quantitative Models of the English Stage, 1550–1900’. &lt;em&gt;New Literary History&lt;/em&gt; &lt;em&gt;48&lt;/em&gt; (2017) 4, 751-782.&amp;nbsp;&lt;/p&gt; &lt;p&gt;Debaene, Florian, et al. ‘Early Modern Dutch Comedies and Farces in the Spotlight : Introducing EmDComF and Its Emotion Framework.’ &lt;em&gt;Proceedings of the Third Workshop on Language Technologies for Historical and Ancient Languages (LT4HALA) @ LREC-COLING-2024&lt;/em&gt;, edited by Rachele Sprugnoli and Marco Passarotti, ELRA and ICCL, 2024, 144–55.&lt;/p&gt; &lt;p&gt;Deijl, L.A. van der. ‘Orde en rationalisme in het toneel van Nil Volentibus Arduum. Een computationele benadering van vroegmoderne verhaalmodellen’. &lt;em&gt;Spiegel der Letteren&amp;nbsp;&lt;/em&gt;66&lt;em&gt;&amp;nbsp;&lt;/em&gt;(2024) 1, 53-94.&lt;/p&gt; &lt;p&gt;Fischer, Frank, et al.&amp;nbsp;‘Programmable Corpora: Introducing DraCor, an Infrastructure for the Research on European Drama’.&amp;nbsp;In &lt;em&gt;Proceedings of DH2019: "Complexities"&lt;/em&gt;, Utrecht University, 2019.&amp;nbsp;&lt;/p&gt; &lt;p&gt;Leemans, Inger, et al.&amp;nbsp;‘Mining Embodied Emotions: A Comparative Analysis of Sentiment and Emotion in Dutch Texts, 1600-1800’. &lt;em&gt;Digital Humanities Quarterly&lt;/em&gt; 11 (2017) 4.&amp;nbsp;&lt;/p&gt; &lt;p&gt;Moretti, Franco, ‘Network Theory, Plot Analysis’, &lt;em&gt;Stanford Literary Lab Pamphlets&lt;/em&gt; 2 (2011).&lt;/p&gt; &lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Mon, 18 Nov 2024 09:38:20 +0100</pubDate> <dc:creator>celonie.rozema@kb.nl</dc:creator> <guid isPermaLink="false">396 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>Archiving the KB Lab</title> <link>https://lab.kb.nl/news/archiving-kb-lab</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;We are now archiving the KB Lab!&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt; &lt;p&gt;According to the&amp;nbsp;&lt;a href="https://www.communicatierijk.nl/vakkennis/rijkswebsites/verplichte-richtlijnen/archiefwet"&gt;Archive Act&lt;/a&gt; of the Netherlands, government organizations should archive their websites. As the KB is an independent governing body (“zelfstandig besturingsorgaan” (ZBO)), our&amp;nbsp;tasks fall under the scope of this Archive Act.&lt;/p&gt; &lt;p&gt;Since October 8th, the KB Lab is being archived every single day. This process includes harvesting, preparing and uploading each page of the website, as well as the links between pages. This makes it possible to navigate the archive just like you would the website itself. Links to external URLs are excluded, but everything else is collected for the future in an accessible and sustainable way. The archive shows the state of the website on any given day, making it possible to compare over time and track changes.&amp;nbsp;&lt;/p&gt; &lt;p&gt;The KB Lab archive is publicly available at&amp;nbsp;&lt;a href="http://kb.webarchief.online/lab-kb-nl" title="kb.webarchief.online/lab-kb-nl"&gt;kb.webarchief.online/lab-kb-nl&lt;/a&gt;. You can now also permanently find this link in the footer, at the very bottom of the website. We are looking forward to seeing the KB Lab archive grow with time!&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Wed, 16 Oct 2024 14:33:35 +0200</pubDate> <dc:creator>celonie.rozema@kb.nl</dc:creator> <guid isPermaLink="false">392 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>10 reasons why the National Library of the Netherlands moved its Wikimedia-related publications from SlideShare to Zenodo, and keeps them on Wikimedia Commons</title> <link>https://lab.kb.nl/about-us/blog/10-reasons-why-national-library-netherlands-moved-its-wikimedia-related-publications</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;em&gt;In this article the Wikimedia coordinator of the KB, the national library of the Netherlands, explains why he decided to migrate all KB’s Wikimedia-related publications of the last 13 years from SlideShare to Zenodo, while retaining copies of them on Wikimedia Commons.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/kb_gebouw.png?itok=l_M5KZl-" width="1024" height="695" alt="Photo of the KB building with a square in front of it."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Main entrance of the KB national library of the Netherlands&lt;/em&gt;. &lt;em&gt;Source: KB, national library of the Netherlands&lt;/em&gt;.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="image-alignment--text-image"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="row flex-start order"&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;As the &lt;a href="https://www.kb.nl/over-ons/experts/olaf-janssen"&gt;Wikimedia coordinato&lt;/a&gt;r of the KB, the &lt;a href="https://en.wikipedia.org/wiki/Royal_Library_of_the_Netherlands" data-wp-title="Royal_Library_of_the_Netherlands" data-wp-lang="en"&gt;national library of the Netherlands&lt;/a&gt;, sharing knowledge is an integral and important part of my job. Not only live during events, but also for knowledge reference and sustainability purposes after the events have ended.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-hidden field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/kb_logo.png?itok=vUVUzZLU" width="374" height="123" alt="KB|National library of the Netherlands"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="image-alignment--text-image"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="row flex-start order"&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;Wikimedia Commons&lt;/h3&gt; &lt;p&gt;This is why I make all Wikimedia-related presentations, articles, reports, workshop materials, tutorials, videos and other publications available in the Dutch and English bilingual &lt;a href="https://commons.wikimedia.org/wiki/GLAM_at_Koninklijke_Bibliotheek/Archive"&gt;KB Wikimedia presentations &amp;amp; publications archive&lt;/a&gt; on Wikimedia Commons. I’ve been doing so for the last 13 years. This ensures all such KB content:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;can be easily found via search engines (Google loves Wiki),&lt;/li&gt; &lt;li&gt;is available for reuse in the &lt;a href="https://meta.wikimedia.org/wiki/Complete_list_of_Wikimedia_projects"&gt;700+ Wikimedia projects&lt;/a&gt; and communities,&lt;/li&gt; &lt;li&gt;can be reused freely by the entire world because open (Creative Commons) licensing is mandatory,&lt;/li&gt; &lt;/ul&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-hidden field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/image_41cd7f.png?itok=BjUG71k5" width="259" height="299" alt="Wikimedia commons logo"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;ul&gt; &lt;li&gt;can be used as linked open data, independent of language, because multilingual &lt;a href="https://commons.wikimedia.org/wiki/Commons:Structured_data"&gt;Structured Data&lt;/a&gt; has been added to many of these files,&lt;/li&gt; &lt;li&gt;is stored in a durable way; this year, Wikimedia Commons is celebrating its 20th anniversary and future financing and governance look strong.&lt;/li&gt; &lt;/ul&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/KB-Wikimedia-presentations-and-publications-archive-28-August-2024.png?itok=SJUvQ0FO" width="1300" height="1041" alt="Screenshot of the Wikimedia page 'Glam at Koninklijke Bibliotheek / Archive"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Screenshot of the &lt;/em&gt;&lt;a href="https://commons.wikimedia.org/wiki/GLAM_at_Koninklijke_Bibliotheek/Archive"&gt;&lt;em&gt;KB Wikimedia presentations &amp;amp; publications archive&lt;/em&gt;&lt;/a&gt;&lt;em&gt; on Wikimedia Commons, dd 28 August 2024.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="image-alignment--text-image"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="row flex-start order"&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;SlideShare and new needs&lt;/h3&gt; &lt;p&gt;In addition to Wikimedia Commons, I also used to upload &lt;a href="https://www.slideshare.net/OlafJanssenNL"&gt;my outputs to SlideShare&lt;/a&gt;. When I started doing this 14 years ago, my publishing and sharing needs were relatively simple and naive, with visibility and findability being the main purposes. Back then, SlideShare met this need, as it is well-indexed by search engines, has a visual-first user experience, and can be embedded into LinkedIn and Twitter posts.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-hidden field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/slideshare_logo2.png?itok=KU00wXOv" width="1190" height="362" alt="Slideshare with logo (white background, two figures holding a frame)"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;At that time I had no need for (or awareness of) more advanced functionalities, such as&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Sharing a wider variety of file formats, beyond the typical “presentation oriented” PDF and JPG, such as more “data oriented” formats like JSON, TSV, Markdown, Jupyter notebooks or zipped OpenRefine project files.&lt;/li&gt; &lt;li&gt;Publishing constituent workshop materials under one unique and persistent identifier – i.e. making all slides, notes, guide for participants, CSV with data, Jupyter notebooks or OpenRefine files used for a typical (data)workshop accessible as a combined package via a single URL.&lt;/li&gt; &lt;li&gt;Sharing large files, such as video recording of live presentations of 100s of MBs, or entire datasets of hundreds of hi-res images and their descriptive metadata files.&lt;/li&gt; &lt;li&gt;Adhering to &lt;a href="https://www.go-fair.org/fair-principles/"&gt;FAIR principles&lt;/a&gt;.&lt;/li&gt; &lt;li&gt;REST APIs to interact with the publications programmatically.&lt;/li&gt; &lt;li&gt;OAI-PMH connectivity for exchanging publications with other repositories.&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;Although Wikimedia and/or SlideShare can meet some of these needs, over the years I gradually found out that they were not really potent enough to meet my ever increasing publication needs for my work to be discoverable and reusable by as many people, institutions and machines as possible, now and in the future, in a durable way, with low risk of their URLs becoming 404s or not findable at all.&lt;/p&gt; &lt;p&gt;Furthermore, the KB is a scientific institution and thus part of the international science and research communities. So as an employee of such an institution, I felt a need to also make my publications more strongly integrated into these communities. Both Wikimedia Commons and SlideShare fail to meet this need, neither of them has a strong user base in academic publishing.&lt;/p&gt; &lt;p&gt;Finally, as a European user of SlideShare, without going into all (legal) details, I felt some stress about having my content hosted on servers located in the US and being under that jurisdiction. This stimulated me to look for strictly EU-based hosting alternatives.&lt;/p&gt; &lt;h3&gt;New publication strategy, including Zenodo&lt;/h3&gt; &lt;p&gt;The new needs and insights I developed over these years slowly but surely urged me to change my approach to storing and sharing my content. As the KB has been a part of the Wikimedia community for many years, an important requirement was to keep all Wikimedia-related KB output available through Wikimedia Commons.&lt;/p&gt; &lt;p&gt;However, for the KB content hosted on SlideShare, I needed to find a better place, closer to home, on EU-based servers, with a service meeting as many of my demands as possible.&lt;/p&gt; &lt;p&gt;After doing some (non-exhaustive) comparison, using the &lt;a href="https://zenodo.org/records/7946938"&gt;Generalist Repository Comparison Chart&lt;/a&gt; among others, I picked &lt;a href="https://en.wikipedia.org/wiki/Zenodo?wprov=wppw2"&gt;Zenodo&lt;/a&gt; as the best match for my needs.&lt;/p&gt; &lt;blockquote&gt;&lt;p&gt;In summary, &lt;a href="https://about.zenodo.org/"&gt;Zenodo&lt;/a&gt; &lt;em&gt;is a general-purpose EU-hosted data repository built on open-source software that accepts all forms of research output, including presentations, research papers, data sets, research software, reports, and any other research related digital artefact. For each submission, a persistent &lt;/em&gt;&lt;a href="https://en.wikipedia.org/wiki/Digital_object_identifier" data-wp-title="Digital_object_identifier" data-wp-lang="en"&gt;&lt;em&gt;digital object identifier&lt;/em&gt;&lt;/a&gt;&lt;em&gt; (DOI) is minted, which makes the stored items easily citable.&lt;/em&gt;&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;My choice for Zenodo was also influenced by my wish to comply with KB’s earlier choice of Zenodo as its preferred repository; employee-generated publications have been stored in its &lt;a href="https://zenodo.org/communities/kbnl/records?q=&amp;amp;l=list&amp;amp;p=1&amp;amp;s=10&amp;amp;sort=oldest"&gt;KB community&lt;/a&gt; since 2017.&lt;/p&gt; &lt;p&gt;Gradually I started moving my Wikimedia-related content from SlideShare to Zenodo. Along the way I also improved and harmonized the descriptions and other metadata associated with the files. Of course I made sure to submit all my content to the KB community as well. I completed this task in the summer of 2024, making all these &lt;a href="https://zenodo.org/communities/kbnl/records?q=&amp;amp;f=subject%3AOlaf%20Janssen&amp;amp;l=list&amp;amp;p=1&amp;amp;s=10&amp;amp;sort=newest"&gt;presentations, articles, reports, tutorials, videos and other publications&lt;/a&gt; now accessible from Zenodo.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/zenodo_kb_28082024.png?itok=SdmCaZ28" width="762" height="958" alt="Screenshot of KB community page with this article mentioned on top."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Screenshot of KB’s Zenodo community page, dd 28 August 2024, now including all Wikimedia-related publications that were previously hosted on SlideShare. &lt;/em&gt;&lt;a href="https://zenodo.org/communities/kbnl/records?q=&amp;amp;f=subject%3AOlaf%20Janssen&amp;amp;l=list&amp;amp;p=1&amp;amp;s=10&amp;amp;sort=newest"&gt;&lt;em&gt;Source&lt;/em&gt;&lt;/a&gt;&lt;em&gt;.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;My Top 10 Zenodo features&lt;/h3&gt; &lt;p&gt;Let us now look at the ten Zenodo features that are most relevant for meeting my personal needs and wishes, in comparison to SlideShare and Wikimedia Commons. I have no ambition to discuss the complete feature set Zenodo has to offer; if you are interested in that, you can check Zenodo’s detailed public &lt;a href="https://about.zenodo.org/"&gt;About&lt;/a&gt;, &lt;a href="https://about.zenodo.org/principles/"&gt;Principles&lt;/a&gt;, &lt;a href="https://about.zenodo.org/policies/"&gt;General Policies&lt;/a&gt;, &lt;a href="https://about.zenodo.org/privacy-policy/"&gt;Privacy Policy&lt;/a&gt; and &lt;a href="https://about.zenodo.org/infrastructure/"&gt;Infrastructure&lt;/a&gt; documents.&lt;/p&gt; &lt;p&gt;The 10 advantages of Zenodo most important to me are :&lt;/p&gt; &lt;p&gt;&lt;strong&gt;1) Sharing a wide variety of file formats&lt;/strong&gt;, beyond the typical “presentation-oriented” PDF and JPG, such as more “data-oriented” formats like JSON, TSV, Markdown, Jupyter notebooks, or zipped files. Zenodo is very flexible, as it &lt;a href="https://help.zenodo.org/docs/deposit/about-records/"&gt;supports uploading files in any format&lt;/a&gt;. Wikimedia Commons has a &lt;a href="https://en.wikipedia.org/wiki/Help:Creation_and_usage_of_media_files?wprov=wppw2" data-wp-title="Help:Creation_and_usage_of_media_files" data-wp-lang="en"&gt;smaller set&lt;/a&gt; of supported formats and SlideShare only allows &lt;a href="https://support.scribd.com/hc/en-us/articles/360055259612-Supported-SlideShare-file-formats-and-sizes"&gt;PowerPoint, PDF and Word&lt;/a&gt; files.&lt;/p&gt; &lt;p&gt;&lt;em&gt;Example:&lt;/em&gt; The &lt;a href="https://zenodo.org/records/7665231"&gt;&lt;em&gt;Workshop OpenRefine en Wikimedia Commons (19-11-2022)&lt;/em&gt;&lt;/a&gt; hosts files in tar.gz, pdf, xlsx, txt and json formats.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/zenodo_multiple_files.png?itok=m-t6e0lq" width="903" height="528" alt="Screenshot of Zenodo showing multiple files stored there. "&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Screenshot of the files used in ‘&lt;/em&gt;&lt;a href="https://zenodo.org/records/7665231"&gt;&lt;em&gt;Workshop OpenRefine en Wikimedia Commons&lt;/em&gt;&lt;/a&gt;&lt;em&gt;’, hosting tar.gz, pdf, xlsx, txt and json formats.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;strong&gt;2) Publishing constituent workshop materials&lt;/strong&gt; under one unique and persistent identifier. When running a typical data-oriented workshop, it is very convenient – both for the participants and for post-workshop archiving – to publish all materials (slides, notes, guide for participants, csv with data, Jupyter notebooks, Openrefine project files, etc.) as a combined package in a single location under a single durable URI or DOI. This is a real added value of Zenodo, as both SlideShare and Wikimedia Commons allow only one file per upload.&lt;/p&gt; &lt;p&gt;&lt;em&gt;Example:&lt;/em&gt; This &lt;a href="https://zenodo.org/records/8207914"&gt;&lt;em&gt;OpenRefine Introduction Workshop&lt;/em&gt;&lt;/a&gt; (2023) packages six files (pdf, xlsx, txt, and md) into a single upload.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;3) Sharing large files, &lt;/strong&gt;with personal use cases including video recording of live presentations of hundreds of MBs, or datasets containing large numbers of hi-res images and their descriptive metadata files (1+ GB). SlideShare has a &lt;a href="https://support.scribd.com/hc/en-us/articles/360055259612-Supported-SlideShare-file-formats-and-sizes"&gt;300MB limit&lt;/a&gt; and Wikimedia Commons allows 100MB by default, or up to 5GB when using &lt;a href="https://commons.wikimedia.org/wiki/Help:Chunked_upload"&gt;chunked uploading&lt;/a&gt;. Zenodo has a default &lt;a href="https://about.zenodo.org/policies/"&gt;50GB file size limit&amp;nbsp;&lt;/a&gt; for each publication, which is more than enough for my needs.&lt;/p&gt; &lt;p&gt;&lt;em&gt;Example:&lt;/em&gt; Hosting the 397 MB video &lt;a href="https://zenodo.org/records/13268860"&gt;&lt;em&gt;Wikidata in de praktijk bij de Koninklijke Bibliotheek, masterclass Wikidata (28-05-2021)&lt;/em&gt;&lt;/a&gt; is well within Zenodo’s file size limits.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;4) Restricting access to files&lt;/strong&gt; and &lt;strong&gt;saving drafts &lt;/strong&gt;are &lt;a href="https://help.zenodo.org/docs/deposit/about-records/#access"&gt;features in Zenodo&lt;/a&gt; that allow editors to work on (drafts of) records in a closed-off environment before releasing them to the public. Wikimedia Commons does not offer this, as every file there is publicly accessible, and under version control right from the start, making it unsuitable for drafting temporary or permanent non-open publications.&lt;/p&gt; &lt;p&gt;&lt;em&gt;Example:&lt;/em&gt; I’m currently preparing a &lt;a href="https://theplant.maastrichtuniversity.nl/event/navigating-the-world-of-wikidata-for-research-science-and-cultural-heritage-2/"&gt;Wikidata introduction workshop for Maastricht University&lt;/a&gt; and already uploaded some draft materials for this event to Zenodo. When the preparations are finished, I will openly share the files with the participants via &lt;a href="https://doi.org/10.5281/zenodo.11224632"&gt;https://doi.org/10.5281/zenodo.11224632&lt;/a&gt; &amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/zenodo_maastricht_15okt2024.png?itok=eTuhWt3r" width="796" height="681" alt="Screenshot of Zenodo page of Olaf Janssen with 'Introduction to Wikidata for Maastricht University, theory and practice, 15 October 2024 article prominently featuring.."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Screenshot of restricted draft materials for an upcoming Wikidata workshop on 15 October 2024. Files will be accessible via &lt;/em&gt;&lt;a href="https://doi.org/10.5281/zenodo.11224632"&gt;&lt;em&gt;https://doi.org/10.5281/zenodo.11224632&lt;/em&gt;&lt;/a&gt;&lt;em&gt; after that date.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;strong&gt;5) Wider licensing options&lt;/strong&gt; compared to Wikimedia Commons and SlideShare. By default, I publish and share my content under open licenses, either CC-BY, CC-BY-SA or even CC0. This makes my publications &lt;a href="https://commons.wikimedia.org/wiki/Commons:Licensing#Acceptable_licenses"&gt;suitable for Wikimedia Commons&lt;/a&gt; as well as &lt;a href="https://support.scribd.com/hc/en-us/articles/360055664591-Your-SlideShare-content-settings-and-licensing"&gt;for SlideShare&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;However, in some cases, I would like to have a bit more control over derivative or commercial reuses of my works, for which CC-BY-ND and/or CC-BY-NC licensing are appropriate instruments. This makes these kinds of works unsuitable for sharing on Wikimedia Commons, but SlideShare would still be an option, as these more restrictive licenses are allowed there.&lt;/p&gt; &lt;p&gt;Zenodo accommodates all of the above scenarios, as it allows for both very open (CC0) and less open (CC-BY-NC/ND) licenses, as well as over &lt;a href="https://spdx.org/licenses/"&gt;600 alternative options&lt;/a&gt;, both for presentation-oriented and data-oriented publication. So in the vast majority of cases, there is always a suitable license to choose from.&lt;/p&gt; &lt;p&gt;The only exception is the ‘All rights reserved’ case. It is allowed by SlideShare, but not on either open-oriented platform. However, I can use this limitation of Zenodo and Commons as a stimulant to always create publications that are suitable for sharing (be it under a CC-BY-ND/NC clause) and reuse when possible (without the ND clause).&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/spdx.png?itok=CUk8yLij" width="1023" height="737" alt="Screenshot of licenses used by Zenodo"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;List of over 600 licensing options used by Zenodo, from &lt;/em&gt;&lt;a href="https://spdx.org/licenses"&gt;&lt;em&gt;https://spdx.org/licenses&lt;/em&gt;&lt;/a&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;strong&gt;6) Adhering to FAIR principles.&lt;/strong&gt; Zenodo’s &lt;a href="https://about.zenodo.org/principles/"&gt;Principles page&lt;/a&gt; explains in detail how the repository adheres to the &lt;a href="https://www.go-fair.org/fair-principles/"&gt;FAIR principles&lt;/a&gt; of being Findable, Accessible, Interoperable and Reusable.&lt;/p&gt; &lt;p&gt;This makes Zenodo more FAIR-compliant than Wikimedia Commons. Although all uploads get their own unique persistent M-identifiers (so-called Concept URIs, such as &lt;a href="https://commons.wikimedia.org/entity/M144836996"&gt;https://commons.wikimedia.org/entity/M144836996&lt;/a&gt;), these play a less manifest and significant role than their DOI equivalents in Zenodo. Multilingual findability is limited by the English-oriented &lt;a href="https://commons.wikimedia.org/wiki/Commons:Categories"&gt;category names&lt;/a&gt; used to group files.&lt;/p&gt; &lt;p&gt;On the positive side, metadata of each upload is indexed and searchable via the Wikimedia Commons search engine immediately after publishing. Additionally, all files and their metadata can be requested for free via a set of &lt;a href="https://www.mediawiki.org/wiki/API"&gt;REST-API&lt;/a&gt;s without the need for a user account.&lt;/p&gt; &lt;p&gt;However, interoperability is non-ideal as Commons uses metadata standards that are not necessarily compatible with ontologies in the cultural heritage and humanities domains. Also Commons does not offer support for standards like IIIF, although &lt;a href="https://commons.wikimedia.org/wiki/Commons:International_Image_Interoperability_Framework"&gt;some attempts&lt;/a&gt; have been made in the past. All Commons files can be reused because open (Creative Commons) licenses are mandatory.&lt;/p&gt; &lt;p&gt;Finally, thanks to the &lt;a href="https://commons.wikimedia.org/wiki/Commons:Structured_data"&gt;Structured Data on Commons&lt;/a&gt; effort, Wikidata has been integrated into Commons. This means all &lt;a href="https://ipres2019.org/static/pdf/iPres2019_paper_135.pdf"&gt;FAIR strongpoints of Wikidata&lt;/a&gt; &lt;em&gt;(“Wikidata fulfills the most complete degree of FAIRness”&lt;/em&gt;) are now exposed to Commons as well.&lt;/p&gt; &lt;p&gt;As for SlideShare, it is a purely presentation-oriented and visual-first environment, with no explicit attention to being FAIR. It does for instance not use unique and persistent identifiers for its uploads, nor does it offer rich and explicit metadata for them. Publications are not linked to open, external vocabularies, and you will need to have an account to be able to download content and their (very basic) metadata.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="image-alignment--text-image"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="row flex-start order"&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;strong&gt;7) Durability for files, governance and funding: &lt;/strong&gt;Zenodo was launched in May 2013 and is hosted as an embedded &lt;a href="https://home.cern/news/news/computing/cern-software-become-central-hub-eu-research"&gt;service of CERN&lt;/a&gt;, which has existed for 70 years and currently has programs defined for the next 20+ years. Files are stored with &lt;a href="https://about.zenodo.org/policies/"&gt;longevity&lt;/a&gt; as a primary focus. &lt;a href="https://about.zenodo.org/infrastructure/"&gt;Additional checks and balances&lt;/a&gt; with respect to the infrastructure, servers, storage, security, governance, financing, and legal status all contribute to future-proofing the repository.&lt;/p&gt; &lt;p&gt;This is at least on par with the sustainability of Wikimedia Commons, which has been in operation for 20 years now. It is part of the &lt;a href="https://wikimediafoundation.org/"&gt;Wikimedia Foundation&lt;/a&gt; portfolio, and as such, is funded and governed by the &lt;a href="https://foundation.wikimedia.org/wiki/Home"&gt;overall policies&lt;/a&gt; of the Wikimedia movement, with durability, transparency, openness and reliability at its core. Long-term funding of its projects is secured by the &lt;a href="https://wikimediaendowment.org/"&gt;Wikimedia Endowment&lt;/a&gt;, aiming to support Wikimedia projects in perpetuity.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="col-xs-12 col-md-6"&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-hidden field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/cern_logo2.png?itok=vCJpeCNp" width="460" height="439" alt="CERN logo (white background with blue lined circles)"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;As for SlideShare, it is operated by &lt;a href="https://www.scribd.com/home"&gt;Scribd&lt;/a&gt;, a U.S.-based privately owned company funded by &lt;a href="https://en.wikipedia.org/wiki/Scribd#Financials" data-wp-title="Scribd#Financials" data-wp-lang="en"&gt;venture capital&lt;/a&gt;. Obviously, this is not an ideal situation to ensure long term accessibility of content hosted on SlideShare. This was another reason to migrate my content from there onto Zenodo.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;8) Contributing to international research: &lt;/strong&gt;The KB is a scientific organization and, as such, part of the international science and research communities. As an employee of such an institution, Zenodo allows me to automatically integrate my publications into scholarly aggregators, such as &lt;a href="https://orcid.org/0000-0002-9058-9941"&gt;ORCID&lt;/a&gt;, &lt;a href="https://commons.datacite.org/orcid.org/0000-0002-9058-9941"&gt;DataCite&lt;/a&gt;, &lt;a href="https://explore.openaire.eu/search/advanced/research-outcomes?f0=authorid&amp;amp;fv0=0000-0002-9058-9941"&gt;OpenAIRE&lt;/a&gt;, &lt;a href="https://www.base-search.net/Search/Results?lookfor=olaf+Janssen+koninklijke+bibliotheek&amp;amp;type=allus&amp;amp;page=1&amp;amp;l=en&amp;amp;oaboost=1&amp;amp;refid=dcpageen"&gt;BASE&lt;/a&gt; or &lt;a href="https://search.fid-benelux.de/Search/Results?lookfor=%22Olaf+Janssen%22&amp;amp;type=Author"&gt;FID Benelux&lt;/a&gt;, making them more visible for study and research purposes, without any extra effort on my part.&lt;/p&gt; &lt;p&gt;Both Wikimedia Commons and SlideShare are not well integrated into academic workflows and don’t have strong user bases in the scholarly community. By exposing my Wikimedia-related publications to this target group, I hope to raise more awareness of the benefits that Wikimedia can bring to their fields of work.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/OPENaire_OlafJanssen.png?itok=xCirh8bS" width="1023" height="858" alt="Screenshot of an OpenAIRE Explore environment"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Screenshot of the author’s publications as listed in OpenAIRE on 22 August 2024. All records were automatically imported from Zenodo, based on the &lt;/em&gt;&lt;a href="https://orcid.org/0000-0002-9058-9941"&gt;&lt;em&gt;ORCID of the author&lt;/em&gt;&lt;/a&gt;&lt;em&gt;. (&lt;/em&gt;&lt;a href="https://explore.openaire.eu/search/advanced/research-outcomes?f0=authorid&amp;amp;fv0=0000-0002-9058-9941"&gt;&lt;em&gt;Source of image&lt;/em&gt;&lt;/a&gt;&lt;em&gt;).&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;strong&gt;9) Fully hosted on EU-based servers:&lt;/strong&gt; Zenodo is powered by the &lt;a href="https://home.cern/science/computing/data-centre"&gt;CERN Data Centre&lt;/a&gt;, physically located in France. This means it is subject to CERN’s legal status as an intergovernmental organization with immunity from the jurisdictions of the nation courts of the EU Member States (&lt;a href="https://about.zenodo.org/infrastructure/"&gt;source&lt;/a&gt;). This effectively safeguards Zenodo from being taken down due to legal procedures initiated by hostile agents.&lt;/p&gt; &lt;p&gt;Although Wikimedia Commons &lt;a href="https://wikitech.wikimedia.org/wiki/Data_centers"&gt;runs in data centers&lt;/a&gt; partly located in the EU (Amsterdam and Marseille), the platform legally falls under U.S. jurisdiction, as its operator, the Wikimedia Foundation, is a nonprofit public charity under U.S. law.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;10) The REST API and OAI-PMH interface &lt;/strong&gt;allow for programmatic interactions with my publications. In accordance with the &lt;a href="https://collectionsasdata.github.io/"&gt;Collections as Data&lt;/a&gt; initiative, these APIs allow me to expose my “Publications as Data”, supporting computationally-driven sharing, research and teaching.&lt;/p&gt; &lt;p&gt;Zenodo’s &lt;a href="https://developers.zenodo.org/#rest-api"&gt;REST API&lt;/a&gt; allows publication metadata to be requested directly in JSON format (&lt;a href="https://zenodo.org/api/records/7665231"&gt;example&lt;/a&gt;) that can be processed further via Python and other languages. For instance, with only a few lines of code, you can request all my publications &lt;a href="https://public-paws.wmcloud.org/19781798/zenodo_records_olafjanssen_16082024.xlsx"&gt;as an Excel file&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;Via Zenodo’s &lt;a href="https://zenodo.org/oai2d?verb=Identify"&gt;OAI-PMH interface&lt;/a&gt;, all publications in the &lt;a href="https://zenodo.org/communities/kbnl/records?q=&amp;amp;l=list&amp;amp;p=1&amp;amp;s=10&amp;amp;sort=newest"&gt;KB community&lt;/a&gt; can be requested in &lt;a href="https://zenodo.org/oai2d?verb=ListMetadataFormats"&gt;various metadata formats&lt;/a&gt;, including the library-oriented &lt;a href="https://zenodo.org/oai2d?verb=ListRecords&amp;amp;metadataPrefix=oai_dc&amp;amp;set=user-kbnl"&gt;OAI_DC&lt;/a&gt; or &lt;a href="https://zenodo.org/oai2d?verb=ListRecords&amp;amp;metadataPrefix=marc21&amp;amp;set=user-kbnl"&gt;MARC21&lt;/a&gt; schemes. This protocol is used by the scholarly aggregators listed in point 8) to ingest KB publications into their repositories.&lt;/p&gt; &lt;p&gt;As for Wikimedia Commons, the MediaWiki software used by this platform offers a set of rich and free &lt;a href="https://www.mediawiki.org/wiki/API"&gt;REST-API&lt;/a&gt;s allowing for a wide range of machine interactions with my publications. Furthermore, thanks to the &lt;a href="https://commons.wikimedia.org/wiki/Commons:Structured_data"&gt;Structured Data on Commons&lt;/a&gt; effort, all my publications will soon be available as Linked Open Data that can be queried via the &lt;a href="https://commons.wikimedia.org/wiki/Commons:SPARQL_query_service"&gt;Wikimedia Commons SPARQL service&lt;/a&gt;. Unfortunately, Commons does not offer an OAI-PMH interface.&lt;/p&gt; &lt;p&gt;SlideShare &lt;a href="https://www.linkedin.com/blog/engineering/archive/introducing-slideshare-api-explorer"&gt;used to have&lt;/a&gt; a REST API, but it seems to have been &lt;a href="https://groups.google.com/g/slideshare-developers"&gt;inactive for several years&lt;/a&gt; now.&lt;/p&gt; &lt;h3&gt;Downsides of Zenodo&lt;/h3&gt; &lt;p&gt;Given all these positive features, you might think there are no downsides to sharing your presentations, articles, tutorials, and other publications via Zenodo. Well, of course there are! Coming from SlideShare and Wikimedia Commons backgrounds, three drawbacks of Zenodo I’ve personally encountered are:&lt;/p&gt; &lt;p&gt;&lt;strong&gt;1) Zenodo does not have a vivid community&lt;/strong&gt;. One of the very uniqe features of Wikimedia Commons is its very vivid community. It means &lt;a href="https://commons.wikimedia.org/wiki/Commons:Tools"&gt;tools&lt;/a&gt;, events, meetings, &lt;a href="https://commons.wikimedia.org/wiki/Commons:Help_desk"&gt;help desk&lt;/a&gt;, &lt;a href="https://commons.wikimedia.org/wiki/Commons:Village_pump"&gt;village pump&lt;/a&gt;, &lt;a href="https://commons.wikimedia.org/wiki/Commons:Discussion_pages"&gt;discussions&lt;/a&gt;, documentation, and &lt;a href="https://commons.wikimedia.org/wiki/Commons:Community_portal"&gt;all other things&lt;/a&gt; Wikimedians have collectively created to make Commons such a valuable a &lt;a href="https://en.wikipedia.org/wiki/Social_machine?wprov=wppw2"&gt;social machine&lt;/a&gt;. Zenodo lacks such a group of external contributors advancing and supporting its development.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/Wikiman%C3%ADa_d%C3%ADa_4_-_PK_-_19.jpg?itok=ixBjGLWb" width="1024" height="768" alt="Screenshot of a lot of smiling people at a congres. All have keycards around their necks."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Group of Wikimedians during Wikimania 2024. &lt;/em&gt;&lt;a href="https://commons.wikimedia.org/wiki/File:Wikiman%C3%ADa_d%C3%ADa_4_-_PK_-_19.jpg"&gt;&lt;em&gt;Source&lt;/em&gt;&lt;/a&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;strong&gt;2) Zenodo is not well known among regular web users&lt;/strong&gt;, as it is not part of the mainstream internet. Compared to SlideShare, still &lt;a href="https://www.semrush.com/website/slideshare.net/overview/"&gt;ranked in the top 600&lt;/a&gt; of most visited websites worldwide, Zenodo is &lt;a href="https://www.semrush.com/website/zenodo.org"&gt;far more long-tail&lt;/a&gt; and niche (ranked 55K+). This lowers the chances for my publications to be spontaneously discovered via search engines or social media by general web users.&lt;/p&gt; &lt;p&gt;This disadvantage is however mitigated by my publications also being available on Wikimedia Commons, which has a much better exposure to search engines compared to Zenodo. This makes my presentations findable outside the scientific communication and publication channels.&lt;/p&gt; &lt;p&gt;Furthermore, most of my content is not aimed at the general public, but rather at professional, specialized target groups, including library and digital heritage professionals, data-oriented scholars (digital humanities), and the Wikimedia communities. These types of users will probably be more likely to visit Zenodo (and Wikimedia Commons) than SlideShare when looking for this sort of content.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;3) Zenodo does not offer a visual-first user experience. &lt;/strong&gt;This is especially apparent when looking at how search results for the query “koninklijke bibliotheek” are displayed on SlideShare versus Zenodo. The &lt;a href="https://www.slideshare.net/search?q=koninklijke+bibliotheek"&gt;default gallery view&lt;/a&gt; used by SlideShare is visually more appealing than the &lt;a href="https://zenodo.org/search?q=koninklijke%20bibliotheek&amp;amp;l=list&amp;amp;p=1&amp;amp;s=10&amp;amp;sort=bestmatch"&gt;text-oriented display&lt;/a&gt; of Zenodo’s results.&lt;/p&gt; &lt;p&gt;For the publications themselves, a &lt;a href="https://www.slideshare.net/slideshow/ing-huygens-delpherdata20140107ojforupload/29730483?from_search=2"&gt;typical SlideShare page&lt;/a&gt; offers a much stronger visual-first experience than a &lt;a href="https://zenodo.org/records/12569311"&gt;typical Zenodo record&lt;/a&gt; page, which contains much more manifest textual (metadata) elements.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/zenodo-textual.png?itok=mZj4FifA" width="797" height="883" alt="Zenodo screenshot showing the result for searching on 'koninklijke bibliotheek'. The search results are all about Wikipedia and written by Olf Janssen."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;For the query “koninklijke bibliotheek” the text-oriented &lt;/em&gt;&lt;a href="https://zenodo.org/search?q=koninklijke%20bibliotheek&amp;amp;l=list&amp;amp;p=1&amp;amp;s=10&amp;amp;sort=bestmatch"&gt;&lt;em&gt;search results on Zenodo&lt;/em&gt;&lt;/a&gt;&lt;em&gt; do not offer the same visual-first user experience as the &lt;/em&gt;&lt;a href="https://www.slideshare.net/search?q=koninklijke+bibliotheek"&gt;&lt;em&gt;same query on SlideShare&lt;/em&gt;&lt;/a&gt;&lt;em&gt;.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;Of course, these differences are hardly surprising because Zenodo was built as a scientific data-focused service, giving metadata the same (or even higher) priority as the object. But for users coming from the visual-first background of SlideShare, where most textual metadata is rather hidden, the differences are striking.&lt;/p&gt; &lt;p&gt;Fortunately, using its REST API and some Python code, it would be very feasible to generate a thumbnail gallery view for all my publications in Zenodo, mimicking the &lt;a href="https://commons.wikimedia.org/wiki/GLAM_at_Koninklijke_Bibliotheek/Archive"&gt;KB Wikimedia presentations &amp;amp; publications archive&lt;/a&gt; discussed at the start of this article.&lt;/p&gt; &lt;h3&gt;Summary and conclusion&lt;/h3&gt; &lt;p&gt;In this article, I describe my journey in transitioning from SlideShare to Zenodo for hosting and sharing my professional Wikimedia-related content, while continuing to maintain KB’s presence on Wikimedia Commons.&lt;/p&gt; &lt;p&gt;As my publishing requirements evolved over time, the need for a more robust, versatile, and research-oriented platform became clear. While SlideShare initially met my basic needs for visibility and discoverability, its limitations—such as a narrow selection of file formats, lack of advanced metadata support, and concerns about long-term accessibility—prompted me to look for a better alternative.&lt;/p&gt; &lt;p&gt;Zenodo emerged as the optimal choice due to its EU-based hosting, support for a wide range of file types, and strong alignment with the FAIR principles of data management. The platform’s ability to mint DOIs, manage large files, and integrate with academic repositories, along with its multi-level sustainability and machine interaction capabilities, significantly enhances the discoverability and reuse of my work within the international research community.&lt;/p&gt; &lt;p&gt;Despite some drawbacks, such as the lack of a vivid community and its less visual-first user experience compared to SlideShare, Zenodo’s strengths in durability, flexibility, and scholarly integration far outweigh these concerns.&lt;/p&gt; &lt;p&gt;In conclusion, Zenodo, in conjunction with Wikimedia Commons, provides a powerful and sustainable solution for managing and disseminating my professional outputs. By utilizing both platforms synergistically, I can ensure that my work remains accessible, reusable, and impactful for a diverse range of audiences, from general web users to specialized academic communities.&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Mon, 09 Sep 2024 13:46:52 +0200</pubDate> <dc:creator>Iris.Geldermans@KB.nl</dc:creator> <guid isPermaLink="false">391 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>Link analysis sample set</title> <link>https://lab.kb.nl/dataset/link-analysis-sample-set</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;em&gt;In 2022 and 2023 two researchers started working with the KB web collection for the first time in the history of our web collection. This triggered the need for analysing the web-data within the WARC container files we hold. The result of this: datasets with hyperlinks. On this page you can find an example of the kind of dataset we used for their research. As example a kb.nl harvest was used.&amp;nbsp;&lt;/em&gt;&lt;/p&gt; &lt;h3&gt;Analysing hyperlinks in the KB web collection&lt;/h3&gt; &lt;p&gt;The first time extracting hyperlinks was done by myself in preparation for the arrival of Researcher in Residence &lt;a href="https://lab.kb.nl/person/dr-karin-de-wild" data-entity-type="node" data-entity-uuid="76b60cac-3632-4e22-ba94-235767efc94d" data-entity-substitution="canonical" title="Dr. Karin de Wild "&gt;Karin the Wild&lt;/a&gt; back in 2022. You can read how I extracted the hyperlinks and worked with them in Gephi in the blog series ‘&lt;a href="https://lab.kb.nl/about-us/blog/analysing-hyperlinks-kb-web-collection" data-entity-type="node" data-entity-uuid="b0fa4f08-d7b6-47c2-9a57-5889c49e886e" data-entity-substitution="canonical" title="Analysing hyperlinks in the KB web collection"&gt;Analysing hyperlinks in the KB web collection&lt;/a&gt;’.&amp;nbsp;&lt;/p&gt; &lt;p&gt;I learned a lot from this first experiment. The main thing I discovered was that I wanted to have the tags as well as the hyperlink in my dataset. They tell a lot about the type of hyperlink you extract and are needed if you want to do a thorough analysis. I also learned that the way you crop your hyperlink is &lt;a href="https://lab.kb.nl/about-us/blog/wait-where-did-hyves-go-link-analysis-part-4" data-entity-type="node" data-entity-uuid="01e229d2-61af-48f3-91f0-4877c4c9688b" data-entity-substitution="canonical" title="Wait... Where did Hyves go?! - Link analysis part 4"&gt;very important for the outcome of your hyperlink analysis&lt;/a&gt;. I took those experiences and used them when &lt;a href="https://lab.kb.nl/person/jesper-verhoef" data-entity-type="node" data-entity-uuid="3d017eef-e63a-4571-a022-028e878e7d82" data-entity-substitution="canonical" title="Jesper Verhoef"&gt;Jesper Verhoef&lt;/a&gt; became our Researcher in Residence in 2023. Changes to our original extraction script improved the dataset.&amp;nbsp;&lt;/p&gt; &lt;blockquote&gt;&lt;p&gt;Fast forward to the end of 2022 and&amp;amp;nbsp;&amp;lt;/em&amp;gt;&amp;lt;a href="&lt;a href="https://www.kb.nl/en/news/kbs-xs4all-web-collection-unesco-world-heritage-list"&gt;https://www.kb.nl/en/news/kbs-xs4all-web-collection-unesco-world-heritage-list&lt;/a&gt;"&amp;gt;&amp;lt;em&amp;gt;this collection was recognized as UNESCO heritage&amp;lt;/em&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;em&amp;gt;. But… Was Kees right?&amp;nbsp;&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;&lt;em&gt;Example how a hyperlink is embedded in a website (and therefore in a WARC file). Source: &lt;/em&gt;&lt;a href="https://lab.kb.nl/about-us/blog/no-longer-xs4all" data-entity-type="node" data-entity-uuid="d3ec2356-bfe2-4c62-8bdd-d68fbaee0b44" data-entity-substitution="canonical" title="No longer XS4ALL"&gt;&lt;em&gt;No Longer XS4ALL&lt;/em&gt;&lt;/a&gt;&lt;em&gt;.&amp;nbsp;&lt;/em&gt;&lt;/p&gt; &lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;h3&gt;The dataset&lt;/h3&gt; &lt;p&gt;For those interested I made a sample set based on a crawl from the website of kb.nl:&lt;/p&gt; &lt;table&gt; &lt;tbody&gt; &lt;tr&gt; &lt;td&gt;Target Instance ID&lt;/td&gt; &lt;td&gt;38712298&lt;/td&gt; &lt;td&gt;&amp;nbsp;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;Target Name&lt;/td&gt; &lt;td&gt;Koninklijke Bibliotheek&lt;/td&gt; &lt;td&gt;&amp;nbsp;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;Schedule start&lt;/td&gt; &lt;td&gt;06/07/2024 18:57:00&lt;/td&gt; &lt;td&gt;&amp;nbsp;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;URLs downloaded&lt;/td&gt; &lt;td&gt;175.115&lt;/td&gt; &lt;td&gt;limit: 700.000&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;Data downloaded&lt;/td&gt; &lt;td&gt;21.03 GB&lt;/td&gt; &lt;td&gt;limiet: 50 GB&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;Elapsed time&lt;/td&gt; &lt;td&gt;12:14:54:33&lt;/td&gt; &lt;td&gt;&amp;nbsp;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;Seeds&lt;/td&gt; &lt;td&gt; &lt;p&gt;&lt;a href="https://inschrijven.kb.nl/"&gt;https://inschrijven.kb.nl/&lt;/a&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;&lt;a href="https://galerij.kb.nl/"&gt;https://galerij.kb.nl/&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href="https://www.kb.nl/"&gt;&lt;strong&gt;https://www.kb.nl/&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;a href="https://collecties.kb.nl/"&gt;https://collecties.kb.nl/&lt;/a&gt;&lt;/p&gt; &lt;/td&gt; &lt;td&gt;&lt;strong&gt;Bold = primary seed&lt;/strong&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;Excluded from harvest&lt;/td&gt; &lt;td&gt; &lt;p&gt;.*field_categories.*&lt;/p&gt; &lt;p&gt;&lt;a href="http://acroeng.adobe.com/"&gt;http://acroeng.adobe.com/&lt;/a&gt;.*&lt;/p&gt; &lt;p&gt;.*f%5B0%5D=.*&lt;/p&gt; &lt;p&gt;.*\.rss.*&lt;/p&gt; &lt;p&gt;^[^/]+://[^/]*(youtube).*&lt;/p&gt; &lt;p&gt;^[^/]+://[^/]*(facebook).*&lt;/p&gt; &lt;p&gt;^[^/]+://[^/]*(google).*&lt;/p&gt; &lt;/td&gt; &lt;td&gt;&amp;nbsp;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;strong&gt;Important to note&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;&lt;strong&gt;Harvest finished by operator&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;&amp;nbsp;&lt;/td&gt; &lt;/tr&gt; &lt;/tbody&gt; &lt;/table&gt; &lt;p&gt;&lt;em&gt;Table 1. Metadata from the kb.nl harvest.&lt;/em&gt;&lt;/p&gt; &lt;p&gt;This target has four seeds, but the harvest was cut short by a quality assurance officer. This means only a part of the selected seeds were harvested. Because kb.nl is the primary seed, the harvester started with that seed and did not come around to the other before it was manually stopped.&amp;nbsp;&lt;/p&gt; &lt;h3&gt;Result&lt;/h3&gt; &lt;p&gt;You can find the whole dataset in csv under the ‘examples’ tab. But here (table 1) is a little sneak peek. In the datasets I used you first have the ‘source’ website: the website on which the link was found. After this comes the ‘target’: the website to which the link refers. The third column is the weight: how many times the source website refers to the ‘target’ website. Lastly we have the type of URL. As mentioned above in the beginning this was only anchor or embedded. After updating the extraction script we now find the specific tag which surrounds the link. In the KB dataset it is mostly ‘a’ for anchor link. But you can also find some images and frames in there.&amp;nbsp;&lt;/p&gt; &lt;table&gt; &lt;tbody&gt; &lt;tr&gt; &lt;td&gt;&lt;strong&gt;Source&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;&lt;strong&gt;Target&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;&lt;strong&gt;Weight&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;&lt;strong&gt;Type_URL_v2&lt;/strong&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;strong&gt;kb.nl&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;webggc.oclc.org&lt;/td&gt; &lt;td&gt;167154&lt;/td&gt; &lt;td&gt;a&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;strong&gt;kb.nl&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;collecties.kb.nl&lt;/td&gt; &lt;td&gt;166452&lt;/td&gt; &lt;td&gt;a&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;strong&gt;kb.nl&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;youtube.com&lt;/td&gt; &lt;td&gt;166288&lt;/td&gt; &lt;td&gt;a&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;strong&gt;kb.nl&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;delpher.nl&lt;/td&gt; &lt;td&gt;155586&lt;/td&gt; &lt;td&gt;a&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;strong&gt;kb.nl&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;webwinkel.kb.nl&lt;/td&gt; &lt;td&gt;152806&lt;/td&gt; &lt;td&gt;a&lt;/td&gt; &lt;/tr&gt; &lt;/tbody&gt; &lt;/table&gt; &lt;p&gt;&lt;em&gt;Table 2. Example of the data found inside the kb.nl_2024_links dataset.&lt;/em&gt;&lt;/p&gt; &lt;p&gt;&lt;em&gt;It is important to note that this dataset does not reflect the kb.nl website as a whole. As mentioned above the harvest was stopped manually. But even if the harvest was completed, it only shows what we have been managed to archive with Heritrix and WCT and what we managed to extract with our &lt;/em&gt;&lt;a href="https://lab.kb.nl/about-us/blog/lets-get-some-data-link-analysis-part-1" data-entity-type="node" data-entity-uuid="4718eb88-9a98-4fac-931f-e603e088639a" data-entity-substitution="canonical" title="Let's get some data - Link analysis part 1"&gt;&lt;em&gt;WARC-link-extraction script&lt;/em&gt;&lt;/a&gt;&lt;em&gt;.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/kb.nl_most_linked.png?itok=KJacxW0r" width="1024" height="521" alt="Link web with kb.nl referring to a number of other websites. Some lines are thicker because kb.nl refers to them more often"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Figure 1: Example of what you can do with the dataset. In this case it shows the websites kb.nl most often refers to.&amp;nbsp;&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Tue, 27 Aug 2024 12:41:02 +0200</pubDate> <dc:creator>Iris.Geldermans@KB.nl</dc:creator> <guid isPermaLink="false">390 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>No longer XS4ALL</title> <link>https://lab.kb.nl/about-us/blog/no-longer-xs4all</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;em&gt;Early 2019 former conservator Digital Born Collections Kees Teszelszsky raised the alarm: XS4ALL websites were at significant risk of disappearing from the live web. The cause? KPN announced the end of its subsidiary company XS4ALL. Multiple colleagues within the KB (myself included) rose to the challenge and started archiving these websites under supervision of a collection specialist. Fast forward to the end of 2022 and&amp;nbsp;&lt;/em&gt;&lt;a href="https://www.kb.nl/en/news/kbs-xs4all-web-collection-unesco-world-heritage-list"&gt;&lt;em&gt;this collection was recognized as UNESCO heritage&lt;/em&gt;&lt;/a&gt;&lt;em&gt;. But… Was Kees right? What happened to the XS4ALL websites on the live web? Join me as I investigate how the collection quietly started disappearing from the live web.&lt;/em&gt;&lt;/p&gt; &lt;p&gt;I started looking into the XS4ALL websites in June 2023. The reason was that a colleague pointed out that KPN announced that&amp;nbsp;&lt;a href="https://www.kpn.com/service/homepages.htm"&gt;it would stop hosting ‘home. kpn .nl’ pages&lt;/a&gt;. This reminded me of the XS4ALL domain it also hosts. As I was involved in building the collection I was interested in what had happened to it on the live web, so I started investigating.&lt;/p&gt; &lt;h3&gt;&lt;em&gt;Do we still archive it?&lt;/em&gt;&lt;/h3&gt; &lt;p&gt;First I checked how the collection was build and whether it was being archived by us. As of June 2023 the collection comprised 3.261 websites. Because the KB has a selective collection each website has its own database entry called a Target Record. This is why counting which ones are still active is an easy process. The collection was built during 2019/2020, with most websites archived in 2021 (graph 1). After that year the active portion of the collection started to dimmish a little. This is because of our QA process: when a website is no longer online the Target Record will be closed and the website is no longer harvested. Within 2021 and 2022 84 websites had been closed. Not that much considering the thousands we had archived. So far so good.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/Graph%20archived%20websites.png?itok=BzOTsMAW" width="746" height="411" alt="Line Graph showing a steep growth in XS4ALL website in the KB collection with a little dip at the end."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Graph&amp;nbsp;1: Number of XS4ALL websites archived by the KB.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;&lt;em&gt;What is actually archived?&lt;/em&gt;&lt;/h3&gt; &lt;p&gt;Next I had a look at the harvest results. Because we have a selective archive, where we archive one website at a time, I can also easily check the metadata of the harvest result. For instance I can check the amount of bytes harvested. This is one of the criteria we use for our web collections quality assurance (QA). Four years of performing QA has taught our team that when a website is smaller than 1 MB, it should be checked whether it is still online. In these cases it is likely that the website is either offline or it has been migrated to another domain. However, this parameter applies to current &lt;strong&gt;modern&lt;/strong&gt; websites. XS4ALL websites are much older, mostly dating from 1993 until – 2005, and therefore smaller. Sometimes the website only consists of one or two pages! This is why for the XS4ALL websites I maintained a limit of 1 KB for QA. In this case (as experience teaches us) it is 99% likely to be offline. I plotted the results in a graph, and started getting worried…&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/Graph%20harvestresults.png?itok=-v3p0z0s" width="841" height="551" alt="Bar chart showing 4 bars with a little red and a lot of green. The last bar is 60 percent red."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Graph 2: The websites which are probably offline (smaller than 1 KB) have been coloured red. The websites which are probably still online (larger than 1 KB) have been coloured green. This graph was made in percentages of the total instead of absolute numbers so a comparison between years was possible.&amp;nbsp;&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;I found the difference between 2019/2020 and 2021/2022 already pretty notable. The number of unsuccessful harvests increased significantly (in percentages). But in first 6 months of 2023 &lt;strong&gt;more than&lt;/strong&gt; &lt;strong&gt;half of the harvested websites failed to harvest successfully.&amp;nbsp;&lt;/strong&gt;In absolute numbers this is about a third of the whole collection. I verified this on the live web and found that 95% of the websites with less than 1 KB harvested were indeed gone.&lt;/p&gt; &lt;h3&gt;&lt;em&gt;Logfiles: Http(s) response code&lt;/em&gt;&lt;/h3&gt; &lt;p&gt;End 2023/early 2024 we received a research proposal to study our XS4ALL collection. To assist the researcher I returned to this project after a short break. Up until this moment I was only looking into metadata from our web archiving software the&amp;nbsp;&lt;a href="https://webcuratortool.org/"&gt;Web Curator Tool&lt;/a&gt; but I felt this was not enough to aid the researcher in understanding the quality of our XS4ALL collection. As I had determined: a lot of websites were still being harvested while they were no longer online. I pondered if it was possible to get a better picture of the quality of each harvest.&lt;/p&gt; &lt;p&gt;A colleague of mine had (on my request) previously examined a group of almost 19.000 XS4ALL homepages on the live web. From this group almost 55% returned the well-known 404 (Page not found) response matching my conclusions based on the metadata of 2023. This inspired me: what if we could get the status response from the WARC-files (where the actual archived data is stored)? This would give us a better view of the state of a website during harvesting!&lt;/p&gt; &lt;p&gt;Once again I turned to a teammate of mine and told him of my ideas. For practical reasons we used the logfiles (the crawl.log) of crawler Heritrix instead of the WARC files. My colleague created a list with all harvested URLs from the XS4ALL collection based on WCT data. Next he extracted the first 20 lines of the craw.log, where the response code was found, and matched it against the URL’s from the WCT data. Now we had the response code of every harvested URL for each archived version! With these results I could once again analyse the quality of the collection.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/Graph%20responce%20codes%20v2.png?itok=rLgUm8o6" width="906" height="657" alt="Bar chart showing 3 bars with a lot of green. the fourth bar is 60 percent green, 15 percent yellow en 15 percent shades of red. The last bar is more or less 55 percent red and 45 percent green."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Graph 3: Overview of all found http response codes. Green being websites that still existed, other colours are websites that had either moved or were not reachable.&amp;nbsp;&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;&lt;em&gt;Page not found…..&lt;/em&gt;&lt;/h3&gt; &lt;p&gt;So again: in 2019/2020 everything was fine. Most of the websites were successfully harvested. This is important as it was the period where most websites were harvested for the first time as we were building the collection. In 2021 serious problems began to emerge: about 10% of the URL’s returned a 403 – forbidden response, meaning the website was inaccessible. In 2022 the problems became more severe and diverse. Almost 40% of the websites were not harvested because of multiple http response states. Besides a 403 response, websites started vanishing due to a 404 (not found) or a 302 (temporary moved) response. The 302 response was an interesting one. Close reading of this group revealed that when the domain was a x.home.xs4all.nl/ URL, it usually redirected to a &lt;a href="https://www.xs4all.nl/unknownuser/xs4all/x"&gt;https://www.xs4all.nl/unknownuser/xs4all/x&lt;/a&gt; URL. You then got the page: ‘Oops, page not found’ 404 page from the main XS4ALL website.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/XS4ALL%20unknownuser%20pagina.png?itok=UEpozPhY" width="1300" height="880" alt="Webpage in KB webarchive Wayback Machine: XS4ALL website with the text 'Oeps... pagina niet gevonden. 404 - de pagina bestaat niet meer of heeft u misschien een typefout gemaakt?&amp;quot;"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Screenshot 1: Screenshot of a XS4ALL website May 2022. The website redirects to a page which states that the website is no longer online. Made from the KB Wayback Machine.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;By 2023, the collection's state on the live web significantly deteriorated. The websites on the live web which were unreachable in 2022 (because of the 302 and 403) now returned the general 404 – Not Found response code. Marking the end of the websites. More than half of the websites we tried to harvest had disappeared from the live web.&amp;nbsp;&lt;/p&gt; &lt;h3&gt;&lt;em&gt;But…. Why?&lt;/em&gt;&lt;/h3&gt; &lt;p&gt;What could be the reason for the disappearance of these website? Is KPN responsible? Since 2022 KPN has been integrating XS4ALL in its own infrastructure. Starting from 2023&amp;nbsp;&lt;a href="https://www.kpn.com/service/xs4all-overzicht.htm"&gt;XS4ALL began using KPN technology&lt;/a&gt; and from then on creating a new XS4ALL homepage became impossible. This aligns with KPN's cessation of hosting its homepages&amp;nbsp;(http:// home. kpn .nl/ websites). Or is it because of the new competitor, “Freedom Internet”? Founded on November 11, 2019, in response to KPN's takeover of XS4ALL, customers might have moved there, ending their XS4ALL accounts.&lt;/p&gt; &lt;p&gt;Whatever the reason: I am very happy that Kees sounded the alarm back in 2019. Because even though many websites are now disappearing from the live web, the KB still has an extensive collection of XS4ALL websites safely stored in its archive.&amp;nbsp;&lt;/p&gt; &lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;h3&gt;&lt;em&gt;Related research&lt;/em&gt;&lt;/h3&gt; &lt;p&gt;&lt;strong&gt;When Online Content Disappears&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;em&gt;38% of webpages that existed in 2013 are no longer accessible a decade later &amp;amp; Methodology&lt;/em&gt;&lt;/p&gt; &lt;p&gt;By Athena Chapekis, Samuel Bestvater, Emma Remy and Gonzalo Rivero.&amp;nbsp;&lt;/p&gt; &lt;p&gt;&lt;a href="https://www.pewresearch.org/data-labs/2024/05/17/when-online-content-disappears/"&gt;https://www.pewresearch.org/data-labs/2024/05/17/when-online-content-di…&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;a href="https://www.pewresearch.org/data-labs/2024/05/17/methodology-link-rot/"&gt;https://www.pewresearch.org/data-labs/2024/05/17/methodology-link-rot/&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Thu, 25 Jul 2024 15:24:01 +0200</pubDate> <dc:creator>Iris.Geldermans@KB.nl</dc:creator> <guid isPermaLink="false">381 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>Continuing the pop-up and movable books research </title> <link>https://lab.kb.nl/about-us/blog/continuing-pop-and-movable-books-research</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;In&amp;nbsp;&lt;a href="https://lab.kb.nl/about-us/blog/experiencing-pop-and-movable-books-through-mixed-reality-technology"&gt;my previous blog post&lt;/a&gt;, I introduced my research project, on characterising the materials experience of pop-up and movable books, and designing digitally-mediated interactions with their digital representations. In this post, I will give an update on all activities since the last post. Best news is that our paper describing this research, has since been accepted and was presented last week at world’s largest and peer-reviewed human-computer interaction conference, called CHI (pronounced ‘kai’). The full paper (describing the complete research project), can be found&amp;nbsp;&lt;a href="https://doi.org/10.1145/3613904.3642142"&gt;here&lt;/a&gt;, and be referred to as follows:&lt;/p&gt; &lt;p&gt;&lt;em&gt;Willemijn S. Elkhuizen, Jeff Love, Stefano Parisi, and Elvin Karana.&amp;nbsp;2024. On the Role of Materials Experience for Novel Interactions with Digital Representations of Historical Pop-up and Movable Books. In Proceedings of the CHI Conference on Human Factors in Computing Systems (CHI '24). Association for Computing Machinery, New York, NY, USA, Article 619, 1–18.&amp;nbsp;&lt;/em&gt;&lt;a href="https://doi.org/10.1145/3613904.3642142"&gt;&lt;em&gt;https://doi.org/10.1145/3613904.3642142&lt;/em&gt;&lt;/a&gt;&lt;/p&gt; &lt;p&gt;The paper provided many details on the conducted case study, but here I will describe the process (hopefully) in a bit more accessible fashion here.&lt;/p&gt; &lt;h3&gt;Making sense of the data&lt;/h3&gt; &lt;p&gt;The last blog left off at the end of the data collection and preliminary data analysis phase. So let’s pick up from here. After the observation and interview data was collected, three great student research assistants (and some AI transcription tooling&amp;nbsp;J) supported me with the transcription and coding of the data. For the data coding we made use of a software tool called Atlas.ti, which allows you combine and annotate all kinds of data types (incl. video, audio, and text files).&amp;nbsp;&lt;/p&gt; &lt;p&gt;For the data coding we used a theoretical thematic analysis approach, meaning that we searched for themes in the data, guided by a pre-existing theoretical framework. In our case we made use of the &lt;em&gt;&lt;strong&gt;materials experience framework&lt;/strong&gt;&lt;/em&gt; (&lt;a href="https://doi.org/10.1145/2702123.2702337"&gt;Giaccardi and Karana, 2015&lt;/a&gt;), which was initially designed to be used in the context of &lt;em&gt;&lt;strong&gt;material-driven design&amp;nbsp;&lt;/strong&gt;&lt;/em&gt;(&lt;a href="https://www.ijdesign.org/index.php/IJDesign/article/view/1965"&gt;Karana et al, 2015&lt;/a&gt;), but was transferred to the cultural heritage context for the first time in this project. In particular, we made use of the frameworks’ materials experience &lt;strong&gt;levels&lt;/strong&gt;, which recognizes that materials experience takes place on four different interrelated levels, namely the:&amp;nbsp;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Performative level, i.e. what actions the books evoke.&lt;/li&gt; &lt;li&gt;Sensorial level, i.e. how the materials is sensed through for instance vision, sound, and touch).&lt;/li&gt; &lt;li&gt;Affective level, i.e. the emotions elicited by the books, such as joy, boredom, excitement.&lt;/li&gt; &lt;li&gt;Interpretive level, i.e. the meanings ascribed to the books, such as old, fragile, and expensive.&amp;nbsp;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;We annotated the observational videos and interview data on the different interactions, sensorial characteristics, emotions and associations that could be observed or that were mentioned by the participants.&amp;nbsp;&lt;/p&gt; &lt;h3&gt;Interactions with pop-up and movable elements&lt;/h3&gt; &lt;p&gt;In the video below, you can see several examples of the diverse interactions participants had with the physical books.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;video controls width="800" height="500" muted loop autoplay&gt; &lt;source src="https://github.com/KBNLresearch/KBNLresearch.github.io/raw/main/Video1_PerformativityExamples.mp4" type="video/mp4"&gt; &lt;/video&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="source"&gt; &lt;em&gt; &lt;sub&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/sub&gt; &lt;/em&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;Once we identified all the different interactions, they were grouped per type of interactive element, such as a pop-up structures, pull tabs, or rotations wheels. See figure 1 for some examples of the different interactions with pop-up elements. In this diagram we also added when specific sequences of actions could help observed (e.g. repetitive actions), and whenever actions have notable temporal characteristics (e.g. taking place fast or slow).&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/Image1_PerformativityBooks.png?itok=6RURIE5v" width="1300" height="1214" alt="Showing people interact with a pop-up book. Lot's of different small images."&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Figure&amp;nbsp;1: Interactions with pop-up elements in the books (complete image can be viewed in the paper).&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;Similarly, we identified and grouped the different interactions that could be observed with the pop-up and movable books in VR (see figure 2). These interactions together can be denoted as the performativity of the books (i.e. one of the four materials experience levels).&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/Image2_PerformativityVRBooks.jpg?itok=HCQ8rQ0_" width="1300" height="716" alt="Lot of different little pictures showing a woman interacting with a virtual reality pop-up book. "&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Figure 2: interactions with the virtual pop-up and movable books&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;Paper qualities exploited in pop-up and movable books&lt;/h3&gt; &lt;p&gt;Next, we tried to understand how all these identified characteristics relate to the different &lt;strong&gt;material&lt;/strong&gt; &lt;strong&gt;qualities&lt;/strong&gt; of pop-up and movable books. Through an iterative process we arrived at five key qualities of paper exploited in pop-up and movable books, namely:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;strong&gt;Fold-ability&lt;/strong&gt;, related to the ability of paper to fold from a flat page, into 3D structures, and which is associated with repetitive actions, associations such as it being ‘like an explosion’, and emotions such as amusement, admiration, but also boredom.&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Slide-ability&lt;/strong&gt;, related to the ability of paper, to slide in front and behind each other, also eliciting&amp;nbsp;repetitive actions, it being described as ‘toylike’, ‘playful’, and ‘nostalgic’, ‘intuitive’, and eliciting emotions like amusement.&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Tear-ability&lt;/strong&gt;, related to the ability of paper to damage (easily), associated with the&amp;nbsp;ripping &amp;amp; scratching sounds, slowly page turning, fear of damaging, and the association that the books are actually not (very) suitable for children.&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Age-ability&lt;/strong&gt;, relates to paper’s ability to show signs of use and where, which participants associate with ‘fragileness’, ‘old’, visual imperfections, and an (absence of) old-book smell.&amp;nbsp;&lt;/li&gt; &lt;li&gt;&lt;strong&gt;Print-ability&lt;/strong&gt;, relates to paper’s ability to be printed (with letters and images), and can thereby be associated with (not) reading, colorful and nostalgic associations, leading to sensory pleasure, but also sometimes experienced as overwhelming and confusing.&amp;nbsp;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;These characteristics were summarized in five diagrams, such as can be seen in figure 3, which summarises the materials experience characteristics and their interrelationships (if identified), for the &lt;strong&gt;fold-ability&lt;/strong&gt; quality.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/image%203a%20four%20levels%20material%20experience.jpg?itok=GINXYIud" width="1300" height="1300" alt="a semi circle schematic with four levels"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Figure 3: Materials experience on four levels, relating to the fold-ability of paper, as used in pop-up and movable books.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;Designing a mixed reality and two VR experiences&lt;/h3&gt; &lt;p&gt;Based on these characterisations, several ideas for demonstrators were conceptualised. I created one mixed reality experience, and two master graduation students both created their own VR experience as part of their master graduation project, one of which is also featured in the paper. Here, I must also acknowledge Jeroen Boots and Yosua Andoko from the TU Delft XR zone, who supported us all greatly, with the development of all the prototypes. I will explain the mixed reality demonstrator in a bit more detail here.&lt;/p&gt; &lt;p&gt;Firstly, we digitized the book ‘Tip+top boven de wolken’, from 1964, by Vojtěch Kubašta, and used this as a basis for all the prototypes. Initially, we took a whole series of photographs of the original book from the national library collection. We then tried to reconstruct the 2D planes (i.e. the non-deformed, flat paper cut-outs), that make up the 3D shapes in the book (we already reasoned that 3D scanning is not suitable in this case). Reconstructing the planes turned out to be rather challenging using this approach (they need to have the correct dimensions, otherwise the book cannot fold correctly). In second instance, we used an identical book, bought from an antiques bookshop, which we put under a printer flatbed scanner. As all the elements are cut from one page, this was achievable. From this we traced all the parts which made up the book (in Blender). These could then be animated in the Unreal Engine, to create the mixed reality and VR prototypes.&amp;nbsp;&lt;/p&gt; &lt;p&gt;In the mixed reality prototype we aimed to create a memetic material experience, meaning the experience aims to mimic the interactions with the physical book. The XR prototype combines a dummy book, printed with fiducial markers, and a mixed reality headset (Image 4a). As the reader opens the book and turns the pages, the pop-ups are visualised as overlays onto the physical pages (Figure 4b). The movable parts can be interacted with via the eye-tracking functionality – though preferebly we would have liked to rely on more memetic hand tracking (this did not work reliably enough). On three pages, we also explored enhancing different material qualities. On this page we aimed to enhance the fold-ability. By having parts of the page change color, linked to the opening angle of the page, aiming to create surprise, and trigger the repeated actions of opening and closing pages (Figure 4c-d). On another page, we aimed to enhance the age-ability of the book, where the first user sees a page, restored to its original appearance, but with repeated interaction, the pages slowly age and degrade (Figure 4e). Finally we have a page which emphasises the tear-ability of paper, as the plane on the page flies off, you see and hear it ripping loose from the page (Figure 4f).&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/Image3_XR_demonstrator.png?itok=uYpG4rYN" width="871" height="1300" alt="Showing one pop-up book with planes with a fysical and VR aspects combined "&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;Figure 4: XRLibris,a mixed reality prototype of the book ‘Tip+top boven de wolken’, uit 1964, origineel geschreven door Vojtěch Kubašta.&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;An early version of this prototype was demonstrated at The DH Benelux conference, held last year June (2023), in Brussels.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;video controls width="800" height="500" muted loop autoplay&gt; &lt;source src="https://github.com/KBNLresearch/KBNLresearch.github.io/raw/main/Video2_XRDemonstrator_v2.mp4" type="video/mp4"&gt; &lt;/video&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="source"&gt; &lt;em&gt; &lt;sub&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/sub&gt; &lt;/em&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;h3&gt;Implications, limitations and future work&lt;/h3&gt; &lt;p&gt;From the characterisation and the development of these prototypes we show that the Materials Experience Framework, can well transferred from the (material) design context, and also be used in the context of cultural heritage. We see this case study as a first step towards a possible material-driven design methodology for the augmentation of tangible cultural heritage.&amp;nbsp;&lt;/p&gt; &lt;p&gt;Some of the challenges we encountered relate to disentangling the different material qualities, and also separating experiences triggered by the books’ materiality, and other sources of experience (such as the text or depictions eliciting associations and emotions).&amp;nbsp;&lt;/p&gt; &lt;p&gt;Finally we must acknowledge some limitations of this case study. In the demonstrators we do not tackle the practical challenges, that need to be resolved for actual implementation of such an experience in a library or museum context. This includes the important aspect of enabling social interaction, which is currently not (well) addressed but deemed important in cultural heritage experiences (i.e. people like to share cultural heritage experiences, or experience things in larger groups).&amp;nbsp;&lt;/p&gt; &lt;p&gt;Another (potential) limitation is that we used surrogate books to characterise the materials experience. This might not be possible or viable for many other heritage artifacts (i.e. we might not have surrogates available, or they might be to expensive to create).&amp;nbsp;&lt;/p&gt; &lt;p&gt;We hope to extend on this work in the future, by for instance exploring other ways of materials experience characterisation, and expanding the characterisation beyond the ‘use’ of the CH artifacts (i.e. also look the role of materiality in making, or conservation of CH artifacts). We also aim expand on the design phase of the methodology, exploring how designers might be better supported in translating the materials experience insights into meaningful, digitally-mediated experiences. Finally, the evaluation of the prototypes on their materials experience, is currently ongoing, which might provide us with further insight, into how well we are able to capture and translate the materials experience in the end.&amp;nbsp;&lt;/p&gt; &lt;h3&gt;Thanks to…&amp;nbsp;&lt;/h3&gt; &lt;p&gt;I would really like to thank the KB for providing me this opportunity to work with their collections and people, which led to this fantastic result. I really enjoyed working at the KB and with people from the KB, also getting an insight into all the other research topics they work on. This work has really helped me to shape my further research directions.&amp;nbsp;&lt;/p&gt; &lt;p&gt;I would also like to thank my co-authors, for their excellent contributions to the paper, making the research not only better content wise, but also greatly helping articulate this in writing. Finally, I would like to thank the heirs of Vojtěch Kubašta, who kindly let us use his work for the XR demonstrators, the KB imaging department, and the XR Zone for helping us realise the demonstrators.&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Mon, 15 Jul 2024 10:52:27 +0200</pubDate> <dc:creator>Iris.Geldermans@KB.nl</dc:creator> <guid isPermaLink="false">378 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>From Hyperlinks to Queer Histories: Uncovering LGBTQ Web Archives </title> <link>https://lab.kb.nl/about-us/blog/hyperlinks-queer-histories-uncovering-lgbtq-web-archives</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;em&gt;In 2023, as &lt;/em&gt;&lt;a href="https://lab.kb.nl/person/jesper-verhoef" data-entity-type="node" data-entity-uuid="3d017eef-e63a-4571-a022-028e878e7d82" data-entity-substitution="canonical" title="Jesper Verhoef"&gt;&lt;em&gt;KB Researcher-in-Residence&lt;/em&gt;&lt;/a&gt;&lt;em&gt; and &lt;/em&gt;&lt;a href="https://www.cais-research.de/fellows/jesper-verhoef/"&gt;&lt;em&gt;fellow&lt;/em&gt;&lt;/a&gt;&lt;em&gt; at the Center for Advanced Internet Studies (CAIS), I started to study the unique collection of archived LGBT+ websites the National Library of the Netherlands (KB) holds. In my &lt;/em&gt;&lt;a href="https://lab.kb.nl/about-us/blog/analyzing-lgbt-web-archive-data-preservation-preparation" data-entity-type="node" data-entity-uuid="1dc5b313-cd16-47df-b6c1-8e0299fd14cd" data-entity-substitution="canonical" title="Analyzing the LGBT+ Web Archive: From Data Preservation to Preparation"&gt;&lt;em&gt;previous blog&lt;/em&gt;&lt;/a&gt;&lt;em&gt; I outlined how I prepared a dataset. In this blog, I will briefly review steps subsequently taken and the future that lies ahead.&amp;nbsp;&lt;/em&gt;&lt;/p&gt; &lt;p&gt;With the help of &lt;a href="https://lab.kb.nl/about-us/blog/lets-get-some-data-link-analysis-part-1" data-entity-type="node" data-entity-uuid="4718eb88-9a98-4fac-931f-e603e088639a" data-entity-substitution="canonical" title="Let's get some data - Link analysis part 1"&gt;a script developed by Hanna Koppelaar&lt;/a&gt;, which we finetuned, we extracted all hyperlinks from the corpus of hundreds of LGBT+ websites (2008-2022). Analyses of this dataset – including network analyses, or historical hyperlink analyses, using Gephi – are ongoing, but I have already presented interesting findings at various venues and will continue to do so in the next years. Besides presenting internally at the KB and CAIS, I have shared my work at a Cultural Analytics Lab meeting in Amsterdam and at conferences in Prague, Vienna, Southampton, Paris, Hilversum and Utrecht. I made sure to present at conferences related to both the topic (e.g., the LGBTQIA Research Day 2023), web archives as a source (IIPC Web Archiving conference 2023 and 2024), and method (Sociohistorical Network Analysis conference 2024). For a full overview, see &lt;a href="https://pure.eur.nl/en/persons/jesper-verhoef"&gt;here&lt;/a&gt;.&amp;nbsp;&lt;/p&gt; &lt;p&gt;This is also the moment to look back and thank the team I worked with. The project would not have been the same without the close collaboration with &lt;a href="https://lab.kb.nl/person/willem-jan-faber" data-entity-type="node" data-entity-uuid="fd716d2e-defc-46cc-864c-0f104e6578c7" data-entity-substitution="canonical" title="Willem Jan Faber"&gt;Willem Jan Faber&lt;/a&gt;, &lt;a href="https://lab.kb.nl/person/iris-geldermans" data-entity-type="node" data-entity-uuid="c9e91676-1243-4e74-98b1-67d32f81a90a" data-entity-substitution="canonical" title="Iris Geldermans"&gt;Iris Geldermans&lt;/a&gt; and &lt;a href="https://lab.kb.nl/person/michel-de-gruijter" data-entity-type="node" data-entity-uuid="8b72666a-fda9-4f20-81d0-ae9209fb086b" data-entity-substitution="canonical" title="Michel de Gruijter"&gt;Michel de Gruijter&lt;/a&gt;. A highlight was &lt;a href="https://informatieprofessional.maglr.com/hyperlinkanalyse-lhbt-websites"&gt;the article&lt;/a&gt; that Iris and I wrote for the journal &lt;em&gt;Informatieprofessional &lt;/em&gt;(in Dutch), which – also due to its beautiful design – is a wonderful example of what in current academic lingo is referred to as valorization: bringing scholarly work to a wider audience.&amp;nbsp; Special thanks also go to all KB staff working on the web archive. You are instrumental in preserving the past, especially the histories of marginalized groups. As I argue in the first &lt;a href="https://www.tandfonline.com/doi/full/10.1080/24701475.2024.2357897"&gt;peer-reviewed article&lt;/a&gt; my project has resulted in, ‘Doing LGBTQ Internet Histories Justice: a Queer Web Archive Manifesto’ (&lt;em&gt;Internet Histories&lt;/em&gt;, 2024), the KB has done a terrific job, and other libraries should follow suit.&amp;nbsp;&amp;nbsp;&lt;/p&gt; &lt;p&gt;The article also argues that scholars should finally start using existing queer web collections. In the next years, I will continue to do so and, thus, hope to inspire others and prompt more web archive research. More articles will follow, e.g., on the networks that religious LGBTQ websites formed, as well as on the relations between websites of transgender and gay organizations. I am excited that the Netherlands Organization for Scientific Research &lt;a href="https://www.eur.nl/en/eshcc/news/jesper-verhoef-receives-nwo-sgw-open-competition-grant"&gt;(NWO) has recently awarded my project&lt;/a&gt; ‘A Marriage of Convenience? A Web-Historical Analysis of the Relations between Transgender and Gay Organizations (2008-2023)’ an NWO SGW Open Competition grant for excellent, curiosity-driven research. The acronym LGBT suggests a natural alliance between lesbian, gay, bisexual, and transgender people. However, it masks the fraught history between ‘LG’ and the only recently added ‘T’. Although the Web provided a key battleground for gay/transgender relations, how these relationships have taken shape online is still unclear. To address this gap, this project is the first to study a web archive. Drawing on hyperlink analyses and interviews, it will provide quantitative and qualitative insights into the online ties and tensions between ‘LG’ and ‘T’ and contributes to the burgeoning field of web-historical research.&amp;nbsp;&lt;/p&gt; &lt;p&gt;In conclusion, then, my KB Researcher-in-Residency has been a crucial steppingstone for the prolonged project I will work on, which aims to highlight the online pasts of queer and other underrepresented individuals, the historical value of web archives, and the many opportunities that Digital Humanities and computational techniques offer for analyzing this data.&amp;nbsp;&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Thu, 20 Jun 2024 13:41:08 +0200</pubDate> <dc:creator>Iris.Geldermans@KB.nl</dc:creator> <guid isPermaLink="false">379 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>Verhoef receives NWO SGW Open Competition grant</title> <link>https://lab.kb.nl/news/verhoef-receives-nwo-sgw-open-competition-grant</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;strong&gt;Former Researcher in Residence &lt;/strong&gt;&lt;a href="https://lab.kb.nl/person/jesper-verhoef" data-entity-type="node" data-entity-uuid="3d017eef-e63a-4571-a022-028e878e7d82" data-entity-substitution="canonical" title="Jesper Verhoef"&gt;&lt;strong&gt;Jesper Verhoef&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt; has been awarded a NWO SGW Open Competition grant for his research on the relation history between gay and transgender organisations.&amp;nbsp;His project is the first to study a unique LGBT database, comprising 400 archived Dutch websites.&amp;nbsp;&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;Read the full article:&lt;/p&gt; &lt;p&gt;&lt;a href="https://www.eur.nl/en/eshcc/news/jesper-verhoef-receives-nwo-sgw-open-competition-grant"&gt;https://www.eur.nl/en/eshcc/news/jesper-verhoef-receives-nwo-sgw-open-competition-grant&lt;/a&gt;&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Mon, 10 Jun 2024 10:45:48 +0200</pubDate> <dc:creator>Iris.Geldermans@KB.nl</dc:creator> <guid isPermaLink="false">377 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>The remodeling of the KB Lab</title> <link>https://lab.kb.nl/news/remodeling-kb-lab</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;About two years ago the style of the website was renewed to match the new KB branding style. Now, we are going to tackle the lay-out.&amp;nbsp;&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt; &lt;p&gt;As you might have noticed, a new row of content blocks has appeared on &lt;a href="https://lab.kb.nl/"&gt;the front-page&lt;/a&gt; featuring blogs, events and news. This is one of many little changes that will happen through-out 2024 to make sure the website matches our current and future needs. A lot will stay the same, but hopefully, the website will flow a little better and we will be able to better promote what is happening at the KB lab at this very moment. Such as &lt;a href="https://lab.kb.nl/summerschool2024" data-entity-type="node" data-entity-uuid="d47e15a5-7e68-4e38-9c54-35b996b9774a" data-entity-substitution="canonical" title="KB Summerschool Digitale Collecties"&gt;the Summerschool&lt;/a&gt; and the &lt;a href="https://lab.kb.nl/news/opening-kbdatalab" data-entity-type="node" data-entity-uuid="d904bf6d-c020-4728-b0fd-9065fa603200" data-entity-substitution="canonical" title="Opening of the KB_Datalab"&gt;opening of the KB Datalab&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;Please bear with us as we remodel our website!&amp;nbsp;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/CK0067%20-%20Makersplaats%20-%2096x96%20KB%20LAB.png?itok=nt1L-TH6" width="1300" height="327" alt="A paintbrush and wrench crossing each other"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Mon, 27 May 2024 15:32:56 +0200</pubDate> <dc:creator>Iris.Geldermans@KB.nl</dc:creator> <guid isPermaLink="false">376 at <a href="https://lab.kb.nl/"/></guid> </item> <item> <title>CHI NL Read: Cultural Heritage Artifacts and Material Experiences</title> <link>https://lab.kb.nl/news/chi-nl-read-cultural-heritage-artifacts-and-material-experiences</link> <description> &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;Chi NL, an organisation that connects, supports, and represents the Human-Computer Interaction (HCI) community in the Netherlands, has published an interview with our Researcher-in-Resident &lt;/strong&gt;&lt;/em&gt;&lt;a href="https://lab.kb.nl/person/willemijn-elkhuizen" data-entity-type="node" data-entity-uuid="a39b14a0-07fc-4b6b-9ff4-acefa3ffae52" data-entity-substitution="canonical" title="Willemijn Elkhuizen"&gt;&lt;em&gt;&lt;strong&gt;Willemijn Elkhuizen&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;em&gt;&lt;strong&gt;. She has recently published a CHI 2024 paper called "On the Role of Materials Experience for Novel Interactions with Digital Representations of Historical Pop-up and Movable Books".&amp;nbsp;&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="paragraph paragraph--type--afbeelding paragraph--view-mode--rss"&gt; &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-image field--type-entity-reference field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Afbeelding&lt;/div&gt; &lt;div class="field__item"&gt;&lt;div&gt; &lt;div class="field field--name-field-media-image field--type-image field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Image&lt;/div&gt; &lt;div class="field__item"&gt; &lt;img loading="lazy" src="https://lab.kb.nl/sites/default/files/styles/max_1300x1300/public/images/3_Backup2_FindingASuitableBook.jpeg?itok=dwSIvsQL" width="975" height="1300" alt="Pop-up book with planes"&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; &lt;div class="field field--name-field-caption field--type-text-long field--label-visually_hidden"&gt; &lt;div class="field__label visually-hidden"&gt;Bijschrift&lt;/div&gt; &lt;div class="field__item"&gt;&lt;p&gt;&lt;em&gt;[GIF] Selecting a suitable pop-up book from the KB collection for XR experience, featuring ‘Tip+Top boven de wolken’, by Vojtĕch Kubas̆ta (1914-1992), 1964 from Willemijn her blogpost on the KB lab: "&lt;/em&gt;&lt;a href="https://lab.kb.nl/about-us/blog/experiencing-pop-and-movable-books-through-mixed-reality-technology" data-entity-type="node" data-entity-uuid="bb8bc0fb-06e2-4afb-aa16-f80e97cbcbdc" data-entity-substitution="canonical" title="Experiencing pop-up and movable books through mixed reality technology"&gt;&lt;em&gt;Experiencing pop-up and movable books through mixed reality technology&lt;/em&gt;&lt;/a&gt;&lt;em&gt;".&amp;nbsp;&lt;/em&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; , &lt;div class="component-text"&gt; &lt;div class="text__content"&gt; &lt;div class="field field--name-field-body field--type-text-long field--label-hidden field__item"&gt;&lt;p&gt;You can read &lt;a href="https://chinederland.nl/2024/04/chi-nl-read-cultural-heritage-artifacts-and-material-experiences/"&gt;the interview on the CHI NL&lt;/a&gt; website or read her paper:&amp;nbsp;&lt;/p&gt; &lt;p&gt;Willemijn Elkhuizen, Jeff Love, Stefano Parisi, and Elvin Karana. 2024. On the Role of Materials Experience for Novel Interactions with Digital Representations of Historical Pop-up and Movable Books. In Proceedings of the CHI Conference on Human Factors in Computing Systems (CHI ’24), May 11–16, 2024, Honolulu, HI, USA. ACM, New York, NY, USA, 18 pages. &lt;a href="https://doi.org/10.1145/3613904.3642142"&gt;https://doi.org/10.1145/3613904.3642142&lt;/a&gt;&lt;/p&gt; &lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </description> <pubDate>Fri, 24 May 2024 12:22:57 +0200</pubDate> <dc:creator>Iris.Geldermans@KB.nl</dc:creator> <guid isPermaLink="false">375 at <a href="https://lab.kb.nl/"/></guid> </item> </channel> </rss>