You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For IATI XML to spreadsheet conversions, when we have a instance of multiple uses of the same sub element, these are pushed to their own worksheet. A consequence of this is that it is not then possible to roundtrip this data back to XML - as we are missing any data to relate the sub element to its parent.
@rorads has been looking into this too - finding that inserting a column result/0/iati-identifier into a worksheet then "trick" (?) CoVE into consolidating different rows of results data into the same XML block (with the invalid element being inserted as the last element)
I guess we could look at inserting such an ID into XML, on demand?
Note - this does also alter the structure of spreadsheets, as activity-identifier is replaced by cove:id in various sheets. This will need some testing / thought
(original discussion in #1219)
For IATI XML to spreadsheet conversions, when we have a instance of multiple uses of the same sub element, these are pushed to their own worksheet. A consequence of this is that it is not then possible to roundtrip this data back to XML - as we are missing any data to relate the sub element to its parent.
@Bjwebb suggests:
The types of instances where this occur would be:
document-link
with multipledocument-category
sub-elementsresult
with multipleindicator
I think multi lingual instances are also affected by this, which would describe instances where any text has multiple versions (which is legitimate) :
title
with multiplenarrative
The text was updated successfully, but these errors were encountered: