MD5 in CSV Output

[gleporeNARA]

Currently the CSV output has the SHA256 column header hard coded and only outputs the hash if SHA256 is selected. With the MD5 option available in Parse Options I think it makes sense to rename the CSV column to Hash Value and output whichever hashing algorithm is selected.

[tballison]

Let me take a look.

[tballison]

The column headers (and therefore the values that are dumped) are all controlled in example-digipres-metadata-mappings-jdbc.csv.

The challenge is that you select which digester should run in the GUI, but then you also have to define which columns from the extracted/generated metadata should be written out.

I agree that it would be nicer to only have to specify that once... I'm worried a bit about guessing what the user intended for how they want to map Tika's metadata keys to the output keys. Perhaps we special case this for CSV?

I also noticed that there's some weirdness in modifying the Tika Metadata Key and the Output Metadata Key in the GUI. It felt like the key or the value or both were sticky at times... that's a separate issue.

[tballison]

The stickiness is default behavior of javafx. I'm sure there are workarounds, but I'm don't think I'll pursue them. As long as you type a value into the cell and click return, the update happens correctly. If you type a new value and then click on another cell, the original change is not saved. This isn't great, but so it goes... If this is a high priority, please chime in on #210