Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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

Failure

Solutions

Challenges

AMID conflict

  • Regenarate

  • Ignore row

  • Replace all objectReference

  • For removing

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

  • No labels