From a916b43d8643706922c91d8166905379bdfd8667 Mon Sep 17 00:00:00 2001 From: Katherine Heal Date: Wed, 6 Nov 2024 14:28:47 -0800 Subject: [PATCH 1/2] Add ADR for metaP mongo data --- decisions/0017-metaP-mongodata.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 decisions/0017-metaP-mongodata.md diff --git a/decisions/0017-metaP-mongodata.md b/decisions/0017-metaP-mongodata.md new file mode 100644 index 0000000..402bfe8 --- /dev/null +++ b/decisions/0017-metaP-mongodata.md @@ -0,0 +1,30 @@ +--- +# 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 +--- +# {short title of solved problem and solution} + +## 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. + From e39a1129fa48463b111a684d844cfceb8cbe6f07 Mon Sep 17 00:00:00 2001 From: Katherine Heal Date: Wed, 6 Nov 2024 14:33:15 -0800 Subject: [PATCH 2/2] Update 0017-metaP-mongodata.md --- decisions/0017-metaP-mongodata.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/decisions/0017-metaP-mongodata.md b/decisions/0017-metaP-mongodata.md index 402bfe8..73d7553 100644 --- a/decisions/0017-metaP-mongodata.md +++ b/decisions/0017-metaP-mongodata.md @@ -6,8 +6,7 @@ deciders: Shreyas Cholia, Katherine Heal, Alicia Clum, Sam Purvine consulted: Paul Piehowski, Lee Ann McCue, Mark Miller informed: Everyone in Metadata meeting --- -# {short title of solved problem and solution} - +# 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. @@ -15,16 +14,18 @@ There are large mongo data records for metaproteomics workflow activities, this ## Considered Options -* {Rework Aggregation Scripts} -- Rewrite the aggregation scripts to access the Metaproteomics processed data (not just the mongo records about those data). +* **Rework Aggregation Scripts** + +Rewrite the aggregation scripts to access the Metaproteomics processed data (not just the mongo records about those data). + +* **Bypass Aggregation Scripts** -* {Bypass Aggregation Scripts} -- Modify the Metaproteomics workflow to directly write the FunctionalAnnotationAggMember records (originally written by aggregation script). +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. +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.