Compound CSV: new options for MODS.xml

[bondjimbond]

Given the issue raised here: https://jira.duraspace.org/browse/ISLANDORA-2194

Since default Islandora behaviour is to essentially ignore/hide the metadata on the compound parent object and instead display the first child, MIK should have the option to use the parent metadata (excluding the label) for child objects that don't have their own CSV rows.

[mjordan]

If the intent is to assign the parent metadata to the first child, I suggest that we develop a post-write hook script to copy the parent's MODS.xml into the directory if its first child object. That way, we don't need to introduce complex logic into the CSVCompound writer (it's already quite complicated). We can also reuse the same post-write hook script for compound objects created from CONTENTdm.

[mjordan]

Forgot to add, overwriting the first child's metadata with the parent's begs the question of what to do if there is already a MODS.xml file for the child.