One of the configuration goal of Dynamic Evidence is to provide an administrative-time to reduce complexity in developing and maintaining the artefacts that Cúram Administrators need to define. Initially this was targeted at customers who did not have development installations of Cúram, in that after creation or maintenance of Dynamic Evidence Type Versions, the database would be the 'system of record' for these administrated and generated artefacts; database backups would ensure that this data was persisted.
As discussed previously, Dynamic Evidence Type can evolve over time. For example, a change in legislation may require that a new Evidence attribute must now be recorded, starting from a specified date. Dynamic Evidence supports this requirement by using Dynamic Evidence Type Versions to record modifications to metadata over time. As Metadata evolves, It was necessary for customers with Cúram development projects to import and export the configurable Metadata using Cúram Data Manager. This way once the database was recreated (a typical development-time activity in Cúram), any Dynamic Evidence Type Versions would be persisted and would not have to be recreated every time.
To assist in this effort, a Dynamic Evidence Metadata Loader tool has been provided in Cúram version 6.0.5.0. This tool provides two features:
Download: This tool downloads Dynamic Evidence Metadata information of an effective date from a run time Cúram database, and writes Metadata information in an XML file to the file system.
Upload: This tool uploads Dynamic Evidence Metadata information for an effective date from a file system and updated a record to a run time Cúram database.