Home

New facts about the WINGS_PROVENANCE_EXPORT V_2.0:

BUGS SOLVED:

1. hasRules has been exported in OPMW in the retrieval of components in the creation of the Abstract Template.
2. isConcrete has been exported in OPMW in the retrieval of components in the creation of the Abstract Template.
3. isCollection has been exported in OPMW in the retrieval of the data variables in the creation of the Abstract Template.

CREATION OF THE EXPANDED TEMPLATE:

1. The expanded template has been created only if there are abstract components available or else it is ensured that its creation does not take place. This has been handled with the public boolean ExportExpandedTemplate() function.
2. The expanded template gets created in a systematic and consistent manner, similar to the abstract template with the P-PLAN relations maintained (public String createExpandedTemplate(String accname,String expandedTemplateName,String expandedTemplateURI,String templateName)).
3. The URIs are all maintained consistent within the entire export.
4. Currently we have relations between the executions and expanded template (if only the expanded template is created). Further relations between the expanded template and abstract template also.

Important Factor for Expanded Template Creation:

The current naming scheme for the expanded template is: ABSOLUTE_NAME_FOR_EXPANDED_TEMPLATE+"_"+HASHED_VALUE_FOR_NAMES_OF_SORTED(ALPHABETICALLY)_COMPONENTS

VALIDATIONS:

1. There is a new folder called Validations created present inside the src folder.
2. There are tests for counting the number of templates, expanded templates and executions that are inserted in a local directory folder.