errors in tei_to_es about datura

[techgique]

@jduss4 I was working on CSV to ES transform and posting (https://github.com/CDRH/data_stories_humanity/commit/a2f2708f397e65b9d6b8e1f917ff1c744d016daa) and committed some ideas that relate to ameliorating error frustration and were helpful in my headscratching: https://github.com/CDRH/datura/tree/feature/debugging

[jduss4]

This commit begins to address this issue, but I would like it to be more specific and more robust.

220a88b

[jduss4]

These are still bad, bumping in 2019

[techgique]

Still troublesome in 2020 😜 I was running into it with #171 while working on Whitman Elasticsearch indexing revisions and having to comment/uncomment individual field method overrides to identify which causing the error.

We discussed outputting the original error message and perhaps optionally displaying a full traceback if -v verbose option is set with the command.

Jess pointed at a few places where this could be addressed:

• https://github.com/CDRH/datura/blob/dev/lib/datura/file_type.rb#L52
• https://github.com/CDRH/datura/blob/dev/lib/datura/file_type.rb#L137
• https://github.com/CDRH/datura/blob/dev/lib/datura/data_manager.rb#L308