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.

Sign up for GitHub

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

Jump to bottom

Lowercasing #71

Open
michelole opened this issue May 9, 2019 · 2 comments
Open

Lowercasing #71

michelole opened this issue May 9, 2019 · 2 comments
Labels
P1 Higher priority issues, a SHOULD

Comments

@michelole
Copy link
Member

michelole commented May 9, 2019 •
edited
Loading

Lowercasing might make models denser and solve some issues, e.g. ACS = akutes_Koronarsyndrom.

We might need to relax filtering rules for a case-insensitive match as well.
@michelole michelole added the P1 Higher priority issues, a SHOULD label May 9, 2019
@michelole michelole changed the title Try lowercasing Lowercasing May 9, 2019
@michelole michelole added enhancement New feature or request and removed P1 Higher priority issues, a SHOULD labels Aug 19, 2019
@michelole
Copy link
Member Author

We tried that informally and had worse results, downgrading.

@michelole michelole removed the enhancement New feature or request label Aug 20, 2019
@michelole
Copy link
Member Author

Another idea would be to lowercase everything that it's not an acronym and accepting matches on lowercased versions of expansions.

@michelole michelole added the P1 Higher priority issues, a SHOULD label Aug 27, 2019
@michelole michelole mentioned this issue Aug 29, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P1 Higher priority issues, a SHOULD
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@michelole