Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ADR for metaP mongo data #920

Merged
merged 2 commits into from
Nov 8, 2024
Merged
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
31 changes: 31 additions & 0 deletions decisions/0017-metaP-mongodata.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
# Update these YAML values so they describe this decision. Delete the leading `→` characters.
status: accepted
date: 2024-10-06
deciders: Shreyas Cholia, Katherine Heal, Alicia Clum, Sam Purvine
consulted: Paul Piehowski, Lee Ann McCue, Mark Miller
informed: Everyone in Metadata meeting
---
# Metaproteomics results data should not be in Mongo
## Context and Problem Statement

There are large mongo data records for metaproteomics workflow activities, this causes issues for the API and elsewhere and is not sustainable.


## Considered Options

* **Rework Aggregation Scripts**

Rewrite the aggregation scripts to access the Metaproteomics processed data (not just the mongo records about those data).

* **Bypass Aggregation Scripts**

Modify the Metaproteomics workflow to directly write the FunctionalAnnotationAggMember records (originally written by aggregation script).


## Decision Outcome

Chosen option: "**Rework Aggregation Scripts**", to maintain modularity of the aggregation process.

We will also rewrite the aggregation script to use the API rather than directly access mongoDB.