Content Import Resolution Tool

We can encounter failures while importing content/data in Asta7 for several reasons. So far our approach for handling failures has been to throw an exception and abort the import. But this approach is not user-friendly as most of the failures are recoverable.

We want a tool to handle imports better to ease the mobility of archives between different Asta7 installations and within the same Asta7. The tool should be based on current functionality in Asta5 and adapted to the challenges we have in Asta7.

Failures and Possible Solutions

Normal Entities

Failure	Solutions	Challenges
AMID conflict	Regenarate	Replace all `objectReference`
PK conflict	Regenaret if UUID Input from the user	Replace all FK How to handle composite PK?
Unique conflict	Regenarate if UUID Input from the user Set `null` if nullable
FK conflict	Set `null` if nullable
NULL conflict	Regenarate if UUID Input from the user
Wrong type	Regenarate if UUID Input from the user Set `null` if nullable
Wrong length	Input from the user Remove extra Set `null` if nullable
FVP Unique conflict	Regenarate Input from the user

System Entities

For simplicity and user-friendliness, we should only consider the AKTOR entity for this section and ignore AMID/PK conflicts for all participant module sub-entities. For the AKTOR entity, we should add some additional options for handling AMID/PK/Unique/FVP Unique conflicts.

Failure	Solutions	Challenges
AMID/PK/Unique/FVP Unique conflict	Ignore	Ignore the whole subtree for this row Should we consider the possible new sub-entity objects? Should we consider the possible changes for this subtree?

Note: This additional option can be applied to normal entities as well, but would that be meaningful?

Content Import Resolution Tool

Failures and Possible Solutions

Normal Entities

System Entities

Implementation