Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 4 additions & 20 deletions DATABASES.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,15 +16,15 @@ Stores user agreements created in Genomics Status, connected to the cost calcula

---

## DEPRECATED: `analysis`
## `application_categories`

Summary statistics from various analysis, likely updated from `Piper` or similar since its not updated anymore. Likely stopped being updated around 2020 or similar.
Listing our application categories and abrevation, with one document per application. Used by the statistics api of genstat which in turn feeds the dashboard.

---

## `application_categories`
## `archiving_status`

Listing our application categories and abrevation, with one document per application. Used by the statistics api of genstat which in turn feeds the dashboard.
A database to track the archiving status of all flowcells handled by the encryption and archiving scripts introduced with Project Helix. Updated by dataflow_encrypt until the status is set to `encrypted`, and then by dataflow_archive which is run nightly.

---

Expand Down Expand Up @@ -65,12 +65,6 @@ Flowcells database for the Element Bioisciences sequencing instrument. Created b

---

## DEPRECATED `expected_yields`

One document per run mode and sequencer. Not sure where this is used.

---

## [NOT UPDATED] `flowcells`

Illumina flowcells database used for pre HiSeq-X. Not updated after 2016. But still searchable in genstat and also likely possible to list in project lists.
Expand Down Expand Up @@ -167,10 +161,6 @@ Never made it into use, was supposed to keep track of sample requirements for di

---

## [DEPRECATED] `samples`

Seems to track and document QC runs. Seems to have stopped udpating around 2016.

## `sensorpush`

Uploades time series data for our freezers and fridges that are connected with a sensorpush sensor. One document per sensor and 24h. Data is uploaded by a script running on ngi_internal polling the sensorpush API. We suspect that the API isn't great and sometimes misses out data, but it could also be sensors that drop out.
Expand All @@ -191,12 +181,6 @@ Keeps track of which items have been added to the suggestion box. Keeps a link t

---

## [DEPRECATED] `taca_flowcells`

Abandoned project for taca to uploade flowcells I think. Only one document and uploaded 2015.

---

## `userman`

Database to keep track of the Charon users.
Expand Down
5 changes: 5 additions & 0 deletions StatusDB_views/archiving_status/lookup/encrypted_runs.map.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
function (doc) {
if (doc.status === "encrypted") {
emit(doc._id, doc.status);
}
}
5 changes: 5 additions & 0 deletions StatusDB_views/archiving_status/lookup/pending_runs.map.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
function (doc) {
if (doc.status === "pending") {
emit(doc._id, doc.status);
}
}
3 changes: 3 additions & 0 deletions StatusDB_views/archiving_status/lookup/runfolder_id.map.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
function (doc) {
emit(doc._id);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we have these in quite a few databases, but I don't think they're actually needed. Statusdb allows direct lookup of the doc._id without this view. Or am I missing something?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, right. I use this view in the encryption script. I could rewrite it, but maybe it's ok to keep that way for now?

}
Loading