Eric Kansa @ekansa@octodon.social

@steko @ebel

2/2

So, need policies and procedures, and above all lots of awareness of local contexts and issues. Working in collaboration with local/indigenous communities to understand needs, align data practices to positive outcomes and reduce risks is needed.

@steko @ebel

I don't have any specific guidance or references at my finger tips. But yes, there are sensitive data concerns that are very context dependent. In US, Native American sites get looted & vandalized, and location data are sensitive. Certain endangered species also involve sensitive location data.

1/2

@sebhth @electricarchaeo @paregorios

Good points all. I will check it out!

@sebhth @electricarchaeo

I gave up on Academia.edu. Will you try this on Zenodo?

@paregorios @aejolene @sebhth @steko

I think Tom called it. Also DOIs get more indexing in different discovery and metrics (including Altmetrics).

EZID supports minting 1 million ARKs / year at $1500 / year service fee.

@steko @paregorios @aejolene

I'm hoping that OC mitigates the downsides by providing curation services as it publishes data. We are too small to do longevity / preservation services.

@paregorios @steko @aejolene

OK. I'm now uploading our image data into Zenodo. At the rate things are going, this will take several days running round the clock.

I can't believe this is really a free service, especially when I consider costs of other digital repository services.

So what's the downside to using Zenodo?

The SNL Cold Open was pretty funny.

These days, it somehow feels safer archiving research data far from US shores.

@paregorios @steko @aejolene @sebhth

The effort is minimal, because I can script it. Getting ARKs from EZID just requires API calls.

So, ok, I'll get on it.

@steko @paregorios
@aejolene
@sebhth

What do you all think? Will it help, harm, or "meh" to add ARK identifiers to all our URI identified data?

@paregorios @steko @aejolene

Do you think it is good to go for production use?

@steko @paregorios
@aejolene

Second example, this one has Pleiades and PeriodO URIs in the metadata:

https://sandbox.zenodo.org/record/217236

I think I'm more or less OK to advance to using the real API not the sandbox?

Ack. Coffee isn't working yet. I can't possibly focus enough to "toot" without error. How am I supposed to code?

@steko @paregorios @aejolene

Sorry tooted in haste last night. "A Quite Place" was about to begin (BTW: fun movie!!!)

My tooth last night was a messy way of saying that I have to break up Open Context projects into separate Zenodo archives. Not ideal, but metadata should are their common relationships explicit.

@steko @paregorios putting @aejolene in the loop also.

One more thing about our use of Zenodo. I'm making separate archives for all the pictures associated with an Open Context project and the structured data in an Open Context project. The reasons is that we'll too often run into the Zenodo limits on storage for an individual archive. Because of this, some Open Context will have many different Zenodo archives.

@steko @paregorios

Here's a test upload (in the sandbox) of the files associated with a small project.

Does this look useful?

https://sandbox.zenodo.org/record/217212

Tips for improvement? All the metadata is generated from metadata we already had, so I'm pleased by the ability script uploads and documentation.