Referenced from Dave's comment on the parent ticket:
Create New Library:
When we get to the "create" screen, there's a point at which we've uploaded and read/restored the contents of the backup archive, but the library itself doesn't exist yet:
We actually have a decent representation for this state in the data model. This will mean that there exists a Learning Core LearningPackage that we've restored the contents of the archive into, but there is no edx-platform ContentLibrary pointing to it. It is usually the case that LearningPackage.key would be derived from the ContentLibrary.org and ContentLibrary.slug, but they can be set separately for the purposes of this kind of upload staging.
Referenced from Dave's comment on the parent ticket:
Create New Library:
When we get to the "create" screen, there's a point at which we've uploaded and read/restored the contents of the backup archive, but the library itself doesn't exist yet:
We actually have a decent representation for this state in the data model. This will mean that there exists a Learning Core LearningPackage that we've restored the contents of the archive into, but there is no edx-platform ContentLibrary pointing to it. It is usually the case that LearningPackage.key would be derived from the ContentLibrary.org and ContentLibrary.slug, but they can be set separately for the purposes of this kind of upload staging.