CONP-PCNO/conp-portal

Marking "coming soon" data in the portal.

Open

#550 opened on Jun 3, 2022

View on GitHub
 (1 comment) (0 reactions) (4 assignees)JavaScript (26 forks)auto 404
discussion-requiredenhancementhelp wanted

Repository metrics

Stars
 (9 stars)
PR merge metrics
 (PR metrics pending)

Description

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

  1. 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)
  2. 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.)

Contributor guide

Research direction
Familiarize with the DATS.json schema in the repository, then add a 'comingSoon' field under extraProperties. Next, modify the portal frontend to check for this field and adjust the card display accordingly (e.g., fade or add a badge). Consider design feedback for visual changes.
Tech stack
javascript
Domain
web devbackendfull stack
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60