home.social

#dayofdh2023 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dayofdh2023, aggregated by home.social.

  1. I'm very late to posting something for #DayOfDH2023 but I'll blame it on being 15 hours off of my home time zone. I spent the day offline, on a boat, with DH colleagues and my spinning machine and crochet. We talked about projects, conferences, organizations, and there was seafood and beverages aplenty. It was not at all what my regular life looks like doing #DigitalHumanities, but it's a memory I'll treasure.

  2. So you say it was #DayofDH2023 yesterday? I say: I spent some time caring about the i18n of a precious, entry-level common good, the Voyant Tools suite of text analysis tools. voyant-tools.org/?lang=fr

  3. My #DayOfDH2023 was spent on a lot of inside-baseball kinds of logistics for constellate.org

    - planning some workflow changes with my developer colleague
    - talking UX design and review workflow questions with my UX colleague
    - working through a bunch of SQL to make sure our internal data store is flowing correctly, so we can e.g. keeps track of how long it takes users' Jupyter Labs to spin up

    In sum: a lot of time asking "will it be worth investing the work to do X?" before doing X

  4. This #DayOfDH2023 was a day of joyful collaboration to build open infrastructures for tool and method registries on top of (or rather in) Wikidata. Talking data models, SPARQL, APIs, and trying to get #OpenRefine to push our mapping of the #TaDiRAH taxonomy to #Wikidata.

    Finally, I spent the bigger part of the day with my kids and, later on my partner, before briefly sitting down to scheme for the new #ADHO #SIG #MultilingualDH, which I have the honour to co-chair with Merve Tekgüler.

    There are also things I would have liked to do but couldn’t, namely attending the 9th conference of the Islamicate DH Network (@idhn) or the open research colloquium at @DigitalHistory

    #DigitalHumanities #LOD #DayOfDH

  5. The end of my day was me staring at spreadsheets being confused so that's pretty normal. Thanks for a great #DayOfDH2023 everyone :D

  6. RT @EurResearch: It's the #dayofdh2023!
    This year's theme - Humanizing Data - makes us reflect on how we bring together cultural heritage #data and #people in the @Europeanaeu ecosystem. The Research Community is the place for those who work in academia and research! 👇pro.europeana.eu/page/european t.co/Q75JdayywX

    🐦🔗: n.respublicae.eu/EU_opendata/s

  7. I just remembered it's #DayofDH2023! My day began with a meeting with the wonderful @dhandlib team. Then spent some time working on our upcoming #podcast institute with @natlhumanities and prepping the #ACH2023 conference. Took a break from conference/institute planning to have a team meeting w my fantastic #DH staff person. Now it's back to more conference planning! Speaking of which, there's still time to register for the @ach virtual conference, to be held June 29-July 1. We'll be sharing the program details very soon! ach2023.ach.org/

    #DigitalHumanities #DayofDH

  8. On this #DayOfDH2023 I have also been following #SSP2023 on the various platforms — the Society for Scholarly Publishing, that is. If you want to know more about what I’m doing now that’s DH-adjacent but is also pertinent to other realms of scholarship, see this short video I recorded to accompany our SSP poster. player.vimeo.com/video/8294058

  9. Hm I kind of missed #DayOfDH2023 but I spent today sending out some messages for @ResearchOrgs, twiddling with the ROR website at ror.org, and starting some slides for the ROR workshop I’ll be co-leading in South Africa in 2 weeks. I don’t do exclusively humanities anymore, but DH sure led me here! #DayOfDH

  10. Oh, it's #DayOfDH2023. I didn't even notice. I spent the day filing receipts. 😭😭😭 I am now working on a report of the state of DH program at a dear liberals art college that hired me as an outside consultant. This one is a happy report because they are killing it!

  11. The upside of Airtable is that you can work out the data model on the fly and change it as project needs dictate.

    I bet you can guess what the downside is.

    #DayOfDH2023

  12. starting to wind down my #DayOfDH2023 #DayOfDH with dinner.

    I'm the cook in the household. We have a CSA delivery each Saturday, so what I make depends on what we get, plus a few things.

    For today, I'm taking a break from potatoes and rice by making Pasta e Ceci with some of the kale we got and an onion from a couple weeks ago.

  13. Happy #DayofDH2023 !

    I don't have anything to share, so I want to shout out some of the excellent work by my colleagues at @IDAH .

    First, of course, is something that @kalanicraig has been putting together for the past year or so. A community archiving page built with Jekyll, that is a minimal computing answer to creating collections by and for underserved communities.

    Here's the current github page: github.com/kalanicraig/communi

  14. With the release out of the way, it's time to work on a radically different project. First, though, let's check on the production server.

    People are busy on #dayofdh2023! FromThePage.com is running at 332 pages transcribed per hour, which is about 50% higher than I'd expect at this time of day.

  15. After several meetings on DH #infrastructure (e.g. how to organise shared access to GPU-clusters?), supervising two #PhD candidates (on #distantviewing #Newsreels and on interdisciplinary #digitalScholarlyEditions, preparing for a presentation on #srmanticweb and #regesta if #medieval #charters (#diplomaticsrulez), teaching #Persona methods to a DH course on the example of #endangeredlanguages #digitalarchives and conversion of book #indices into #factoid #prosopography I finally conclude my #dayofdh2023 #dayofdh with bottle of beer ...

  16. The meeting with Sponsored Programs about the proposal budget went well and now we have a clear game plan.

    #DayOfDH2023

  17. #dayofdh2023 continues with a lunch break followed by releasing the fixes and features we developed over the last couple of days. #FromThePage is open-source, so first we deploy to the SAAS fromthepage.com as a last verification step, then we merge into the main branch and cut a new release: github.com/benwbrum/fromthepag

    Our friends at the University of Texas-Austin Libraries have been testing these releases, including accessibility and security scans, so they're the first people we email about the release.

  18. #DayOfDH2023

    Adding some more documentation to a GitHub hosted repo so AIs can have some higher quality training data to use for turning us into batteries or whatever.

  19. Trying to get a short call with all the approval stakeholders on this imminent grant proposal to answer budget-related questions once and for all because the story keeps changing when passed from person to person and I am absolutely not going to create and email (!!!!) yet another spreadsheet budget to have somebody go "no that's not what we said" again.

    #DayOfDH2023

  20. Now for the all important digital humanities task of trying to figure out the exact sequence of things I need to click in my university's interface to get reimbursed for my trip to Whitman Camp

    I have 2 "how to" PDF's people have sent me to try to help figure it out 🤞

    #DayOfDH2023

  21. Talks aren't posted yet as of when I'm writing this, but I did submit one for dhsi.org/open-digital-collab-2 about data as the basis for sustainability.

    I assert that we need to work at the right level of abstraction that lets us capture the human intent. Domain specific languages (DSLs) are one way to represent intent as data interpreted by an engine.

    In today's work with Surface, HTML and CSS are too low-level. That's why we have React/Vue/Surface to capture the UX intent.

    #DayOfDH2023 #DayOfDH

  22. Today is a pretty meeting light day (only 4!). So far I've met about a new project on Mari Sandoz I am super excited about, and met about setting up new development servers (also pretty excited about that, the old server is getting pretty old). #DayOfDH2023

  23. Back from my workout, showered, and fixing lunch. Continuing my work with Surface.

    I'm finding it easier to reason about scopes for data in the UI. It's all server-side rendering, but it feels a lot like React/Vue.

    The ultimate goal is to make it easy to add features like object editing in the web UI rather than forcing use of a Python command line client.

    #DayOfDH2023 #DayOfDH

  24. CW: cat photo

    My feline co-worker Moonshadow approves of the implementation plan I've just worked out with a colleague in Slack.

    #DayOfDH2023

  25. #DayOfDH2023

    I continue my complicated and fraught relationship with Docker.

  26. Doing a hopefully quick context switch since I got an email from root on the #ISAWNYU website server that reads: "memmon.py restarted the process named primary_zeoclient1:primary_zeoclient1 at Wed May 31 12:03:05 2023 because it was consuming too much memory (1547214848 bytes RSS)"

    Plone clients grow RAM-wise over time, so this is an expected behavior, but it can also be an indicator of malicious pummeling, so it's worth checking network traffic via Cloudwatch.

    #DayOfDH2023

  27. On this #DayOfDH2023 I've been mostly working on an XSLT stylesheet to convert the poetry TEI of the #RomanticPeriodPoetryArchive into OntoPoetry-underpinned RDF. Read more about the project here:

    romanticperiodpoetry.org

    #RPPA #GlobalRomanticism #LOD #POSTDATA @DayofDH #DayofDH

  28. In next week's @BL_DigiSchol reading group we're discussing @bestqualitycrab 's 'Scholarship in a Clopen World ' popjournal.ca/issue04/verhoeve

    The 'paradox of open' is also a good read on the subject paradox.openfuture.eu/ (HT twitter.com/sclaeyssens for the latter)

    (Edited to add #DayofDH2023 #DayofDH as I've just realised how on-topic it is)

  29. Apparently it's #DayofDH2023 #dayOfDH - as far as I can tell, a day when folk working in Digital Humanities share what they're up to help demystify our work

    I've bounced between meetings, email, slack, thinking about a conference proposal, documenting code and processing / moving crowdsourced data around. This means I've chatted to a combination of @LivingWithMachines and @BL_DigiSchol people, plus folk from Kings Digital Lab and a bit of social media (like this)

  30. Starting #DayOfDH2023 like I do most days: with a lovely (e)bike ride to work.

    #DayOfDH

  31. Today is #DayOfDH2023 (or just #DayOfDH). I’m not seeing a lot of posts yet, but I plan to post some through the day. I missed last year’s (and several before that), but that would have been before the large migration from the other place.

  32. I doubt I'll be working late tonight (it was an early start), so that's probably my #dayOfDH2023 done.

    So what's happening in the rest of the world? #dayOfDH

  33. Although it's not included in the plan, I'll also have to be updating the #GLAMWorkbench as I develop the content for the #Trove Data Guide. glam-workbench.net/

    That's because I'll be using the GW to save related tools, resources, and tutorials -- some new, most updated. On top of that, v3 of the Trove API will be released shortly, so I'll have to update *all* of the Trove content in the GW.

    Anyway, that's probably enough planning for now. Tomorrow I'll make a start on the content! 😬 #dayOfDH2023. #dayOfDH

  34. Ok, I've moved all my notes about the Trove Data Guide from a Google Doc to a series of GitHub issues. This way I can add further notes as I go, documenting the development process, and relate the issues to specific tasks to keep myself on track. Hmm I might also investigate GitHub's Project tool... github.com/wragge/trove-data-g #dayOfDH2023. #dayOfDH

  35. What I'm trying to do now is document my decisions and questions about the guide in the repository's 'issues': github.com/wragge/trove-data-g

    I'll be adding to this throughout today's #dayOfDH2023. #dayOfDH

  36. One of the cool things about JB is that you can easily include computationally-generated content, like the Trove category charts in my demo page. They're created when the book is built by a bit of code that gets the data from the #Trove API.

    When I push changes in the book's code to GitHub, an action runs that builds the book and commits it to GitHub pages. But when I uploaded my new pages this morning the charts didn't appear. Why? I needed to add the Trove API key as a 'secret' in GitHub, then modify my GH action script to use that secret when it builds the book. Now it's working!

    #dayOfDH2023 #dayOfDH

  37. In the process I discovered a bug in the jupyterlab_myst extension, and the fix is already in! github.com/executablebooks/jup

    I also realised that the reason my citations weren't rendering was that you need to have included the `bibliography` directive somewhere first -- I suppose it's obvious, but it's not exactly clear in the documentation. But this is what learning any new system is like!

    #dayOfDH2023 #dayOfDH

  38. I'm creating the guide using Jupyter Book. I'm only a couple of days into the project, so I'm really just figuring out how JB works, and deciding on things like style and formatting. Yesterday I created a basic demo page to test things like references, glossaries, indexes, and creating and 'glueing' variables into the rendered content: wragge.github.io/trove-data-gu #dayOfDH2023 #dayOfDH

  39. Oh, so here in Australia it's #dayofdh2023 already!

    Today I'm working on the #Trove Data Guide, which will be part of the HASS Community Data Lab being developed by the ARDC: ardc.edu.au/project/hass-commu

    #DayofDH