Software publication (and their metadata) may have to be curated, depending on curation workflows at different institutions. We support this by providing a way to produce a normalized metadata set for curation, without drafting or publishing the actual deposit.
Curation policies at institutions
Policies can address different stages of the software development and publishing workflow
Potentially multiple runs
Break until curation is successful
Chosen option: “Potentially multiple runs”, because this is the option that supports our project targets
The workflow is run multiply for different steps depending on requirements (produce curatable metadata set, curate and sign off, draft, publish). This needs to be supported even for curation in target repositories in case of updated drafts. This option includes the scenario where metadata has been curated before the first workflow run and can be published straightaway.
Good, because Covers different curation scenarios
Bad, because Adds complexity / multiple runs
Breaks workflow until curation has been successful, continues in the next run
Good, because Usable for web services
Bad, because Not usable for CI services