I can’t match the log’s line number to the current code, so I don’t know which specific field is the problem. Overall, my guess would be that one of the date ranges only has a start or end date, but not both and the code may be failing due to that. Since this is occurring during the code to generate the metadata for DataCite, I’d guess that the overall update for DataCite is failing. If all of the metadata was entered when creating the dataset, it’s possible that you won’t notice any difference in Fabrica (is the DOI now findable?). In any case, I think it’s worth finding and addressing rather than just letting it go.
-- Jim
--
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-commu...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/dataverse-community/d4092b82-5943-4cae-aee4-aa3418cf2707n%40googlegroups.com.
With the version number, I can see that the problem is here: https://github.com/IQSS/dataverse/blob/906f874f9fd56241c41e6c2c2f6989c4406f5909/src/main/java/edu/harvard/iq/dataverse/pidproviders/doi/XmlMetadataTemplate.java#L748-L754 and involves the release date. A bug and fix for v6.5 are described in this issue (which also had a DataCite config issue) and this PR. TLDR: Some publication failures caused a draft dataset to have a 1.0 version in the database even though publication failed and, once that happened, the codeblock I showed above was incorrectly assuming that the draft version had a release date causing the null pointer.
This shouldn’t happen for a normal dataset where no publication failure has ever occurred and shouldn’t happen when publishing versions after 1.0. I would have thought that DataCite would not have the latest metadata due to this bug, but, given that the DataCite entry looks OK, I guess it is something you can just watch for in other datasets. The problem should go away as of v6.5.
--Jim
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/b50f4917-b3b4-4992-95b6-4c83577dc3e4n%40googlegroups.com.