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

better handling of arboratorgrew's specific meta #237

Open
kirianguiller opened this issue Jun 30, 2023 · 1 comment
Open

better handling of arboratorgrew's specific meta #237

kirianguiller opened this issue Jun 30, 2023 · 1 comment

Comments

@kirianguiller
Copy link
Collaborator

kirianguiller commented Jun 30, 2023

We should handle better the meta that are arboratorgrew specific.

First, we should have the following :

  • AG_user_id : self-explanatory.(Even for parsed sentences, this is the custom name that we can attribute when running a parsing (in the parse settings))
  • AG_timestamp : when the sentence was annotated (or parsed) the last time
  • AG_parser_id : that would be the exact info of the parser (when was it train, the nickname, the performance, etc). It's only here if the sentence is a parsed one

And then, I think we want that these AG_xxx meta are not exported by default, but an option in the export panel could allow us to do so (useful in case of exporting -> importing usecase, which is often useful when we want to run a script on all sentences of all users).

What do you think @bguil and @khansadaoudi ?

@bguil
Copy link
Collaborator

bguil commented Jul 4, 2023

I like the idea. It gives a clear disctinction between AG spectific metadata vs other metadata.
I am wondering how to organize the transition. We should plan an update of the already existing projet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants