Uploaded image for project: 'OODT'
  1. OODT
  2. OODT-725

CAS-PGE should not pass global metadata keys from Workflow to CAS-Crawler from reserved key set

    XMLWordPrintableJSON

Details

    • Don't Know (Unsure) - The default level

    Description

      Currently CAS-PGE adds all Workflow global metadata to CAS-Crawler before invoking it when it runs its ingestCrawler. This can cause a big issue on WorkflowNotifications from CAS Crawler e.g., by its TriggerPostIngestWorkflow or UpdateWorkflowStatusToIngest actions b/c they pass along to the workflow dynamic metadata the "Filename" keyword. This is great for staging the input for the next set of workflow tasks, but it messes up ingestion since CAS-PGE passes this information to CAS-Crawler before ingesting the outputs of the CAS-PGE task. Having the upstream Filename met field screws up the Crawler since it thinks that the filename for the ingest product is actually the preceding one instead of the one generated and being crawled.

      CAS-PGE should NOT pass dyn workflow metadata to CAS-Crawler's global metadata on reserved keywords like Filename, FileLocation, ProductName and ProductType.

      Attachments

        Issue Links

          Activity

            People

              chrismattmann Chris A. Mattmann
              chrismattmann Chris A. Mattmann
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: