Can we think of other solutions? I'd like the stage to only have a single download stage.
Do i see it correctly, that the docs_blob url is available at the time we create the declarative content? Can we make it a second declarative artifact that we extract again before saving? Or we introduce a DeclarativeBlob that is also downloaded in the artifact_download stage. Is the docs blob meant to be an attached artifact for the content unit?

Can we think of other solutions?

Yes, this is a quick fix for the problem noticed by David after looking into total count.

I'd like the stage to only have a single download stage. Do i see it correctly, that the docs_blob url is available at the time we create the declarative content?

Yes, it's available on the collection version metadata. It's optional though, so it is not always present.

Can we make it a second declarative artifact that we extract again before saving? Or we introduce a DeclarativeBlob that is also downloaded in the artifact_download stage. Is the docs blob meant to be an attached artifact for the content unit?

DocsBlob is a JSON field on the collection-version model. It can't be added as a second declarative artifact without a serious rework. We could however just override the first downloader stage and have it download the docs-blob with the artifact if the url is present.

Do you want me to look into merging this downloader stage into the first artifact downloader stage?

Do you want me to look into merging this downloader stage into the first artifact downloader stage?
Yes, I would prefer that.

I was thinking about a stage between ArtifactDownloader and ArtifactSaver that would find the "extra" d_artifact and turn it into the docs_blob.

This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution!

This pull request has been closed due to inactivity. If you feel this is in error, please reopen the pull request or file a new PR with the relevant details.