Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-2619

NP sets should support scoped common terms

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      The NP sets currently do not support common terms scoped to applications (i.e. within application blocks). This is need for the PCP.

      The functionality we want is:

      • If there are common terms inside an application block, these should be used as input for the transformations (with higher priority than top-level common terms - i.e. an application specific common terms value is used over a top level common terms value)
      • Common terms in an application block should be filtered based on the solutions inputPaths and capabilities
      • Inferred common terms are handled as usual but these will be supplemented by the common terms form the application specific block
      • No common terms should be passed as settings handlers

      Secondarily, we want the all non-common terms values within an application specific block to be considered an application term (or whatever the hell they are called) and also go through the transformer. The only settings that make it to the settingshandlers are ones that have been passed through the transformer

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jhernandez Javier Hernández
              Reporter:
              kasper Kasper Markus
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: