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

Provide resource for parsing ILCS strings into their component parts #8

Open
bepetersn opened this issue Aug 2, 2014 · 3 comments
Open

Comments

@bepetersn
Copy link
Member

We've talked about switching to only allowing lookup of IUCR code with ILCS bits. If we were to make this change, it would put the responsibility on the client to do their own parsing of ILCS reference strings, parsing which we could at least try to help with.

The simplest thing would be to provide a regex with which to parse ILCS reference strings as a constant, like ILCS_FORMAT. Another possibility would be to expose a method which is capable of doing some parsing for the client.

Problems arise in that there might be multiple formats in which ILCS data could appear, which suggests a more involved approach as opposed to providing a single regex.

@ghing
Copy link
Contributor

ghing commented Aug 2, 2014

@bepetersn Good summary of all the caveats connected with this issue.

@ghing
Copy link
Contributor

ghing commented Aug 16, 2017

@hancush Can you check if parserator is appropriate for parsing ILCS statutes? Do you have to train it? How much training data does it need?

@ghing
Copy link
Contributor

ghing commented Aug 16, 2017

Also, I think https://github.com/sc3/python-ilcs might be a better place for this.

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