I did a brief search of the code, and this appears to be a missing
feature. That is: the harvesting code builds a WorkspaceItem and
installs it directly, ignoring workflow.
It seems reasonable to me that one might wish to enable or disable
workflow for harvesting, but it will require some development. I
would suggest that you file a feature-request Issue on Github.
It seems to me that workflow should be on every path by which an Item
enters the repository. Perhaps it should be factored out of
submission, harvest, import etc. into a class which is common to them
all.
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
library.indianapolis.iu.edu