Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapping Generation Wizard (i.e. Export Data) #46

Open
kdjones opened this issue Oct 9, 2017 · 0 comments
Open

Mapping Generation Wizard (i.e. Export Data) #46

kdjones opened this issue Oct 9, 2017 · 0 comments

Comments

@kdjones
Copy link

kdjones commented Oct 9, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant