Error message when trying to publish a dataset

329 views
Skip to first unread message

ofu...@gmail.com

unread,
Oct 28, 2016, 3:04:48 AM10/28/16
to Dataverse Users Community

Hi,

We are receiving the following error message when we try to publish a dataset:

 

" Error – This dataset may not be published because the DataCite Service is currently inaccessible. Please try again. Does the issue continue to persist? Please contact Dataverse Support for assistance."

 

It looks like it is a bug in dataverse system.  The error message occurs also when we change the contributor to another at the draft stage and later want to publish the dataset.

 

Any help? We are running Dataverse v.4.3

 

-         - Obi

Philip Durbin

unread,
Oct 28, 2016, 8:45:38 AM10/28/16
to dataverse...@googlegroups.com
Hi Obi,

The error is coming from the bundle key "dataset.publish.error.datacite" at https://github.com/IQSS/dataverse/blob/v4.3/src/main/java/Bundle.properties#L790

There's an open issue at https://github.com/IQSS/dataverse/issues/2225 that seems related at least.

Judging from http://status.datacite.org/history DataCite hasn't had a DOI registration outage in over a month (screenshot attached). It is possible that there's an outage going on?

Was publishing datasets working for you yesterday or last week or whatever? By design, Dataverse prevents you from publishing datasets if the remote service (EZID, DataCite, etc.) is down.*

The people who have been working closely on https://github.com/IQSS/dataverse/pull/3146 would have more insight on all of this than I do (please jump in) but I hope this helps!

Phil

* If this is documented in the guides somewhere, please let me know.


--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f3e428fe-d16a-4cd0-888f-212d6a1a4a81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
DataCite_Status_-_Incident_History_-_2016-10-28_08.39.30.png

Philipp UiT

unread,
Nov 30, 2016, 3:36:37 AM11/30/16
to Dataverse Users Community, philip...@harvard.edu
We have now figured out the reason why we did not get published the dataset. The problem was that there were som HTML tags in the metadata description field. According to Dataverse, some HTML tags are allowed in this field, however we were not able to publish the dataset before we removed all HTML tags. Strangely, I was able to "publish" the very same dataset WITH the HTML tags in the Harvard Demo Dataverse, but I don't know whether the Demo Dataverse is connected to another DOI provider than DataCite. It seems that DataCite does not accept HTML tags in the description field.

Best, Philipp


fredag 28. oktober 2016 14.45.38 UTC+2 skrev Philip Durbin følgende:
Hi Obi,

The error is coming from the bundle key "dataset.publish.error.datacite" at https://github.com/IQSS/dataverse/blob/v4.3/src/main/java/Bundle.properties#L790

There's an open issue at https://github.com/IQSS/dataverse/issues/2225 that seems related at least.

Judging from http://status.datacite.org/history DataCite hasn't had a DOI registration outage in over a month (screenshot attached). It is possible that there's an outage going on?

Was publishing datasets working for you yesterday or last week or whatever? By design, Dataverse prevents you from publishing datasets if the remote service (EZID, DataCite, etc.) is down.*

The people who have been working closely on https://github.com/IQSS/dataverse/pull/3146 would have more insight on all of this than I do (please jump in) but I hope this helps!

Phil

* If this is documented in the guides somewhere, please let me know.

On Fri, Oct 28, 2016 at 3:04 AM, <ofu...@gmail.com> wrote:

Hi,

We are receiving the following error message when we try to publish a dataset:

 

" Error – This dataset may not be published because the DataCite Service is currently inaccessible. Please try again. Does the issue continue to persist? Please contact Dataverse Support for assistance."

 

It looks like it is a bug in dataverse system.  The error message occurs also when we change the contributor to another at the draft stage and later want to publish the dataset.

 

Any help? We are running Dataverse v.4.3

 

-         - Obi

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

Philip Durbin

unread,
Nov 30, 2016, 7:51:19 AM11/30/16
to dataverse...@googlegroups.com
Ah, you are very likely suffering from this bug then:

Publishing fails for script-added dataset with a Dataverse using Datacite - https://github.com/IQSS/dataverse/issues/3328

I'm surprised that you can't replicate this issue on the demo server though. I think the demo server does use EZID rather than DataCite for DOI registration but I thought metadata always sent to DataCite on publish no matter whether you are using EZID or DataCite for DOI registration. I probably have a misunderstanding of how this all works.

Phil

On Wed, Nov 30, 2016 at 3:36 AM, Philipp UiT <uit.p...@gmail.com> wrote:
We have now figured out the reason why we did not get published the dataset. The problem was that there were som HTML tags in the metadata description field. According to Dataverse, some HTML tags are allowed in this field, however we were not able to publish the dataset before we removed all HTML tags. Strangely, I was able to "publish" the very same dataset WITH the HTML tags in the Harvard Demo Dataverse, but I don't know whether the Demo Dataverse is connected to another DOI provider than DataCite. It seems that DataCite does not accept HTML tags in the description field.

Best, Philipp


fredag 28. oktober 2016 14.45.38 UTC+2 skrev Philip Durbin følgende:
Hi Obi,

The error is coming from the bundle key "dataset.publish.error.datacite" at https://github.com/IQSS/dataverse/blob/v4.3/src/main/java/Bundle.properties#L790

There's an open issue at https://github.com/IQSS/dataverse/issues/2225 that seems related at least.

Judging from http://status.datacite.org/history DataCite hasn't had a DOI registration outage in over a month (screenshot attached). It is possible that there's an outage going on?

Was publishing datasets working for you yesterday or last week or whatever? By design, Dataverse prevents you from publishing datasets if the remote service (EZID, DataCite, etc.) is down.*

The people who have been working closely on https://github.com/IQSS/dataverse/pull/3146 would have more insight on all of this than I do (please jump in) but I hope this helps!

Phil

* If this is documented in the guides somewhere, please let me know.

On Fri, Oct 28, 2016 at 3:04 AM, <ofu...@gmail.com> wrote:

Hi,

We are receiving the following error message when we try to publish a dataset:

 

" Error – This dataset may not be published because the DataCite Service is currently inaccessible. Please try again. Does the issue continue to persist? Please contact Dataverse Support for assistance."

 

It looks like it is a bug in dataverse system.  The error message occurs also when we change the contributor to another at the draft stage and later want to publish the dataset.

 

Any help? We are running Dataverse v.4.3

 

-         - Obi

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/b06c3715-e076-4a4d-8295-7e24a1e168b3%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Pete Meyer

unread,
Dec 1, 2016, 11:15:45 AM12/1/16
to Dataverse Users Community, philip...@harvard.edu


On Wednesday, November 30, 2016 at 7:51:19 AM UTC-5, Philip Durbin wrote:
Ah, you are very likely suffering from this bug then:

Publishing fails for script-added dataset with a Dataverse using Datacite - https://github.com/IQSS/dataverse/issues/3328

I'm surprised that you can't replicate this issue on the demo server though. I think the demo server does use EZID rather than DataCite for DOI registration but I thought metadata always sent to DataCite on publish no matter whether you are using EZID or DataCite for DOI registration. I probably have a misunderstanding of how this all works.

I suspect you may be thinking of sending DataCite XML metadata to the EZID API endpoint; but it's also very possible I'm missing something.

Pete
 

Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

Sebastian Karcher

unread,
Dec 1, 2016, 11:25:48 AM12/1/16
to dataverse...@googlegroups.com, philip...@harvard.edu
Technically speaking, EZID forwards the metadata to DataCite, which is the actual registration agency (I think EZID is referred to as the regional partner or so). But since, as Pete says, EZID has their own API for depositing the metadata and creating DOIs, I'm not necessarily surprised it behaves differently from the corresponding DataCite one. I would guess they sanitize the metadata they forward to DataCite.
Before fixing this in DV, it'd be worth checking if basic html tags are actually illegal in DataCite XML. It seems like potentially useful information (e.g. I'd certainly want <em> tags for species in the metadata) and if it is, report this to DataCite as an upstream bug.


Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/8f0e8526-0362-453e-b54a-8b8cc2e96081%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Sebastian Karcher, PhD
www.sebastiankarcher.com

Amber Leahey

unread,
Feb 3, 2017, 12:20:19 PM2/3/17
to Dataverse Users Community, philip...@harvard.edu
Thanks for this thread! I just happened upon it and I think it is relevant to a similar issue we are having here.  

At Scholars Portal, we are using the DataCite service to register data and mint DOIs with our Dataverse instance. We are getting reports that publishing fails for a dataset when HTML is entered into the metadata form, including <p> tags. This problem keeps coming up and we'd like to figure out how to resolve it to support users who want to add HTML or other code, scripts etc. to metadata. 

Turns out DataCite schema doesn't support all HTML tags, only <br> tags: quote:  "Use <br> to indicate a line break for improved rendering of multiple paragraphs, but otherwise no html markup." http://schema.datacite.org/meta/kernel-4.0/doc/DataCite-MetadataKernel_v4.0.pdf 

What is the best approach to try and resolve this issue? Should we no longer support most HTML characters in our instance since we are using DataCite service? This might mean changing some of the guide content to reflect this... OR Is there a way to pass just the valid metadata to DataCite in order to comply? Should this be added to GitHub issue https://github.com/IQSS/dataverse/issues/3328 or new issue started?

Many thanks, 
Amber


Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

Durand, Gustavo

unread,
Feb 3, 2017, 12:45:00 PM2/3/17
to dataverse...@googlegroups.com, Durbin, Philip
My initial instinct would be that we should strip out the html when sending to DataCite. 

If so, then I think that can be the solution to solve 3328.

Thoughts?

On Fri, Feb 3, 2017 at 12:20 PM, Amber Leahey <amber...@gmail.com> wrote:
Thanks for this thread! I just happened upon it and I think it is relevant to a similar issue we are having here.  

At Scholars Portal, we are using the DataCite service to register data and mint DOIs with our Dataverse instance. We are getting reports that publishing fails for a dataset when HTML is entered into the metadata form, including <p> tags. This problem keeps coming up and we'd like to figure out how to resolve it to support users who want to add HTML or other code, scripts etc. to metadata. 

Turns out DataCite schema doesn't support all HTML tags, only <br> tags: quote:  "Use <br> to indicate a line break for improved rendering of multiple paragraphs, but otherwise no html markup." http://schema.datacite.org/meta/kernel-4.0/doc/DataCite-MetadataKernel_v4.0.pdf 

What is the best approach to try and resolve this issue? Should we no longer support most HTML characters in our instance since we are using DataCite service? This might mean changing some of the guide content to reflect this... OR Is there a way to pass just the valid metadata to DataCite in order to comply? Should this be added to GitHub issue https://github.com/IQSS/dataverse/issues/3328 or new issue started?

Many thanks, 
Amber

On Thursday, 1 December 2016 11:25:48 UTC-5, Sebastian Karcher wrote:



--
Sebastian Karcher, PhD
www.sebastiankarcher.com

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.

Philipp at UiT

unread,
May 17, 2017, 12:15:53 PM5/17/17
to Dataverse Users Community, philip...@harvard.edu
I just got the same DataCite related error message again when trying to publish another dataset. After a lot of trial and failure I found out that the metadata field "Contact Name" has to be filled in in order for the dataset to be published. I don't know the reason for this - I couldn't find any information about this field to be obligatory in DataCite Metadata Scheme V 4.0. By default, the contact email address is required by Dataverse, but not the contact name. We have now added this field as obligatory in our Dataverses. Maybe the field should be required by Dataverse.

Best,
Philipp

Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.



--
Sebastian Karcher, PhD
www.sebastiankarcher.com

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

Philip Durbin

unread,
May 17, 2017, 1:10:10 PM5/17/17
to dataverse...@googlegroups.com
Hi Philipp, I left a note about how contactName isn't required at https://github.com/IQSS/dataverse/issues/3802#issuecomment-302144799 but I'm already thinking that your problem deserves a dedicated GitHub issue. If you would be so kind as to create one that would be great. :)

Phil


Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.



--
Sebastian Karcher, PhD
www.sebastiankarcher.com

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/23272b62-0e92-4455-97a6-c0850b328980%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Philip Durbin

unread,
May 18, 2017, 6:05:54 AM5/18/17
to dataverse...@googlegroups.com
Thanks for creating a new issue, Philipp! Here it is:

Contact Name should be required metadata field in Dataverse? - https://github.com/IQSS/dataverse/issues/3839

I'm glad you were able to work around the problem my making contactName required. As far as I can tell, this issue affects people who use DataCite for DOI registration rather than EZID.

Phil

To post to this group, send email to dataverse-community@googlegroups.com.

Philipp at UiT

unread,
Oct 17, 2017, 8:36:53 AM10/17/17
to Dataverse Users Community
As for now, the help text for the description field says "This field supports only certain HTML tags." (the mouse over text does not list any accepted tag, at least not i Firefox or Chrome). As stated earlier in this thread, we have had several instances where HTML tags in this field prevented the dataset from being published because DataCite wouldn't accept the tags. Wouldn't it be better to change the help text to something like "Do not use HTML tags."?

Best,
Philipp

Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.



--
Sebastian Karcher, PhD
www.sebastiankarcher.com

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

Philip Durbin

unread,
Oct 17, 2017, 8:56:45 AM10/17/17
to dataverse...@googlegroups.com
Hi Phillip,

I'm a little confused. You're still running Dataverse 4.7.1 right? That's what I see at https://dataverse.no/api/info/version

There's a fix in 4.8 that addresses this problem related to DataCite. Basically, Dataverse users are still welcome to use certain HTML tags to improve how they are displayed within Dataverse but we strip out those HTML tags before we send the XML to DataCite on publish: https://github.com/IQSS/dataverse/issues/3845

In short, I'm hoping that upgrading to Dataverse 4.8 or higher will solve your problem. Does that make sense? Am I missing something? We don't want to tell users they can't use HTML.

Thanks!

Phil


Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.



--
Sebastian Karcher, PhD
www.sebastiankarcher.com

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/c8ffbdca-87cb-477e-b554-121421922c35%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Philipp at UiT

unread,
Oct 17, 2017, 9:58:35 AM10/17/17
to Dataverse Users Community
Sorry for the confusion, Phil! Yes, you are right, we are still running 4.7.1. And I somehow missed that this bug has been fixed in 4.8. Thanks for reminding me!

Best,
Philipp

Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.



--
Sebastian Karcher, PhD
www.sebastiankarcher.com

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages