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

Make document structure processing parametrizable #82

Closed
kermitt2 opened this issue Jul 6, 2018 · 1 comment
Closed

Make document structure processing parametrizable #82

kermitt2 opened this issue Jul 6, 2018 · 1 comment

Comments

@kermitt2
Copy link
Owner

kermitt2 commented Jul 6, 2018

Similarly as for the query attribute mention which can list different mention recognizers to be applied, we could introduce a structure attribute that will specified the (unique) underlying structure to be considered for processing a complete document (usually a PDF).

For instance default would mean no structure is considered (recognize and disambiguate entities in any tokens extracted from a PDF), scientific-article would mean to use GROBID model for scientific publication, e-book would mean to use GROBID model for structuring monograph document, patent-st36 a patent in XML ST-36 format, etc.

For each structure type - except the default one - some structured might be ignored because they are not textual or it does not make sense to apply a generic entity extraction, and some will be relevant. Ideally this could be specified in some config files.

@kermitt2
Copy link
Owner Author

kermitt2 commented Feb 8, 2022

structure query parameter is implemented see https://nerd.readthedocs.io/en/latest/restAPI.html#structure

@kermitt2 kermitt2 closed this as completed Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant