You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, guys, thanks you are making a really cool tool.
I've faced with number of missing dates as wel ass false positives.
Like:
n\nMaster Transportation Agreement, April 2020.\n\n22777 Springwoods Village - Aprill 2020 will not be recognized as next sentence starts from digits.
record of positive Sept 1st, 2005 earnings - also not recognized if day with '-st', in your model only '-th' taken into account.
And this is strange, as even get_raw_dates not recognize it. But if I use modified forked datefinder from your repo - it's ok: datetime.datetime(2005, 9, 1, 0, 0), 'Sept 1st, 2005'),.
It could be 12.1987 or in 01.1988 - not recognizing date if month is in digit format.
I want to ask if there is an easy way for users to fine-tune your model?
The text was updated successfully, but these errors were encountered:
Hello, guys, thanks you are making a really cool tool.
I've faced with number of missing dates as wel ass false positives.
Like:
n\nMaster Transportation Agreement, April 2020.\n\n22777 Springwoods Village
- Aprill 2020 will not be recognized as next sentence starts from digits.record of positive Sept 1st, 2005 earnings
- also not recognized if day with '-st', in your model only '-th' taken into account.And this is strange, as even
get_raw_dates
not recognize it. But if I use modified forked datefinder from your repo - it's ok:datetime.datetime(2005, 9, 1, 0, 0), 'Sept 1st, 2005'),
.It could be 12.1987 or in 01.1988
- not recognizing date if month is in digit format.I want to ask if there is an easy way for users to fine-tune your model?
The text was updated successfully, but these errors were encountered: