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

Official name and project dir for "rfb" project #57

Closed
2 tasks done
jarumihooi opened this issue Oct 7, 2023 · 2 comments · Fixed by #62
Closed
2 tasks done

Official name and project dir for "rfb" project #57

jarumihooi opened this issue Oct 7, 2023 · 2 comments · Fixed by #62
Labels
✨N New feature or request

Comments

@jarumihooi
Copy link
Collaborator

jarumihooi commented Oct 7, 2023

New Feature Summary

  • The naming of this project also needs to be declared and official.

(For the record, the current used name is "role-filler-binding/rfb" annotation project. It has also been called "OCR" or "creditparsing" or "kvparsing", or something related to the word "structure".)

  • The repository requires a new directory to house information and all other annotation related material for the "rfb" project.

Related

No response

Alternatives

No response

Additional context

No response

@jarumihooi jarumihooi added the ✨N New feature or request label Oct 7, 2023
@clams-bot clams-bot added this to infra Oct 7, 2023
@github-project-automation github-project-automation bot moved this to Todo in infra Oct 7, 2023
@jarumihooi
Copy link
Collaborator Author

Additional Context

====
Impact:
The name of this project is parallel to efforts to better describe what the goal of this project is. With the goal of the project unclear, it is unclear how to make annotation-guideline decisions on differentiation.
This Slack thread details some difficulties during guideline creation.
The current guidelines.ppt is here, and the current readme.md is here.

One of the main questions is which are positive cases (we want to annotate), vs negative cases (we don't care about this).
To know this, we need to know what it is that we are trying to extract -> even if the scope begins as limited in this batch and increases in other later batches.

For instance, is the concept to extract all the information as related to useful metadata even when it doesn't occur as a role-filler key-value type pair... (eg. Copyright information, "Produced in collaboration with Winnifred Touhey Studio and Studio Ghibli" & "Special Thanks To: John Singleton and Studio Ghibli")
Or is the goal to only annotate and possibly reform information into role-filler pairs when needed?

@owencking We may bring this up in a meeting either before or on 10/11 Wed if we are able to find enough cases where both Annotation team and Dev team don't have answers.

@jarumihooi
Copy link
Collaborator Author

During verbal meeting today, the "Role Filler Binding" name was discussed and chosen.

Needs wanted by GBH for metadata extraction were clarified.

Difficulties of the rfb pair data structure were discussed, however, were found sufficient for the task at hand for now, noting that there are some instances still there it may be difficult to match text phenomenon to this pairing scheme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨N New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant