Make Deidentifier Requests to Annotators Robust #133
Description
Is your proposal related to a problem?
When the deidentifier backend makes a request to an annotator (which can be user-submitted) that doesn't respond successfully (i.e. the annotator has an error on a request), the deidentifier fails non-gracefully.
Describe the solution you'd like
When a call to an annotator fails, the deidentifier should apply and return the successful annotation calls, as well as information about which calls were successful. The HTTP status would be something different than complete success, e.g. HTTP 207.
Describe alternatives you've considered
Alternatively, the deidentifier call could still fail if an annotator call fails, but it could fail more gracefully, giving a more informative message than a simple HTTP 500