XML Harvest: Fix inputs

XMLWordPrintable

    • Type: Feature
    • Resolution: Done
    • Priority: Major
    • 1.1.0
    • Affects Version/s: None
    • Component/s: Portal - Curator
    • None

      with the 6/10 version of the questionnaire output, inputs is broken and new attributes are present that require harvesting. This is a summary of what needs to be done:

      a) Ensure we are grabbing the variable name since this is the anchor of the InputCondition object
      b) Ensure we are grabbing both boundary conditions and initial conditions
      c) Ensure we are getting all 5 ICs and BCs
      d) There is a new attribute that METAFOR has added. It is InputTargetComponent. I have added this property hasInputTargetComponent to the esg.owl file already, so it is available for use.
      e) We are now seeing some InputConditions have input files instead of input components. There is a new tag called <type> that indicates whether the source of the input is a component or a file. If it is a component,we will want to put this info into the hasInputSourceComponent.
      If it is a dataobject, then we want to put it into the new property hasInputSourceDataset. I decided to create this property instead of using hasInputDataset b/c the latter actually points to the dataset class and any instance of this attribute will show up in the dataset search.
      f) There is a new input style, ancillary file. We should be able to treat it exactly like a data object IC or BC. We will want to make an new accordion though called "Ancillary Files".

              Assignee:
              Unassigned
              Reporter:
              Sylvia Murphy (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: