-
## 💡 Description
Provenance must process documents with archive_status in a list of configurable values, the list of values configured must match with the registry-api configuration (archived…
-
Currently, updating a task leads to the status of that task being "lost" / set to None?.
In the larger work on how to handle statuses, especially with subsets: We should think about this design cho…
-
### Proposed scenario
**GIVEN** a federated architecture setting of multiple FHIR Servers, assigned one of the FHIR servers as the "central",
**WHEN** `google/fhir-data-pipes` sync the FHIR servers …
-
this ticket is not immediately actionable; need to discuss what the correct implementation is.
From my notes in august 15 meeting:
> make sample groups undeletable once they're used in an outlier an…
e-t-k updated
7 years ago
-
**What is the goal / desired outcome?**
Pachyderm doesn't currently have a well-trodden path to implement an iterative algorithm, where a result is recursively refined until it reaches some accepta…
-
# Is your feature request related to a problem? Please describe.
@aidanheerdegen noted yesterday it might be helpful to have a separate catalogue of restarts, so users would be able to easily access …
-
example scenario: check if an image was built from a specific repo, with a specific branch/commit, include certain reviewers, etc
https://slsa.dev/provenance/v0.2
-
Goals:
- Design a system to assign a global version for the code in this repo. (decided on semantic versioning)
- Collect the broker version, and versions of other important packages, in the [metad…
-
Thread to start thinking about how we want to catalogue the data (and therefore integrate with EIDC).
-
The idea is that we want a minimal set of information to be stored in some way that explains where a given set of IRFs comes from: i.e. _provenance_ information by IVOA standards, like input DL2 files…