Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / inab/fega-mm issues and pull requests
#46 - Update 3_2_incoming_and_outgoing_data_and_metadata_flow.md
Pull Request -
State: closed - Opened by lauportell over 2 years ago
#45 - Update 3_2_incoming_and_outgoing_data_and_metadata_flow.md
Pull Request -
State: closed - Opened by lauportell over 2 years ago
#45 - Update 3_2_incoming_and_outgoing_data_and_metadata_flow.md
Pull Request -
State: closed - Opened by lauportell over 2 years ago
#44 - Update 2_1_data_protection_policies_at_the_federated_ega_node.md
Pull Request -
State: closed - Opened by lauportell over 2 years ago
#44 - Update 2_1_data_protection_policies_at_the_federated_ega_node.md
Pull Request -
State: closed - Opened by lauportell over 2 years ago
#43 - Update 1_3_sustainability_model_of_the_federated_ega_node.md
Pull Request -
State: closed - Opened by lauportell over 2 years ago
#43 - Update 1_3_sustainability_model_of_the_federated_ega_node.md
Pull Request -
State: closed - Opened by lauportell over 2 years ago
#42 - Fix typos
Pull Request -
State: closed - Opened by mshadbolt over 2 years ago
#42 - Fix typos
Pull Request -
State: closed - Opened by mshadbolt over 2 years ago
#41 - Include Acknoledgement
Issue -
State: closed - Opened by scapella over 2 years ago
#41 - Include Acknoledgement
Issue -
State: closed - Opened by scapella over 2 years ago
#40 - Add a new column to reflect the indicators that are related ("Connected with" in the spreadsheet)
Issue -
State: closed - Opened by lauportell over 2 years ago
- 1 comment
#40 - Add a new column to reflect the indicators that are related ("Connected with" in the spreadsheet)
Issue -
State: closed - Opened by lauportell over 2 years ago
- 1 comment
#39 - [4.2] Technical Benchmarking
Issue -
State: open - Opened by lauportell almost 3 years ago
- 3 comments
Labels: Open to discussion
#39 - [4.2] Technical Benchmarking
Issue -
State: open - Opened by lauportell almost 3 years ago
- 3 comments
Labels: Open to discussion
#38 - [4] Technical Infrastructure
Issue -
State: open - Opened by lauportell almost 3 years ago
- 2 comments
#38 - [4] Technical Infrastructure
Issue -
State: open - Opened by lauportell almost 3 years ago
- 2 comments
#37 - [4.4.2] Realibility / Security
Issue -
State: open - Opened by lauportell almost 3 years ago
- 3 comments
Labels: Open to discussion
#37 - [4.4.2] Realibility / Security
Issue -
State: open - Opened by lauportell almost 3 years ago
- 3 comments
Labels: Open to discussion
#36 - [2.3.1] Data Processing Agreement (DPA) is available to users
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 9 comments
Labels: Open to discussion
#36 - [2.3.1] Data Processing Agreement (DPA) is available to users
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 9 comments
Labels: Open to discussion
#35 - [2.1.2] Risk and Vulnerability Analysis perfomed (Level 5)
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 2 comments
Labels: Open to discussion
#35 - [2.1.2] Risk and Vulnerability Analysis perfomed (Level 5)
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 2 comments
Labels: Open to discussion
#34 - [4.3.1] Storage Capacity
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 3 comments
Labels: Open to discussion
#34 - [4.3.1] Storage Capacity
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 3 comments
Labels: Open to discussion
#33 - [4.2.2] Stress Testing
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 2 comments
Labels: Open to discussion
#33 - [4.2.2] Stress Testing
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 2 comments
Labels: Open to discussion
#32 - Update indicator 1.4.1
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#32 - Update indicator 1.4.1
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#31 - Update indicator 4.3.1 and 4.3.2
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#31 - Update indicator 4.3.1 and 4.3.2
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#30 - Update indicator 4.4.1
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#30 - Update indicator 4.4.1
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#29 - Update indicator 4.1.2
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#29 - Update indicator 4.1.2
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#28 - Update indicator 4.3.2
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#28 - Update indicator 4.3.2
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#27 - Update indicator 1.3.2 - Level 2
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#27 - Update indicator 1.3.2 - Level 2
Pull Request -
State: closed - Opened by lauportell almost 3 years ago
#26 - [1.4.1] Implementation, adoption and usage of the Federated EGA node
Issue -
State: closed - Opened by MKonopkoELIXIR almost 3 years ago
#26 - [1.4.1] Implementation, adoption and usage of the Federated EGA node
Issue -
State: closed - Opened by MKonopkoELIXIR almost 3 years ago
#25 - [5.2.1] Establishment of Federated EGA Node team roles
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#25 - [5.2.1] Establishment of Federated EGA Node team roles
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#24 - [4.4.1] Available Capacity - Level 3
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#24 - [4.4.1] Available Capacity - Level 3
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#23 - [4.3.2] Robustness - Level 4
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#23 - [4.3.2] Robustness - Level 4
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#22 - [4.3.2] Robustness - Level 3
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 2 comments
Labels: Open to discussion
#22 - [4.3.2] Robustness - Level 3
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 2 comments
Labels: Open to discussion
#21 - [4.3.2] Robustness - Level 2
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 3 comments
Labels: Open to discussion
#21 - [4.3.2] Robustness - Level 2
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 3 comments
Labels: Open to discussion
#20 - [4.3.2] Robustness - Level 1
Issue -
State: closed - Opened by lauportell almost 3 years ago
#20 - [4.3.2] Robustness - Level 1
Issue -
State: closed - Opened by lauportell almost 3 years ago
#19 - [4.3.1] Capacity - Level 1
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#18 - [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API) - Level 5
Issue -
State: closed - Opened by lauportell almost 3 years ago
#18 - [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API) - Level 5
Issue -
State: closed - Opened by lauportell almost 3 years ago
#17 - [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API) - Level 4
Issue -
State: closed - Opened by lauportell almost 3 years ago
#17 - [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API) - Level 4
Issue -
State: closed - Opened by lauportell almost 3 years ago
#16 - [4.1.2] Interoperability with CEGA microservices implemented (e.g. permissions API, submission API) - Level 3
Issue -
State: closed - Opened by lauportell almost 3 years ago
#15 - [4.4.2] Realibility / Security
Issue -
State: open - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#15 - [4.4.2] Realibility / Security
Issue -
State: open - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#14 - [4.4.1] Available Capacity
Issue -
State: closed - Opened by lauportell almost 3 years ago
#14 - [4.4.1] Available Capacity
Issue -
State: closed - Opened by lauportell almost 3 years ago
#13 - [4.3.1] Capacity
Issue -
State: closed - Opened by lauportell almost 3 years ago
#13 - [4.3.1] Capacity
Issue -
State: closed - Opened by lauportell almost 3 years ago
#12 - [4.2.1] Compliance testing
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#12 - [4.2.1] Compliance testing
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#11 - [3.3.1] Assessment of the Data Content Quality
Issue -
State: closed - Opened by lauportell almost 3 years ago
Labels: Open to discussion
#11 - [3.3.1] Assessment of the Data Content Quality
Issue -
State: closed - Opened by lauportell almost 3 years ago
Labels: Open to discussion
#10 - [3.2.3] Mechanisms for sharing medatata and other operations-oriented information are established between the federated EGA node and Central EGA - Level 3
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 2 comments
Labels: Open to discussion
#9 - [3.2.3] Mechanisms for sharing medatata and other operations-oriented information are established between the federated EGA node and Central EGA
Issue -
State: closed - Opened by lauportell almost 3 years ago
Labels: Open to discussion
#8 - [3.2.1] Incoming Data flow in the federated EGA node is established - Level 4
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#7 - [3.2] Incoming and outgoing data & metadata flow
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#6 - [3.1.3] Risk register/assessment implemented
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#5 - [1.3.2] Long-term sustainability (Level 3)
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 3 comments
#4 - [1.3.2] Long-term sustainability - Level 3
Issue -
State: closed - Opened by lauportell almost 3 years ago
- 1 comment
Labels: Open to discussion
#3 - [1.3.2] Long-term sustainability - Level 2
Issue -
State: closed - Opened by lauportell almost 3 years ago
#2 - All levels should be read independently
Issue -
State: open - Opened by lauportell almost 3 years ago
#1 - Update README.md
Pull Request -
State: closed - Opened by scapella almost 3 years ago