Skip to content
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

Import any type of EAF tier #343

Closed
William-N-Havard opened this issue Jan 25, 2022 · 2 comments · Fixed by #350
Closed

Import any type of EAF tier #343

William-N-Havard opened this issue Jan 25, 2022 · 2 comments · Fixed by #350
Assignees
Labels

Comments

@William-N-Havard
Copy link

Is your feature request related to a problem? Please describe.
For future annotation campaigns, we might want to create new types of EAF tiers (such as we did to annotate morpho-syntactic complexity). We would like to be able to import the annotations of these new tiers into ChildProject

Describe the solution you'd like
Allow the user to specify which tiers should be imported when importing the annotations from an EAF file

@William-N-Havard William-N-Havard added the enhancement New feature or request label Jan 25, 2022
@lucasgautheron
Copy link
Collaborator

lucasgautheron commented Jan 25, 2022

The package supports custom converters (cf. https://childproject.readthedocs.io/en/latest/api-annotations.html#custom-converter)

Would this work for you?

EDIT: though I agree it might be better to implement support for any tier in the built-in importer.

@William-N-Havard
Copy link
Author

The package supports custom converters (cf. https://childproject.readthedocs.io/en/latest/api-annotations.html#custom-converter)

Would this work for you?

EDIT: though I agree it might be better to implement support for any tier in the built-in importer.

@marianne-m already did it for me. But this enhancement would certainly be useful for users who do not have any coding abilities!

@marianne-m marianne-m linked a pull request Feb 8, 2022 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants