GTnotebook
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Help
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    ## Call - DL 18/07/2025 1500 mots dates : 8-9 décembre Esch-sur-Alzette, Belval https://2025.computational-humanities-research.org/cfp/ Workshops: up to 1500 words. Workshops should be organized to be more interactive than the main conference. The workshops will take place before the conference, on December 9, 2025. Workshop proposals should describe: - the aims and set up of the workshop, - the academic background for the work, - proposed length (e.g. half day or full day), - an outline of the day, including the types of activities, the expected key outcomes, - a short bio of each organizer or presenter, including their name, affiliation, email address - a plan for promoting the workshop to draw participants. - specific requirements, including but not limited to special equipment (e.g. audio/video), software, physical space arrangements, - any technical knowledge, skills, or experience participants should have prior to attending the workshop. ## Notes du 11/07 - déroulé du processus de recherche, exploration de données, analyse, critique et édition au moyen d'un notebook - deux exemples, rzine & jdh - requétage de https://database.factgrid.de/wiki/FactGrid:Vocabulary_model - dépendance aux gafams / github - reproductibilité avec API - [x] email à Elisabeth : Raphaëlle - [x] email à Bertrand : Mattia ## Proposition de planing > [name= Mattia] - Présentation / définition de la notion de notebook et du paradigme de la programmation lettrée - Le notebook pour l'analyse et l'exploration de donnée (TP SPARQL) - Notebook et reproductibilité - Le notebook pour la publication (Rzine , JDH) ## Workshop Proposal (WIP) - 1500 words > [name= Mattia] Je commence la mise en page en // sur latex *Notebooks, challenges and issues related to the research data cycle* TODO : Add "open science", "reproductibility" keywords This workshop follows the existing actions (webinars, seminar, student training, workshops, summer school, etc.) of the interdisciplinary [GT Notebook](https://gt-notebook.gitpages.huma-num.fr/site_quarto/) working group, started on 2021. By choosing not to define this object, the "notebook", too precisely, we are trying to map its boundaries each time they appear as new practices, new tools, new ways of writing or seeing documents that potentially implement any of Literate Programming principles (Knuth, 1984). ### Aims & Set up With this workshop proposal we try to answer to three main goals : - this original workshop focuses on Notebook's prior functionalities (interactivity, transclusion, literate programming, etc) to foster exploration of historical data within collaborative to publication pratices, so we adapt our discourse to humanities research communities that don't know or use Notebook actually; - by proposing this workshop at CHR, we are aiming at sharing ideas, theories and practices co-built within our french speaking international network (~250 scientists, engineers, doctoral fellows working in multiple disciplinary fields) to international audience; - to our knowledge and experience, the proposed workshop contributes to incentives - through theoretical support and technical experimentation - to better understand complex relations on performing computational humanities, between "hack AND yack" DH paradigm (Nowviskie, 2016) > [name=Rey ] > @RaphaelleK n'ayant pas lu l'article, tu peux en dire un peu plus ici :) ? > @reycoseb il s'agit de déconstruire l'opposition humanités & techniques/tecnologies qui court avec l'idiome DH depuis les ThatCamp "more hack less yack", i.e. "more grok less talk". L'article de 2 pages en fait un court historique critique. j'ai repris le point 3 ci-dessus. > ci dessous une proposition de "set up" à retoucher In the morning, a first part (one hour) will provide pratical and theoretical introduction to Notebooks from an interdisciplinary point of view built on GT Notebook's work in progress. During the second part of the morning we will discuss and pratice collectively around some issues encountered when using a Notebook leads to writing a computational scientific paper to be peer reviewed. Two frameworks - the Journal of Digital History and RZine journal, will be quickly presented : their workflows and how editorial teams try to mitigate or take into account different issues. Within the afternoon, participants will practice and publish a replicable or derivated Notebook by following a step by step tutorial based on the previously seen workflows, with the support of the trainer's team. ### Academic background for the work The gt notebook is a working group ### Proposed length (e.g. half day or full day), A day with three parts : introduction (theory/first practice), data collection, computation/edition ### An outline of the day, including the types of activities, the expected key outcomes #### Morning - Introduction of Notebooks universe (morning) : We first introduce the "Notebook" to audience by collectively manipulate such an object, and next we try to introduce the multiple dimensions we face when we question it from inter disciplinar points of view : epistemology, ecosophy, digital literacy, reproducibility - From data collection to publication (morning) : we focus on common issues (computational reproductibility, differentiating workflows between code / natural langage, templates of publication, etc. ) that researchers using Notebooks integrating api collection encounter when the Notebook becomes less an exploratory tool and tends to be more a computational scientific paper. We try to answer collectively these reflexive and technical issues by reviewing externalities and knowledge production elicitation through literate programming paradigm, and potential notebook framework that take into account the question of reproducibility. > [name= Rey] > Je me suis dit que c'était peut être mieux de présenter JDH et RZine de façon contextualisé dans la deuxième partie de matinée, avec peut être une table ronde / réflexion incluant les participants, plutot que de rajouter çà l'après midi. Sinon ca fait beaucoup de théorie et pas tant que çà de pratique. > > [name= Mattia] Une table ronde sur les revues reproductibles ça serait vraiment bien. Mais on a que 2 personnes. Il faudrait une revue en plus. > > > [name= Rey] Programming Historians, même si pas executable ? ou alors il faut qu'on parte en chasse pour en trouver une autre, peut etre chez les archéo ? Ben Marwick a recruté Simon Carrignon (FR/EN) pour la revue [Advance in archeological practice](https://www.cambridge.org/core/journals/advances-in-archaeological-practice/article/introducing-the-associate-editor-of-reproducibility/DBFACBCD750189B1CB4C8332FB6FFE34) > > > > [name= Mattia] PH c'est pas mal, mais c'est ni exécutable, ni basé sur des notebooks. J'ai l'impression qu'on sort pas mal du champ de la journée. Mais je viens de voir qu'il y a E. Schultz dans l'équipe Fr. > > > > [name= Rey] Il y a aussi Episcience, et Nephal + si on veut aussi parler revue Diamant, je ne sais pas ou en est Raphael Tournoy. Je doit m'échapper pour aller chercher les enfants, mais je repasse ce soir :) > > > > > [name= Mattia] a++ #### Afternoon Guided Tutorial (afternoon) : We propose a step by step tutorial based on notebook examples and possible derivatives within two main trends of usage, actually in production : jupyter/python (JdH) and quarto/R (Rzine) templates First part : Notebooks and reproductibility Mooc reproductibilité. Présentation avec Konrad invité sinon suite du TP matin et introduction git / github Second part : Notebooks and publishing (Rzine, JDH) This afternoon session explores how Git and GitHub have emerged as academic publishing standards, transforming how researchers structure, collaborate on, and disseminate their work. Drawing on practical examples from Rzine and JDH, we will examine how proper repository organization—including media management, source code documentation, and notebook editing—supports transparent and reproducible digital scholarship workflows. We end this afternoon by asking two existing journal (Jdh, RZine) to present theirs workflows and how they manage these issues today and in the future. ### a short bio of each organizer or presenter, including their name, affiliation, email address - **Raphaelle Krummeich** (raphaelle.krummeich@univ-rouen.fr) is a research engineer at the UMR IDEES, specialized in data curation, conceptual data modeling, contributing in epistemological studies of research methods and inter disciplines's dialogs.She is also a member of the editorial board of *Rzine*. - **Elisabeth GUERARD** (elisabeth.guerard@uni.lu) is an application developer at the Luxembourg Centre for Contemporary and Digital History (C2DH), University of Luxembourg, particularly for the backend of the *Journal of Digital History* (JDH) and serves as technical reviewer, ensuring research reproducibility, promoting the adoption of standards, and advocating for sustainable digital practices. - **Sebastien Rey-Coyrehourcq** (sebastien.rey-coyrehourcq@univ-rouen.fr) is a geographer, computer scientist working as a research engineer at the UMR IDEES. Member of the steering comitee of the GT Notebook since 2021, he is also create and/or animate webinars and workshops in this context. He is also a member of French Data Workshop network (Atelier de la Données), especially the subgroup about source code, software in context of computational reproductibility. An interest that appear in link with his participation in steering comitee of French Reproductibility Network, and the interest for Devops practices developped around *Rzine* journal. - **Mattia Bunel** (mattia.bunel@ehess.fr) is a geographer and a GIS specialist working as a research engineer at the UMR Géographie-cités. - **Hugues Pecout** (hugues.pecout@cnrs.fr) is a geographer and engineer at the UMR Géographie-cités. He is also a member of the editorial board of *Rzine* ### a plan for promoting the workshop to draw participants - Using our existing mailling list (~250 person) - DH and other thematic list - Communicating on existing Journal focusing these communities : - Jdh (En) - Data & Corpus (Fr) https://msh-lorraine.fr/mshl-17/ - DH list (Fr) - Programming Historians (En) - CAAA Computational Archeology (En) - etc. [name=Rey] Hésitez pas à en ajouter ... ### specific requirements, including but not limited to special equipment (e.g. audio/video), software, physical space arrangements > Les manipulations seron réalisées à l'aide d'une instance Jupyter Lab déployée par les organisateurs du workshops. Les participants au workshop auront simplement besoin de s'y connecter pour suivre les activités proposées. Chaque participant devra venir avec un ordinateur portable et avoir accès à internet. Aucun autre prérequis - Reliable internet connection for each participant - Each participant must bring their own computer. All you need is a web browser ### any technical knowledge, skills, or experience participants should have prior to attending the workshop > On procéde comment techniquement ? On demande a chaque utilisateur de venir avec un Jupyter déjà installé ou on déploie/utilise un serveur jupyter lab/binder en amont ? > > La seconde solution est un peu mieu car dans ce cas on ne demande qu'un ordinateur et un navigateur. :+1: [name=Seb] yes ! - SPARQL and Python Knowledge (pas de "maitrise" nécessaire, mais une petite connaissance aidera beaucoup au suivi. Les personnes intéressées peuvent suivre ce tutoriel PH : https://programminghistorian.org/en/lessons/intro-to-linked-data) - Computationnal and semantic engagment in humanities framework, - - Curiosity for data critical theory (Drucker, 2011) Max 30 participants; à cause des manipulations ### Bibliography Nowviskie, B. (2016). On the Origin of “Hack” and “Yack.” In M. K. Gold & L. F. Klein (Eds.), Debates in the Digital Humanities 2016 (pp. 66–70). University of Minnesota Press. https://doi.org/10.5749/j.ctt1cn6thb.10 Drucker, J. (2011). Humanities Approaches to Graphical Display In DHQ, Vol. 5 N°1. https://dhq.digitalhumanities.org/vol/5/1/000091/000091. Knuth, D. E. 1984. « Literate Programming ». The Computer Journal 27 (2): 97‑111. https://doi.org/10.1093/comjnl/27.2.97.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully