-
Notifications
You must be signed in to change notification settings - Fork 105
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
Hard coded SNOMED release file bug. #467
Comments
I've got these ones locally from June and they seem to still produce the release date reliably:
Which versions does the new naming convention start with? And what does it look like? |
You are right nothing has changed. I think what I was alluding to was using the folder one level up. I could be mistaken in using the wrong level. In which case we need to throw an error as it can pass through without one. For example, for the following names, this convention does not work.
|
so the above code is brittle anyway. |
Yeah, I think we should be able to match the folder basename with regex and pull the third group:
If there's no match, we can raise an exception. EDIT: |
Due to changes in the naming convention of SNOMED CT release files. The date/release no longer fits these exact character range.
MedCAT/medcat/utils/preprocess_snomed.py
Line 80 in 96706c8
Needs to be checked with different releases and extensions before merging.
The text was updated successfully, but these errors were encountered: