[ckan4rdm] using CKAN as research data repository
m.hoffman-sommer at icm.edu.pl
Fri Jan 16 09:24:12 UTC 2015
Thanks a lot for the hints - this is great help. We are now looking at
your extensions in detail, together with my colleagues. The DOI
extension should work for us, I think, and that's very important (we're
aware that we will need a contract for this). I'll be watching for your
embargo extension. And if we stick to our decision of using CKAN (which
we most likely will), then I will certainly have more questions.
W dniu 2015-01-16 o 05:03, Florian May pisze:
> Marta, Ben,
> this is highly interesting! I'm using CKAN to archive all the research
> datasets without a proper home (dedicated data warehouse).
> +1 on embargoing! We run one instance with all datasets set to
> "public" inside our well-protected intranet, and one completely
> separate (because I feared accidental leaks) instance facing outside.
> As we work with sensitive data about threatened species, our data
> release process is painfully manual and goes across several desks, so
> there's no automation yet. It would be great to have some sort of
> auditable data release sign-off, possibly triggering a push to the
> external site.
> Great to hear about ckanext-doi! I'll have to have a chat with the
> Australian National Data Service, who offered to mint DOIs for us,
> whether that offer would extent to a modified ckanext-doi.
> Ben, FYI our colleagues at the WA Museum have just adopted
> CollectiveAccess for their collection data management:
> On Fri, Jan 16, 2015 at 12:23 AM, Ben Scott <ben at benscott.co.uk
> <mailto:ben at benscott.co.uk>> wrote:
> Hi Maria -
> We’re using CKAN as a repository for our research and collections
> data here at the Natural History Museum, London
> 1) Embargoing datasets - this is on our roadmap and a high
> priority so we should be writing an extension for this soon.
> 2) Batch upload - we’ve built data import pipelines using
> Spotify’s Luigi framework (https://github.com/spotify/luigi) and
> the CKAN api. It’s very specialised for our collections database
> though, and not implemented as an extension - but it might be
> useful (https://github.com/NaturalHistoryMuseum/ke2mongo).
> 3) We’ve written an extension for assigning DataCite DOIs -
> https://github.com/NaturalHistoryMuseum/ckanext-doi (You will need
> a contract with DataCite / their national representative to be
> able to mint DOIs).
> Data Portal Lead Architect
> Biodiversity Informatics,
> Natural History Museum,
> +44 (0) 207 942 4277 <tel:%2B44%20%280%29%20207%20942%204277>
> On 15 Jan 2015, at 13:57, Marta Hoffman-Sommer
> <m.hoffman-sommer at icm.edu.pl <mailto:m.hoffman-sommer at icm.edu.pl>>
> > Hi everyone,
> > We're planning an open research data repository which will serve
> the whole scientific community in Poland and we're seriously
> considering to use CKAN for this purpose. I was wondering if some
> of you have already implemented CKAN as a stand-alone repository
> (not part of a data management system)? Is anybody aware of CKAN
> extensions that would enable (1) embargoing dataset release, (2)
> batch upload and edition of multiple files, or (3) DOI assignment
> and display? We have been unsuccessfully searching for these on
> the web.
> > Best,
> > Marta
> > --
> > Marta Hoffman-Sommer
> > Open Science Platform
> > ICM University of Warsaw
> > http://pon.edu.pl
> > _______________________________________________
> > ckan4rdm mailing list
> > ckan4rdm at lists.okfn.org <mailto:ckan4rdm at lists.okfn.org>
> > https://lists.okfn.org/mailman/listinfo/ckan4rdm
> ckan4rdm mailing list
> ckan4rdm at lists.okfn.org <mailto:ckan4rdm at lists.okfn.org>
> ckan4rdm mailing list
> ckan4rdm at lists.okfn.org
Open Science Platform
ICM University of Warsaw
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ckan4rdm