[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: Assigning DOIs to dictionaries
- To: comcifs@iucr.org
- Subject: Re: Assigning DOIs to dictionaries
- From: "john.westbrook@rcsb.org" <john.westbrook@rcsb.org>
- Date: Wed, 10 Jun 2020 09:21:50 -0400
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rcsb.org; s=google;h=reply-to:subject:to:references:from:message-id:date:user-agent:mime-version:in-reply-to:content-language:content-transfer-encoding;bh=Ncc+Pahy7Y/SiHQZ2H8ssUtUhRFMJUMgBEDlsnQXZRo=;b=Z424AfWSnDARr+fMF6ozfpOnzPPl16grcHT9CHPJn8RAiwQlJW5XLLF3bsmQPSTssCU+hqtPKXOSD5MX6kU7P3vKxq/tL1ypSEawf/kQn/B3WU1aGRNNjU8U0RxJx6mpfz9aN7vgOdbPUsaOH/QzNMBgLqYep6vjRdWqHD3skB//kr9JYVQoziA2dl5Yb81SeyK44PXw5LBFXt+EGLjMoXYU/SX+F46zJNyjigFJk6A0psmlix1x1D6rCPhCriUW00gIR3YZMX/TQH10v17MMeWjLBppgJJz90tC80FNRWoGeZAHWwW7b1E4qx/HeNrEr0iXMYwFxEfS5itovgakmA==
- In-Reply-To: <CAM+dB2daWP7sX3mmQWJrGbXK2FjLFHCx6o3gMDJjAEWJQKj79Q@mail.gmail.com>
- References: <CAM+dB2cP+kbftpDWotNVTXDV5042c6VBkp6bacC+1SOx72oipQ@mail.gmail.com><CABcsX26nVZ6C=tcDTSq8mG8sXR2qtL5QGSE_K0ANBV6wkoSQZQ@mail.gmail.com><CAM+dB2daWP7sX3mmQWJrGbXK2FjLFHCx6o3gMDJjAEWJQKj79Q@mail.gmail.com>
Greetings,
There are archival resources that are specifically tasked to
manage diffraction data sets such as
https://proteindiffraction.org/,
https://www.cxidb.org/, andÂ
https://data.sbgrid.org/data/.
Before promoting the notion of storing data in Zenodo, please
support these resources which
provide curation and integration with other data resources.Â
John
On 6/10/20 9:11 AM, James Hester via
comcifs wrote:
CAM+dB2daWP7sX3mmQWJrGbXK2FjLFHCx6o3gMDJjAEWJQKj79Q@mail.gmail.com">Glad you approve Herbert. There is I think an attribute for the DOI in the dictionary but I didn't manage the Github - Zenodo dance as well as I could have this time and so didn't edit in the Zenodo-assigned DOI before publishing. Hopefully we'll be able to iterate to a point where inter-dictionary references via DOIs are machine-actionable - the insistence on DOIs pointing to landing pages instead of files throws a bit of a spanner in the works.
On Wed, 10 Jun 2020 at 19:40, Herbert J. Bernstein <yayahjb@gmail.com> wrote:
Working through Zenodo make sense. While it is not a COMCIFS issue, IUCr should also considerformalizing use of Zenodo for posting DOIs for raw data behind journal publications, and then back toCOMCIFS --adding a uniform DOI tag category _in_ all our dictionaries for all raw data, dictionariesand other relevant permanent links in CIF documents, so it is easy to build permanent document networks.  -- Herbert
On Mon, Apr 27, 2020 at 3:14 AM James Hester via comcifs <comcifs@iucr.org> wrote:
Dear COMCIFS,_______________________________________________
In the past we have discussed assigning DOIs to our CIF dictionaries via the mechanism used by the IUCr for their publications. So far this discussion has not yielded much fruit. A DOI is quite useful as it allows us to refer to other dictionaries via DOIs and URLs that are pretty much guaranteed to not become outdated and are machine-actionable.
Instead of the IUCr publication mechanism it occurred to me that we might use an outside service like Zenodo to deposit canonical dictionary versions. How this would work is as follows:
(1) A new dictionary version would be approved using the current mechanisms(2) The dictionary would be deposited at Zenodo using a COMCIFS or IUCr official account and a DOI reserved (ie document is not yet published)(3) This DOI would be edited into the dictionary if necessary(4) Further technical editing would be undertaken as needed(5) The final dictionary is published on the IUCr website and the 'Publish' button pushed on Zenodo
Ideally the 'author' for Zenodo and citation purposes would be either 'COMCIFS' or 'IUCr'. The authentication password could reside with the COMCIFS secretary(s). I have chosen Zenodo because it is not affiliated or funded by a commercial entity and I have some experience publishing there, but alternative suggestions are welcome.
The minor downsides I see with this scheme are that (1) the DOI would contain the string 'zenodo', which is sort of against the spirit of the underlying object being able to move locations (2) a data DOI such as that delivered by Zenodo points to a 'landing page', not to the object itself. The resources are instead linked from the landing page; as far as I can tell these links are predictable (DOI URL + '/files/<filename>'). I'd prefer an even simpler way to point a program at a DOI and get back the file I wanted, but I digress.
Thoughts?
James.
--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
comcifs mailing list
comcifs@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/comcifs
--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
_______________________________________________ comcifs mailing list comcifs@iucr.org http://mailman.iucr.org/cgi-bin/mailman/listinfo/comcifs
-- John Westbrook RCSB, Protein Data Bank Rutgers, The State University of New Jersey Institute for Quantitative Biomedicine at Rutgers 174 Frelinghuysen Rd Piscataway, NJ 08854-8087 e-mail: john.westbrook@rcsb.org Ph: (848) 445-4290 Fax: (732) 445-4320
Reply to: [list | sender only]
- References:
- Assigning DOIs to dictionaries (James Hester)
- Re: Assigning DOIs to dictionaries (Herbert J. Bernstein)
- Re: Assigning DOIs to dictionaries (James Hester)
- Prev by Date: Re: Assigning DOIs to dictionaries
- Next by Date: Renewal of STAR File trademark registration
- Prev by thread: Re: Assigning DOIs to dictionaries
- Next by thread: Draft 2019 report for IUCr exec
- Index(es):