Open amir-zeldes opened 4 years ago
@thomaskrause this happens if any metakeys are specified, even if the duplicate key is not requested. Assuming this is now because corpus meta is supported in export, I would be happy with using document metadata by default whenever there is a conflict, or adding syntax to specify which level is meant (a quick fix would be preferred by our users, who don't really need corpus metadata export as much as document level).
When asking for metakeys in CSV export, the exporter crashes if a document has the same metadata key as the corpus. To reproduce, use any Scriptorium corpus - there is a metadatum 'annotation' at both the corpus and document level (often with different values). The exporter throws this error: