-
-
KP.2.2+A22995C(rev), C27382A, T27529C(Orf6:L61I,Orf7a:F46L, S:K478T(rev))
GISAID query: G27382A, T27529C
No. of seqs: 3(Canada 2 USA 1(from India))
First: EPI_ISL_19313873, USA from India, 2024…
-
The goal of this issue is to implement an efficient lineage tracking for `chainweb-data`. Currently, there's no efficient nor straightforward way to deduce lineage information about a block or any dat…
-
**Problem Statement**
Hi, as far as I can see, the Lineage Tracking API is not available in the SDK. I can successfully call the REST API directly. I'm referring to the following endpoints, [document…
-
**Objective:** Discuss the development of a centralized schema catalogue to store and manage multiple schemas and their variations effectively. The catalogue should support easy updates, versioning, a…
-
https://cloud.google.com/bigquery/docs/scheduling-queries
-
**Objective:**
Develop a centralized Data Catalogue to manage simple, non-evolving schemas, along with other metadata and data quality metrics. The solution should provide basic versioning, efficie…
-
Most seqs on this JN.1.11+S:R346T branch are dropouts from KP.2*. However, there seems to be a real branch hiding inside.
JN.1.11+C7979T, A12463G,T21737C,G22599C, T22928C(S:F59L,R346T,F456L)+G25440…
-
**Purpose:**
To track lineage at a record level, we must store metadata in the record itself.
This proposal is for standardizing how to store OpenLineage related metadata in the data. For the scope …
-
KP.2.6+C24106T+C28528T,C22716T(S:T385I)
GISAID query: C24106T,C22716T,C28528T
No. of seqs: 12(Chile 1 USA 1 Ireland 1 Spain 1 UK 8)
First: EPI_ISL_19216707, 2024-6-6, UK
Latest: EPI_ISL_193907…