KC2 DataCite GUIDs/DOIs no longer working?

[jonathancrabtree]

For example, this URL used to be valid but now gives a 500 Internal Server Error:

https://doi.org/10.25491/zzv1-xb48

[danielskatz]

cc @mfenner @timclark001 @mercecrosas

[mfenner]

Thanks for reporting this @jonathancrabtree. The DOI is working fine (see https://api.datacite.org/works/10.25491/zzv1-xb48), but there is an issue with the landing page provided by the KC2 landing service. @mlev71 will fix this.

[carlkesselman]

One think I noticed from looking at the metadata is that there is no way to know who published the DOI so I didn't know who to talk to....

This is one of the reasons why I've argued for having metadata about the identifier.

[mfenner]

@carlkesselman I am confused by this statement, as this information is part of the metadata. We have the prefix (namespace), the data-center-id (the account that created the DOI), and the publisher.

[carlkesselman]

Well, the author is "The GTEx Consortium”, the data center id is datacite.gtex, I don’t see the publisher listed. We do have the prefix but it indicates that this is DO is owned by datacite. I guess I was trying to figure out who was actually responsible for creating this DOI so I knew who to contact to get it fixed…..

Carl

---

Dr. Carl Kesselman Dean’s Professor, Epstein Department of Industrial and Systems Engineering Fellow, Information Sciences Institute Viterbi School of Engineering

Professor, Preventive Medicine Keck School of Medicine

University of Southern California 4676 Admiralty Way, Suite 1001, Marina del Rey, CA 90292-6695 Phone: +1 (310) 448-9338 Email: carl@isi.edumailto:carl@isi.edu Web: http://www.isi.edu/~carl

On Jul 20, 2018, at 3:00 PM, Martin Fenner notifications@github.com<mailto:notifications@github.com> wrote:

@carlkesselmanhttps://github.com/carlkesselman I am confused by this statement, as this information is part of the metadata. We have the prefix (namespace), the data-center-id (the account that created the DOI), and the publisher.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/dcppc/crosscut-metadata/issues/13#issuecomment-406737507, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADbjXm_Fe01QYlkBQw1moip37Fhkno76ks5uIlLjgaJpZM4VW9_6.

[mfenner]

Carl, one of the tasks for us (Team Sodium) is better document this information. The prefix is for example specific to a particular data repository, similar to the namespaces used by identifiers.org. datacite.gtex is the DataCite account ID, you can find more info (including contact email) via web page or API (https://api.datacite.org/clients/datacite.gtex). Publisher is less useful in this context.

The prefix is probably the easiest way to find out more, including contact email: https://api.datacite.org/prefixes/10.25491

[carlkesselman]

Hi,

Thats great. Will be very useful.

Carl

---

Dr. Carl Kesselman Dean’s Professor, Epstein Department of Industrial and Systems Engineering Fellow, Information Sciences Institute Viterbi School of Engineering

Professor, Preventive Medicine Keck School of Medicine

University of Southern California 4676 Admiralty Way, Suite 1001, Marina del Rey, CA 90292-6695 Phone: +1 (310) 448-9338 Email: carl@isi.edumailto:carl@isi.edu Web: http://www.isi.edu/~carl

On Jul 20, 2018, at 3:26 PM, Martin Fenner notifications@github.com<mailto:notifications@github.com> wrote:

Carl, one of the tasks for us (Team Sodium) is better document this information. The prefix is for example specific to a particular data repository, similar to the namespaces used by identifiers.orghttp://identifiers.org. datacite.gtex is the DataCite account ID, you can find more info (including contact email) via web page or API (https://api.datacite.org/clients/datacite.gtex). Publisher is less useful in this context.

The prefix is probably the easiest way to find out more, including contact email: https://api.datacite.org/prefixes/10.25491

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/dcppc/crosscut-metadata/issues/13#issuecomment-406742015, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADbjXkjXDSihxnEaKbIFeyQuD1FYuw4bks5uIlj5gaJpZM4VW9_6.

[mlev71]

Hi Jonathan, we transitioned the resolution of the GTEx DOIs to new landing pages and a bug involving translating metadata was deployed. We’re still beta testing and appreciate you making us aware of the issue. The bug was found and resolved, so all 23 GTEx dois resolve properly to their landing pages.