You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have several recent or incoming datasets which contain descriptions but not currently any data, and it has been proposed that we should flag these in some way in the portal.
My suggestion here is
add an optional field to DATS.json under extraProperties, called comingSoon, containing a short description of the dataset status (not just a simple yes/no flag, a string would allow us to include e.g. an expected date if we have one)
modify the portal to check for the existence of this field:
IF there is no comingSoon value THEN proceed exactly as before
IF there is a comingSoon value THEN display that (and possibly adjust other aspects of the card to make this visually clearer - remove some elements, or use lighter colours for a "faded" effect to suggest that the dataset is not currently active? Design input sought here.)
The text was updated successfully, but these errors were encountered:
We have several recent or incoming datasets which contain descriptions but not currently any data, and it has been proposed that we should flag these in some way in the portal.
My suggestion here is
DATS.json
underextraProperties
, calledcomingSoon
, containing a short description of the dataset status (not just a simple yes/no flag, a string would allow us to include e.g. an expected date if we have one)IF there is no
comingSoon
value THEN proceed exactly as beforeIF there is a
comingSoon
value THEN display that (and possibly adjust other aspects of the card to make this visually clearer - remove some elements, or use lighter colours for a "faded" effect to suggest that the dataset is not currently active? Design input sought here.)The text was updated successfully, but these errors were encountered: