Javier Mansilla
Javier Mansilla
Default behavior is to just log some info about each error, and proceed. For debugging, it's useful to be able to have errors raised up to the face.
If you have a Feature producing instances of long integers, the flattener will fail to process it.
If you have a Feature producing instances of decimal.Decimal, the flattener will fail to process it.
Error is raised when clicking on the first EntityOccurrence. (using firefox 37.0.2) "Error: event is not defined $scope.eo_click@http://localhost:8000/static/js/document_questions.js:196:1 fb.prototype.functionCall/
Right now, EO-alias is made up by concatenating involved tokens.
On documentation is not completely clear that once you run the preprocess you can already browse and edit the processed data.
Right now our LiteralNER is _very_ literal, so in some cases is not working. Example: an entry like this ``` takayasu's arteritis ``` Is never found because the documents will...
Follow up of #1067
Given that behind the scenes we are having syntax sugar for a CharField with some fixed choices, I was expecting the same behavior, which is: any change on the choices...