Closed hlapp closed 5 years ago
Looks like RNeXML is assuming that literal metadata nodes are still using the content
attribute for the contents, and not parsing the literal node contents. (e.g. the format we see in TreeBase:
<meta content="Mycologia" datatype="xsd:string" id="meta17" property="dc:publisher" xsi:type="nex:LiteralMeta"/>
<meta content="Mycologia" datatype="xsd:string" id="meta16" property="prism:publicationName" xsi:type="nex:LiteralMeta"/>
Guess it shouldn't be assuming that. (I guess only resource meta nodes can be nested(?) so it should be okay to just parse the contents of any literal meta node? Presumably the schema doesn't allow you to do both a content
attribute and literal content in the same node?
The LiteralMeta schema definition says the following:
If the
@content
attribute is used, then the element should contain no children.
So I guess it's not enforced that it's one way or the other, but it seems it would be fair to just go by the guidance.
See #193
I found this from looking at top-level metadata; it's possible that other metadata elsewhere is getting lost too:
dc:creator
is indeed empty in the file, butdc:description
is not:This isn't a problem in the
get_metadata()
function:Other metadata in the file are coming back fine (though these are not
LiteralMeta
, if that's got something to do with it):Any ideas @cboettig?