Records stuck in Posted, Draft, or Incomplete status

[torrin47]

We generally understand the rationale behind the implementation of #76 and #181 even though they're not terribly useful for us because we're not harvesting external sources - if one of our records has validation errors, we need for it to be corrected at the harvest source rather than in our geoportal database.

What's problematic for us is that we're seeing many records appearing with status of Posted (23), Draft (216), or Incomplete (3) as their status, even though our settings for their parent repositories include:
"Automatically approve newly acquired resources" enabled and
"Publish as draft if validation failed" disabled.

There's no indication of why these records were assigned these statuses, the most recent harvesting reports claim the records are valid (though it's possible that at some point there was a validation error in the records that was subsequently fixed). It would be preferable to disable the draft/incomplete status functionality altogether than to have them sit in the database with an ambiguous status and no clear path forward. Any thoughts on why this might be occurring and/or how to address it?