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

Improvements to core in order to support QuickSet Strip functionality



    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Cloud 1
    • Component/s: None
    • Labels:


      The current (provisional) designs for the QuickSet Strip are housed at https://drive.google.com/drive/u/5/folders/1ehtE4g9kvNvwJQBucae9uIDVIxIT8035 - work is underway on a "Level 0" implementation which simply reuses the existing payloads developed for use with the PSP, but the design includes some features which will need some core work in order to support better:

      i) The current QSS UX allows for some changes to be made to the system without a user keyed in. This is outside the scope of the current core, which requires an active GPII user session. One possible implementation scheme would have a special user session, "noUser" assumed by the system to be keyed in when no other user was. However, we should note that for our initial pilots, it is likely that some user will be keyed into the system at all times via the SSO integration we are planning, so this implementation might be initially unnecessary.

      ii) The designs allow for "immediate application" of a snapset-like set of preferences, without causing a change in key-in state. It's unclear yet whether this requires any interaction with the existing snapset definitions, or whether this will be a matter templated in the QSS implementation itself. In the end the QSS entire configuration will be JSON template-driven in a way which presumably can be stored within the user's preference set, and so this issue of snapset-like preferences will manifest differently - these will either rely on symbolic references to locations in the core snapsets, or to other preference sets within the user's safe.

      These requirements also relate to https://issues.gpii.net/browse/GPII-2956 for "one-way keys" since this is another area where the core's assumptions about the one-to-one linkage between key-in state and system state will have to be broken up. We should think about these issues at the same time.


          Issue Links



              jhernandez Javier Hernández
              amb26 Antranig Basman
              0 Vote for this issue
              2 Start watching this issue