"Hi Julien, sorry to bother you again but I have one more question. I’m
trying to update my data sets to include the DOI for the accompanying
article (it’s not out yet but I just got the DOI). For one of my data sets
I mistakenly hit “publish with DOI” and now I can’t edit / update the
record at all either online or via morpho:
Online it says I don’t have access, in morpho I get this error:
"Problem with saving to metacat in EML200DataPackage! <?xmlversion = "1.0">Could not write file: /var/metacat/documents/doi:10.5063/F12Z13MD.2: /var/metacat/documents/doi:10.5063/F12Z13MD.2 (No such file or directory)
Any tips on how I can fix this and update the record to include the DOI?"
It seems like the user accidentally applied a DOI and then tried to go back to Morpho to edit the package, where it tried to write the new identifier as the DOI.2
The user's problem has been remedied but it seems like this behavior should be fixed
Author Name: Jeanette Clark (Jeanette Clark) Original Redmine Issue: 7205, https://projects.ecoinformatics.org/ecoinfo/issues/7205 Original Date: 2017-08-10
From a user:
"Hi Julien, sorry to bother you again but I have one more question. I’m trying to update my data sets to include the DOI for the accompanying article (it’s not out yet but I just got the DOI). For one of my data sets I mistakenly hit “publish with DOI” and now I can’t edit / update the record at all either online or via morpho:
https://knb.ecoinformatics.org/#view/doi:10.5063/F12Z13MD
Online it says I don’t have access, in morpho I get this error:
"Problem with saving to metacat in EML200DataPackage! <?xmlversion = "1.0">Could not write file: /var/metacat/documents/doi:10.5063/F12Z13MD.2: /var/metacat/documents/doi:10.5063/F12Z13MD.2 (No such file or directory)
Any tips on how I can fix this and update the record to include the DOI?"
It seems like the user accidentally applied a DOI and then tried to go back to Morpho to edit the package, where it tried to write the new identifier as the DOI.2
The user's problem has been remedied but it seems like this behavior should be fixed