Dsc 807

This request includes updates to the EAD work flow routes and screens:
- The EAD collection creation logging is now recorded in a EAD job.
- The EAD collection log will be show through show job details and edit job details screens.
- The EAD job edit screen allows a EAD file to be uploaded, and the JobsController will call Amberdb to attach EAD copies and create the work collection from EAD if the EAD file is successfully uploaded.
- Upon any processing error during the work collection creation, the JobsController will rollback the changes in Amberdb to ensure no EAD copies are attached to the top level collection work and no works are created under the collection work.
This field is used internally to direct an 'Existing single material' job to its correct controller.
An 'Existing single material' job can be processed by 2 different workflows: the 'new' workflow (which essentially is creating new children and uploading files to them), and the 'bulk' workflow (which is uploading to the objects themselves without creating children)
For books, it's easy because we don't allow uploading to the item level. But for other collections, we allow uploading to the item itself, or creating children and uploading to these children.
If we don't have this field, we'll need to put more semantics in to jobType which is already messy now!