-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSV export fails for corpora with same metakey as a document #628
Labels
Comments
@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). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
The text was updated successfully, but these errors were encountered: