GridProtectionAlliance/openECA

Mapping Generation Wizard (i.e. Export Data)

Opened this issue · 0 comments

The openECA client contains a wizard for exporting user defined mappings. There are three issues here:

  1. As it stands, only the mappings that are selected are saved to the file. This should be changed (or an option added) so that the mappings are included recursively. For example, If I have one top level mapping made up of many sub-mappings, i should only need to select the top level mapping when creating the export file.
    What I am trying to avoid with this exercise is using the Project Generation Wizard to create the UserDefinedMappings.ecamap file for an analytic during the deployment phase.

  2. The file extension of the exported file should match the data type. As it stands, only *.txt is exported. Should use *.ecamap and *.ecaidl.

  3. I should be able to import top-level mappings (i.e. with only FILTER expressions) as part of the analytic deployment procedure. For example, I want to ship a mappings file (with only FILTER expressions) that contains no sensitive data and then have the customer import that file as easily as they import a data structures file. Right now it appears that I cannot do this. Perhaps I missed something.

Thanks,
Kevin