Changes needed for migration

[HenningNormann]

Changes needed for migration

App

• Introduce external model vs internal model
• Expand internal (and external?) model
  • Version number (e.g. 2 and 3 for a2 and a3)
  • Blob storage root path (done)
• Application need info about xsls and their internal order (done)
• Code lists referenced from the xsls (done)

Instance/instance event/data element

• Introduce external model vs internal model
• Expand model
  • Version number (e.g. 2 and 3 for a2 and a3)
  • More instanceevent types? (Done)
  • PresentationText also in DataElement (Done with the metadataproperty)
• Support for generating a data element's content on the fly and connect a module to do the generating (Done)
• Hide migrated a3 instances from sbl search
• Support for multiple blobs (and/or accounts) for each service owner (done)

Temporary (Done)

• New controller to upload instances, ievents, data elements and applications (Done)
• Table to store migration state (one row for each a3 service: a2 archive reference and a3 instance guid) (Done)

Misc (Done)

• How to support presentationtexts on the data element level. Current thoughts:
  • Expand internal model for DataElement with property for PresentationTexts
  • Migration program
    • Generate main form values into instance (used for archive title)
    • Generate values for each form into each data element (not used initially, but to avoid to lose significant data)
    • Generate filenames that includes the values for each form

Tasks

Preview Give feedback

1. Make it possible for Storage to access multiple Storage containers/accounts for blob storage based on some rule #438
   kind/feature-request +1