[AIRAVATA-3211] Assign wildcard matches to OutputDataObjectType instead of creating new ones

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: helix implementation
• Assignee: Marcus Christie
• Reporter: Marcus Christie
• Created: 17/Sep/19 16:37
• Updated: 02/Dec/19 15:14
• Resolved: 02/Dec/19 15:14

Description

Currently the OutputDataStagingTask handles wildcard matches by adding additional OutputDataObjectTypes to the Experiment model. The problem with this is that this breaks the association between the name of the original OutputDataObjectType and these newly created ones. The output view providers (AIRAVATA-3029) functionality in the Django portal uses this association to be able to register custom output view providers as metadata of the OutputDataObjectType in the Application Interface and have those applied to experiments that completed before the custom output view provider was registered (the experiments will have a copy of the OutputDataObjectType metadata for their outputs, but won't get any updates to metadata so portal code looks at the original Application Interface to see if there are any other output view providers registered).

Instead I propose:

• if the output type is URI, then take the first wildcard match, create DataProduct and set the data product URI as the value of the output. This will overwrite the wildcard pattern in the value field, but that should be okay since the wildcard pattern is no longer needed.
• if the output type is a URI_COLLECTION, then create DataProducts for all matching files and set the value to a comma delimited string out data product URIs.

TODO

• [ ] Test wildcard matches with multiple matches and URI_COLLECTION type
• [x] Any wildcard matches that were intended to match multiple files should be switched to URI_COLLECTION type