Eric Kansa is a user on octodon.social. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Eric Kansa @ekansa@octodon.social

Eric Kansa boosted

if you haven't come across it, Ed Summer's 'Etudier' python tool for grabbing google scholar citation graph is a really nice little thing. github.com/edsu/etudier . point it at a reference, get the grab that cites it/it cites. pass it a search, get the citation landscape around the term. do a bit of sna on the graph, & you can id works that bridge the clumps.

Eric Kansa boosted

"No split infinitives" is one of those weird holdovers from grammarians who believed Latin was some sort of god-language that every other language needed to mimic, even when it made no sense.

"Don't end a sentence in a preposition" is another rule that it's hard to deal with. Or to adhere to. Or to put up with.

@aejolene Yep. I'm bouncing between these platforms. Some days I'm here more. But ideally, I'd like to see sustained conversations continue over here.

I spent the morning giving grantees more specific data management advice and guidance.

I think it's useful to follow up and let researchers know that we care and pay attention.

Eric Kansa boosted
Opinion: Shut up about Michelle Wolf if you’ve been silent on Trump’s offenses https://t.co/R8ly6WM7zD

I made some updates to our bibliography of Open Context related publications. Some are behind paywalls, so we also self archive and link to green open access versions here:

opencontext.org/about/bibliogr

@CobaltVelvet @kensanata @paregorios @zatnosk @Antanicus @mattcropp

Ah! interesting, and thanks! Tom, does this give a path forward on using hashtags for ancient/old stuff?

@steko @paregorios

Stefano -> YES! Thanks, I'm now in active development for archiving with Zenodo. The main issue is always granularity for us, and bundling up a bunch of JSON files into one submission is very attractive. For the most part that will work, but in some cases, there are some complex licensing issues. Some datasets need to have a variety of licenses for images, so I have to break them apart into different archive bundles for Zenodo.

Nothing is ever simple.

Eric Kansa boosted

I've been collaborating with a visiting Masters student, Fanny Mezard from the @ecoledeschartes@twitter, on generating ePubs for a born-digital journal (ISAW Papers, which covers the Ancient World). You can see a very early version of her work at isawnyu.github.io/isaw-papers- .

Hashtag mechanics question Show more

Hashtag mechanics question Show more

@paregorios

Yep. OK. This all makes sense. I'll get cracking on this! I will make a different zip archive (probably zip, because easier for non-Linux folks) for each DOI identified dataset in Open Context. Some will have 10's of thousands of JSON files and images files etc, some will be just a CSV (for table dumps).

Sound workable?

@paregorios

Yep, our JSON also has predictable key sorting. It's also sorta fun to see the GeoJSON rendered in GitHub. But Zenodo does the versioning thing.

Next question. 10's of thousands of GeoJSON-LD files in an archival "deposit". Should I just compress many files into giant tarballs or is there value in having each one individually identified / accessible in the repository?

@paregorios

That's my impression also. I think it will be more trouble than it is worth to go into GitHub. I just wanted to check to see if anyone had a compelling reason to also use it to version control structured data.

@JubalBarca @paregorios @captain_primate @seanmunger @mlemweb @jenniferlouise @steko @ryanfb @Electricarchaeo @sebhth


OK. I'm wanting to update how we archive data with Open Context.

I'm seriously looking at Zenodo. The question is, is it still worthwhile to put 1.5 million OC GeoJSON-LD files in Github? GitHub is a pain at that kind of scale, but if people think it essential or useful, I want to know.

Otherwise, I'll just use build off the Zenodo API.

Thoughts?