add filter for outcomes relevant to the adoption table

_data/outcomes.yml

@@ -7,6 +7,7 @@
   doi: 10.5281/zenodo.7684470
   last-update: 2023-02-28
   keywords: standard, metadata, PID, search
+  adoption-table-relevant: true
 
 - name: Nexus ontology
   short-name: Nexus-O
@@ -34,6 +35,7 @@
   doi: 10.5281/zenodo.7743913
   last-update: 2023-03-17
   keywords: search, catalogue
+  adoption-table-relevant: true
 
 - name: OAI-PMH endpoint for data catalogues
   short-name: OAI-PMH
@@ -43,6 +45,7 @@
   doi: 10.5281/zenodo.7789134
   last-update: 2023-03-31
   keywords: standard, metadata, search, catalogue
+  adoption-table-relevant: true
 
 - name: PaN training catalogue
   short-name: PaN-training
@@ -52,6 +55,7 @@
   doi: 10.5281/zenodo.7732603
   last-update: 2023-03-14
   keywords: training
+  adoption-table-relevant: true
 
 - name: VISA
   short-name: VISA
@@ -61,6 +65,7 @@
   doi: 10.5281/zenodo.7788839
   last-update: 2023-03-31
   keywords: data analysis, compute, data access
+  adoption-table-relevant: true
 
 - name: PaN FAIR implementation framework
   short-name: FAIR-IF
@@ -70,6 +75,7 @@
   doi: 10.5281/zenodo.7804712
   last-update: 2023-04-12
   keywords: FAIR, data policy, metadata, DMPs, PIDs, FAIR assessment, RDM
+  adoption-table-relevant: true
   
 - name: Testing and validation framework
   short-name: T&V-F
@@ -79,3 +85,5 @@
   doi: 10.5281/zenodo.7867091
   last-update: 2023-05-04
   keywords: research software, data analysis, testing, validation, software quality
+
+

outcomes.html

@@ -34,7 +34,7 @@ The adoption status of these outcomes by our member facilities is shown <a href=
 {% endfor %}
 
 <h1 id="adoption-table">Adoption status</h1>
-{% assign adoption_outcomes = site.data.outcomes | sort_natural %} <!-- must be filtered according to need for a facility-based adoption or not -->
+{% assign adoption_outcomes = site.data.outcomes | sort_natural | where:"adoption-table-relevant",true %}
 <table>
   <tr>
     <th><strong>Facility</strong></th>