Question: future of gem

[mcritchlow]

Hey @dchandekstark!

So I've heard there's an EZID/Datacite working group that's formed for folks who are transitioning from EZID to Datacite. The University of California system, however, is apparently sticking with EZID. So I'm looking into how we might keep your great gem here supported going forward.

I imagine that Duke is transitioning so Datacite, yes? If so, what are your thoughts on the best way to keep this gem going? We could fork into one of our UC organizations, such as UCSD's, or we could add other UC devs as collaborators here, or? I thought about maybe samvera-labs, but this gem will really only be relevant for the UC campuses, as far as I've been told.

[dchandekstark]

Hi @mcritchlow!

Thanks for checking in. I'm glad someone out there finds this work useful. :) At Duke we are transitioning DOIs of course, but AFAIK we will continue to mint ARKs as well, so I would continue supporting this gem for that purpose. It seems unlikely, however, that I will actively work on it in the foreseeable future. Let me consult with folks here about the options you meantioned. In the meantime, PRs are welcome! If it gets to be too much to handle, I'll holler. And, of course, you're certainly free to fork the repo. We can touch base again down the road. I'll leave this issue open for that purpose.

[mcritchlow]

That sounds like a great plan, thanks!. I should say at the moment there's no actionable changes needed, as far as I'm aware. So an onslaught of PR's isn't right around the corner :)

[awead]

Hi guys, I see I'm in good company here. At Penn State we're switching over to DataCite's EZ API, which is supposed to replace EZID. According to them, this gem supports their API. I'm assuming that this means because both DataCite and this gem support the EZID API, q.e.d. your gem supports DataCite.

Are either of you aware of that? And, more importantly, am I wrong?

[dchandekstark]

Hey @awead! Yes, @jgondron contributed work for DataCite compatibility that was incorporated into v1.8.0 (https://github.com/duke-libraries/ezid-client/releases/tag/v1.8.0). We're not using DataCite at Duke, but we do still use EZID for ARKs. Please feel free to submit improvements!

[awead]

@dchandekstark sweet! That's awesome. We need to get off of EZID and on to DataCite by the end of this year, so you may see some PRs from either me or @Cam156. Thanks to you both for keeping this alive.