inab/fega-mm

Issues

• Be consistent with either American English or British English spelling

  #98 opened a year ago by malloryfreeberg
  0

• [5.2.1] Modify Training and Capacity Building indicator name

  #78 opened a year ago by malloryfreeberg
  2

• [5.1] Clarify SOP acronym

  #76 opened a year ago by malloryfreeberg
  2

• [5.1.1] Internal node operation SOPs defined and documentation available

  #67 opened a year ago by lauportell
  1

• [5.1.3] Helpdesk working using FEGA SOPs

  #81 opened a year ago by malloryfreeberg
  0

• [5.2.1] "Training and capacity building" indicator is not very agile

  #80 opened a year ago by malloryfreeberg
  0

• [2.3.1] Data Processing Agreement (DPA) is available to users

  #36 opened 2 years ago by lauportell
  9

• [6.2.1] Training for the Federated EGA Node users

  #69 opened 2 years ago by lauportell
  0

• [6.3.1] Developed communication package

  #70 opened 2 years ago by lauportell
  0

• [4.2.2] Stress Testing

  #33 opened 2 years ago by lauportell
  2

• [5.1.2] CEGA-FEGA interaction SOPs defined and documentation available

  #68 opened 2 years ago by lauportell
  0

• [4.2.1] Compliance testing

  #62 opened 2 years ago by lauportell
  2

• [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API)

  #61 opened 2 years ago by lauportell
  0

• [3.2.2] Outgoing Data flow in the federated EGA node is established

  #60 opened 2 years ago by lauportell
  0

• Missing from MM: Internal compute capacity?

  #51 opened 2 years ago by malloryfreeberg
  2

• [3.1.4] Security breach/incident response plan defined

  #59 opened 2 years ago by lauportell
  0

• [4] Technical Infrastructure

  #38 opened 3 years ago by lauportell
  2

• [4.2] Technical Benchmarking

  #39 opened 3 years ago by lauportell
  3

• [4.4.2] Realibility / Security

  #37 opened 3 years ago by lauportell
  3

• Include Acknoledgement

  #41 opened 2 years ago by scapella
  0

• [3.1.3] Risk register/assessment implemented

  #6 opened 2 years ago by lauportell
  1

• [4.3.2] Robustness - Level 2

  #21 opened 2 years ago by lauportell
  3

• [4.3.1] Storage Capacity

  #34 opened 2 years ago by lauportell
  3

• [4.2.1] Compliance testing

  #12 opened 2 years ago by lauportell
  1

• Add a new column to reflect the indicators that are related ("Connected with" in the spreadsheet)

  #40 opened 2 years ago by lauportell
  1

• Considering the inclusion of evidence

  #52 opened 2 years ago by scapella
  0

• [5.2.1] Establishment of Federated EGA Node team roles

  #25 opened 2 years ago by lauportell
  1

• [4.4.1] Available Capacity - Level 3

  #24 opened 2 years ago by lauportell
  1

• [4.3.2] Robustness - Level 4

  #23 opened 2 years ago by lauportell
  1

• [4.3.1] Capacity - Level 1

  #19 opened 2 years ago by lauportell
  1

• [3.2.3] Mechanisms for sharing medatata and other operations-oriented information are established between the federated EGA node and Central EGA - Level 3

  #10 opened 2 years ago by lauportell
  2

• [3.2.1] Incoming Data flow in the federated EGA node is established - Level 4

  #8 opened 2 years ago by lauportell
  1

• [2.1.2] Risk and Vulnerability Analysis perfomed (Level 5)

  #35 opened 2 years ago by lauportell
  2

• [1.3.2] Long-term sustainability - Level 3

  #4 opened 2 years ago by lauportell
  1

• [4.4.2] Realibility / Security

  #15 opened 3 years ago by lauportell
  1

• [4.3.2] Robustness - Level 3

  #22 opened 3 years ago by lauportell
  2

• [3.3.1] Assessment of the Data Content Quality

  #11 opened 3 years ago by lauportell
  0

• [3.2.3] Mechanisms for sharing medatata and other operations-oriented information are established between the federated EGA node and Central EGA

  #9 opened 3 years ago by lauportell
  0

• [3.2] Incoming and outgoing data & metadata flow

  #7 opened 3 years ago by lauportell
  1

• [1.4.1] Implementation, adoption and usage of the Federated EGA node

  #26 opened 3 years ago by MKonopkoELIXIR
  0

• [4.3.1] Capacity

  #13 opened 3 years ago by lauportell
  0

• [4.4.1] Available Capacity

  #14 opened 3 years ago by lauportell
  0

• [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API) - Level 3

  #16 opened 3 years ago by lauportell
  0

• [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API) - Level 4

  #17 opened 3 years ago by lauportell
  0

• [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API) - Level 5

  #18 opened 3 years ago by lauportell
  0

• [4.3.2] Robustness - Level 1

  #20 opened 3 years ago by lauportell
  0

• [1.3.2] Long-term sustainability (Level 3)

  #5 opened 3 years ago by lauportell
  3

• [1.3.2] Long-term sustainability - Level 2

  #3 opened 3 years ago by lauportell
  0

• All levels should be read independently

  #2 opened 3 years ago by lauportell
  0