Open helbashandy opened 3 years ago
Thanks @helbashandy That is a weird bug, as schemaLocation
is entirely optional in XML, and should be totally ignored by our tools, including MetacatUI. The error you quoted shows a malformed schemaLocation attribute with three componenet URIs rather than the expected 2. So I think the issue is in determining where that schemaLocation
is being injected if its not in your original document. I don't have permission to view the document so I couldn't check it myself. @gothub can you take a quick look at the document and verify there is no schemaLocation
in it, and also see if MetacatUI somehow injects schemaLocation
when it is missing? If so, this could be a very quick fix.
@gothub Have you gotten a chance to take a look at this?
@gothub have you looked at this "Priority Critical" issue yet to at least deduce where the malformed schemaLocation is being introduced?
Describe the bug After upgrading ESS-DIVE's underlying metacatUI to 2.14.0 on data-stage.ess-dive.lbl.gov, in testing older data packages updates we realized that when an EML document that is on 2.1.1 is missing the
schemaLocation
, metacatUI doesn't handle updates for those document. For example, an EML document that starts with the following node:MetacatUI shows the following error:
To Reproduce Steps to reproduce the behavior:
Go to this data package on ESS-DIVE stage: https://data-stage.ess-dive.lbl.gov/view/ess-dive-27a90361bad844c-20200903T192229411859
Try to update it through the UI
Expected behavior MetacatUI should
Screenshots
Desktop (please complete the following information):