...
destination
source
configuration
import filters
destination collections
auto-publish (auto-publish if no errors?)
owner
status
created
manifest extracted
staged
running
complete
reverted
summary
errors
Actions
Notes
Error Handling
Unrecognized Content
Different sites may be customized to support different content types. If we receive such content, our approach is to add the raw OLX data and assets, but to display a generic error message when trying to work with that content later in the library.
Malformed Content
Question: What do we do with content that we know is broken, e.g. a ProblemBlock defined with broken XML? Import it in its broken state, but flag it as an error? Refuse to import the broken item, but allow the rest of the import to succeed? Fail the import as a whole to keep the import operation atomic?
Add/Update vs. Replace: Differences in Library vs. Course Import
...
Advanced OLX-only Features
Historically, some advanced features cannot be accessed through the normal Studio editors, and would require manual editing of the OLX XML format of our content files, followed by an import.