diff --git a/docs/adminGuide/add-beacon.md b/docs/adminGuide/add-beacon.md index e94230c..4fdd5d8 100644 --- a/docs/adminGuide/add-beacon.md +++ b/docs/adminGuide/add-beacon.md @@ -20,19 +20,19 @@ nav_order: 2 In this section you will learn how to add a Beacon in the ELIXIR Beacon Network. There are two sections depending on your role: -- User: You are an owner or mantainer of a Beacon and you want to add it to an ELIXIR Beacon Network. -- EBN mantainer: You are an owner or mantainer of an ELIXIR Beacon Network and a Beacon has requested to add their API URL to the network. +- Beacon Owner: You are an owner or mantainer of a Beacon and you want to add it to an ELIXIR Beacon Network. +- ELIXIR Beacon Network (EBN) mantainer: You are an owner or mantainer of an ELIXIR Beacon Network and a Beacon has requested to add their API URL to the network. -## Add a Beacon to a Network (User - Beacon maintainer view) +## Add a Beacon to a Network (Beacon owner view) ### Add an ID -To have an unique identifier in the EBN, you need to create an unique identifier to your Beacon. This ID should be located in the `info` endpoint, inside the `meta` object. Here it is an example: +To being able to classify your beacon in the EBN, you need to create an unique identifier to your Beacon. This ID should be located in the `info` endpoint, inside the `meta` object. Here it is an example: ``` "meta":{ "apiVersion":"vX.X.X", - "beaconId":"es.elixir.bsc.beacon", + "beaconId":"your.beacon.id", "returnedSchemas": {...} } ``` @@ -41,16 +41,16 @@ The `beaconId` must be unique inside the network and it is mandatory to enable i ### Validate your Beacon -Before asking to add your beacon to the network, you should pass your Beacon to the validator. The Validator can be accessed via Frontend in most of the EBN instances, but as it is not mandatory here it will be described how to validate your Beacon via command-line: +Before asking to add your beacon to the network, you should pass your Beacon to the validator. The Validator can be accessed via Frontend in most of the EBN instances, but it is not mandatory. Here it will be described how to validate your Beacon via command-line: To validate a Beacon before adding it to the ELIXIR Beacon Network, follow these steps: -1. Ensure you have Apache Maven installed. +1. Ensure you have [Apache Maven](https://maven.apache.org/) installed. -2. Download the validation tool from the repository and navigate to the `tool` folder: +2. Download the validator repository and navigate to the `tool` folder: ``` -git clone https://github.com/elixir-europe/neat-beacon-v2-validator/tree/master +git clone https://github.com/elixir-europe/neat-beacon-v2-validator cd neat-beacon-v2-validator ``` @@ -75,55 +75,27 @@ Optionally, you can specify an output file for the validation report using the ` ### Send it to the Network -After passing the validator, the Beacon owner has to send an email to the ELIXIR Beacon Network mantainer asking them to add the Beacon to the network. It is recommended to send the validator output, if any, or specify that the Beacon has passed the validation. +After passing the validator, the Beacon owner might need to send an email to the ELIXIR Beacon Network mantainer asking them to add the Beacon to the network. It is recommended to send the validator output, if any, or specify that the Beacon has passed the validation. The Beacon owner is responsible for addressing any errors reported by the validator. While the Beacon may still function within the Beacon Network despite reported errors, critical errors may prevent it from returning data. - - - ELXIIR Beacon Network maintainers may request the output of the validator before adding the instance to the network. - +{: .important } +> ELXIIR Beacon Network maintainers may request the output of the validator before adding the instance to the network. ## Add a Beacon to a Network (ELIXIR Beacon Network mantainer view) The ELIXIR Beacon Network Mantainer is responsible for requesting the validator output file to confirm that any Beacon meets validation criteria to add it to the network. Subsequently, the Beacon owner should forward the validated Beacon's URL to the EBN Maintainer. -Once validated, the EBN Maintainer will incorporate the URL of the Beacon into the ELIXIR Beacon v2 Network. This involves adding the Beacon's URL to the `wildfly/BEACON-INF/beacon-network.json` file. +Then, the EBN Maintainer will incorporate the URL of the Beacon into the ELIXIR Beacon v2 Network. This involves adding the Beacon's URL to the `wildfly/BEACON-INF/beacon-network.json` file. The structure of this JSON file should be an array containing the URL of the validated Beacon, like this: ``` [ - "your.beacon.url/api" + "new.beacon.url/api" ] ``` After adding the URL to the `beacon-network.json` file, the Beacon Network will automatically fetch the new Beacon, ensuring its integration into the network. This process facilitates the incorporation of Beacons into the ELIXIR Beacon Network. To remove the Beacon, you just need to remove the URL from the `beacon-network.json` file. - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/adminGuide/beacon-aggregator.md b/docs/adminGuide/beacon-aggregator.md index 59f1ee7..22afc85 100644 --- a/docs/adminGuide/beacon-aggregator.md +++ b/docs/adminGuide/beacon-aggregator.md @@ -22,7 +22,7 @@ The Beacon Aggregator (BA) is the agent in charge of querying the Beacons of the ## Meta-Beacon -The Beacon Aggregator is itself a standard Beacon v2. As it is created to query other Beacons, it is referred to as Meta-Beacon. +The Beacon Aggregator is itself a standard Beacon v2. As it is created to query other Beacons, it is also referred to as Meta-Beacon. In order to differentiate the Meta-Beacon to a simple Beacon, besides having aggregation functionalities, we have listed the following additional properties: diff --git a/docs/adminGuide/beacon-registry.md b/docs/adminGuide/beacon-registry.md index 984d2de..35f2cb6 100644 --- a/docs/adminGuide/beacon-registry.md +++ b/docs/adminGuide/beacon-registry.md @@ -32,6 +32,8 @@ The cache of the registry store the following information about the Beacons: - Authentication/Authorization mechanism needed to ensure that only authorized users access the data. +- Basic metadata from the `info` endpoint. + As it can be seen, the data stored in the cache is directly related with the queries policy. So, it needs to be updated every time there is a change in any Beacon. ## Update Registry diff --git a/docs/adminGuide/best-practices.md b/docs/adminGuide/best-practices.md index 19b0866..120673c 100644 --- a/docs/adminGuide/best-practices.md +++ b/docs/adminGuide/best-practices.md @@ -20,11 +20,11 @@ nav_order: 4 ## Adding your own filters -You decide which filtering terms a Beacon Network (BN) can query. You can avoid all the filtering terms your beacons, and only use the ones from the static ontologies of the Aggregator. +As an ELIXIR Beacon Network (EBN) maintainer, along its steering commitee, you decide which filtering terms a Beacon Network (BN) can query. You can avoid all the filtering terms of the beacons in the network, and only use the ones from the static ontologies of the Aggregator. ## User certificates -To ensure the privacy and anonymity of the data, a BN should keep track of the queries done by the users. As an example, a user can make multiple queries to retrieve all the genomic data of a patient. This can potentially compromise the privacy of the patient and confidentiality of the data. +To ensure the privacy and anonymity of the data, a BN should keep track of the metadata of the queries done by the users. As an example, a user can make multiple queries to retrieve all the genomic data of a patient. This can potentially compromise the privacy of the patient and confidentiality of the data. To address the issue, Beacon Networks can use User Certificates to know who makes queries to the Beacons. By monitoring their activity we can prevent users from accessing too much data at once and identify suspicious activities. A possible solution is to limit the number of queries per user in a day or to stop giving access to a user when the queries are mistrustful. @@ -36,19 +36,19 @@ Here there are issues that we have found in different Beacons when importing the ### Query per second -When the network fetches the Beacons, first it needs to query the metadata in order to parse and put it in the cache. These queries are done in consequential order. If one of your Beacons API has limited the queries per second, this would cause trouble to the Network as it won’t let it search for all the needed metadata. +When the EBN fetches the Beacons, first it needs to query the metadata in order to parse and put it in the cache. These queries are done in consequential order. If one of your Beacons API has limited the queries per second, this would cause trouble to the Network as it won’t let it search for all the needed metadata. ### Correct paths -The most common mistake when inserting a beacon to the network is having wrong URL paths in the `/map` endpoint. You must check that all the URLs work properly. +The most common mistake when inserting a beacon to the network is having wrong URL paths in the `/map` endpoint. If you are a Beacon maintainer, you must check that all the URLs work properly. -The Beacon Network need to check all the paths in order to query them or retrieve the correct specification. If the path returns any value, the beacon will not be queried. +The ELIXIR Beacon Network need to check all the paths in order to query them or retrieve the correct specification. If the path returns any value, the beacon will not be queried. ### Beacon ID and general information The Beacon ID of the beacon must be unique. If not, the Beacon Network won't be able to process the responses. -If you deploy your beacon based on another instance or Reference Implementation, you should change the general information of the given beacon with the name of your organisation, project, and other info. +If you deploy your beacon based on another instance or [Reference Implementation](https://github.com/EGA-archive/beacon2-ri-api), you should change the general information of the given beacon with the name of your organisation, project, and other info. ### Filtering terms diff --git a/docs/adminGuide/light-beacon-network.md b/docs/adminGuide/light-beacon-network.md index 375728b..ca0d1c5 100644 --- a/docs/adminGuide/light-beacon-network.md +++ b/docs/adminGuide/light-beacon-network.md @@ -22,9 +22,9 @@ When multiple institutions or organizations deploy a Beacon and make it accessib If you want to deploy the ELIXIR Beacon v2 Network instance made by the [BSC](https://www.bsc.es/discover-bsc/organisation/scientific-structure/national-institute-bioinformatics-elixir-node-0) (Backend) and [EGA-CRG](https://www.crg.eu/en/programmes-groups/ega-team) (Frontend), follow the next steps. -## Full Docker install (Backend & Frontend) +## Full Docker install (Recommended) -Download the code from this [repository](https://github.com/elixir-europe/beacon-network-docker.git), +Download the code from this [repository](https://github.com/elixir-europe/beacon-network-docker.git): ``` git clone https://github.com/elixir-europe/beacon-network-docker.git @@ -48,7 +48,7 @@ Run [docker compose](https://docs.docker.com/compose/) to build and start the co docker compose up -d ``` -Congrats! You have created Beacon Network FrontEnd in [http://localhost:8080/](http://localhost:8080/) and the backend in [http://localhost:8080/beacon-network/v2.0.0/](http://localhost:8080/beacon-network/v2.0.0/). Adjust the URLs based on your setup. +Congrats! You have succesfully deployed ELIXIR Beacon Network FrontEnd in [http://localhost:8080/](http://localhost:8080/) and the backend in [http://localhost:8080/beacon-network/v2.0.0/](http://localhost:8080/beacon-network/v2.0.0/). Adjust the URLs based on your setup. ## Backend Installation @@ -61,7 +61,7 @@ cd beacon-network-backend/docker docker compose up -d ``` -Congrats! You have created Beacon Network in [http://localhost:8080/beacon-network/v2.0.0/](http://localhost:8080/beacon-network/v2.0.0/). You can now view and query the backend as needed. Adjust the URLs as necessary based on your setup. +Congrats! You have deployed the ELIXIR Beacon Network backend in [http://localhost:8080/beacon-network/v2.0.0/](http://localhost:8080/beacon-network/v2.0.0/). You can now view and query the backend with API GET/POST queries. Adjust the URLs as necessary based on your setup. ## FrontEnd Installation @@ -85,7 +85,7 @@ Run [docker compose](https://docs.docker.com/compose/): docker-compose up -d –build ``` -Edit `config.json` from [frontend/src](frontend/src) to point the URLa where you are making the queries. Example: +Edit `config.json` from [frontend/src](frontend/src) to point the URLs where you have the backend, main webpage and keycloak. Example: ``` { @@ -93,7 +93,6 @@ Edit `config.json` from [frontend/src](frontend/src) to point the URLa where you "REDIRECT_URL": "https://yourUIdomain.com", "KEYCLOAK_URL": "https://yourKEYCLOAKdomain.com" } - ``` You have deployed the Beacon Network Frontend in [http://localhost:3000](http://localhost:3000). Adjust the URLs as needed based on your setup. @@ -101,12 +100,17 @@ You have deployed the Beacon Network Frontend in [http://localhost:3000](http:// # Update the EBN To update the ELIXIR Beacon Network (EBN) with a new image, follow these steps: -Pull the latest image: + +- Pull the latest image: + ``` docker-compose pull ``` -Recreate and rebuild the containers with the new image: + +- Recreate and rebuild the containers with the new image: + ``` docker-compose up --force-recreate --build -d ``` + These commands will download the latest image for the EBN and recreate the containers using the new image. The `--force-recreate` flag ensures that the containers are recreated even if they are already running, and the `--build` flag rebuilds the containers if necessary. The `-d flag runs the containers in detached mode. diff --git a/docs/mainDocumentation/documentation.md b/docs/mainDocumentation/documentation.md index a6acdab..8193eea 100644 --- a/docs/mainDocumentation/documentation.md +++ b/docs/mainDocumentation/documentation.md @@ -9,4 +9,4 @@ nav_order: 2 # Documentation -Main documentation for organizational procedures inside the ELIXIR Beacon Network. These documentation has been developed thanks to the 2022 ELIXIR Beacon Infrastructure Service plan and they are a living documentation that will be updated along with new implementations or changes in the main development. \ No newline at end of file +Main documentation for organizational procedures inside the ELIXIR Beacon Network. These documentation has been developed thanks to the 2022 ELIXIR Beacon Infrastructure Service plan. They are a living documentation that will be updated along with new implementations or changes in the main development. \ No newline at end of file diff --git a/docs/mainDocumentation/expectedOperations.md b/docs/mainDocumentation/expectedOperations.md index 01c06e7..0964ea3 100644 --- a/docs/mainDocumentation/expectedOperations.md +++ b/docs/mainDocumentation/expectedOperations.md @@ -29,7 +29,6 @@ The ELIXIR Beacon Network (EBN) holds primary responsibility for querying all be User queries must conform to the schema of the beacons to generate potentially positive results. If a query deviates from the version of the Beacon protocol supported by the aggregator a specific beacon's schema, the beacon will respond negatively. This protocol ensures that users receive accurate and relevant information consistent with the capabilities of each beacon within the network. - ## Add Beacons To include a Beacon in the ELIXIR Beacon Network (EBN), it must first receive acceptance from the ELIXIR Beacon Network Maintainer. @@ -48,7 +47,6 @@ In addition to meeting the Steering Committee's criteria, the following minimum 5. Data: While it is not obligatory for a Beacon to contain data upon integration into the network, it is recommended to utilise synthetic data if authentic data is unavailable. - ## Remove Beacons The individual responsible for removing beacons from the network is the EBN Maintainer. The removal process is initiated under the following circumstances: @@ -61,12 +59,10 @@ The individual responsible for removing beacons from the network is the EBN Main 4. A beacon significantly compromises the network's performance or security. - ## Validate a Beacon Before integration into the ELIXIR Beacon Network (EBN), a beacon must undergo validation. If the validation process concludes without errors, the beacon is deemed suitable for inclusion in the network. However, if errors are detected during validation, and they do not pose significant risks to querying the beacon or to the EBN itself, the decision to integrate the beacon rests with the EBN Maintainer. - ## Load-Balance The Load-Balance server must be hosted at a minimum of two distinct institutions, as designated by the Steering Committee, each of which must possess adequate funding for EBN maintenance. @@ -77,36 +73,30 @@ All institutions implementing the Load-Balance approach within the ELIXIR Beacon The Load-Balance approach is not mandatory. It is up to the SC to decide if it is suitable to use it or use another approach, such as having the EBN in the cloud. - ## Registration/Authorization Users are required to include the appropriate token with each query, whether utilising the direct API or the FrontEnd interface. This token functions as both authentication and authorization, providing the necessary level of access to query the beacons within the ELIXIR Beacon Network with the desired granularity. - ## Product updates and maintenance Any modification to the ELIXIR Beacon Network requires validation by at least two members of the Steering Committee and two members of the Operations Team. Users of the EBN have the ability to create their own branches or forks. However, any additions, removals, or updates to the main or development code must be submitted as pull requests to the main/dev branch of the repository. To initiate a new version of the ELIXIR Beacon Network, approval from all SC members is necessary. Subsequently, an email must be circulated to all participating EBNs in the Load-Balance approach to coordinate the timing of their deployment updates. Finally, an email must be sent to all participants via the EBN mailing list. - ## Monitoring It is up to the Steering Committee to decide which statistics and how to monitor the EBN. The EBN maintainer is the one responsible to be in contact with the Operations Team for deploying the monitorisation, and report it to the Steering Committee (it must be done at least once a year). Also, they are responsible to contact the Disaster Recovery Coordinator when an incident has been detected. - ## Documentation and training Documentation and training for the EBN are continuously evolving to meet the needs of its users. Any user of the EBN has the opportunity to contribute to the documentation. However, any proposed additions, removals, or updates to the documentation must receive approval from at least two members of the Steering Committee or the Operations Team. Training programs may be conducted by any interested individual. Prior to conducting training, notification and relevant information must be provided to the Steering Committee for assistance and coordination. Additionally, the ELIXIR Training program, accessible via TeSS, can offer valuable resources and support for training initiatives. - # What makes a Beacon operational in the ELIXIR Beacon Network This section outlines the standards and expectations for maintaining an Operational Beacons within the ELIXIR Beacon Network v2. It aims to ensure a consistent and high-quality user experience, facilitate interoperability, and uphold the network's overall reliability and integrity. This **section is aimed at Beacon owners** with a Beacon inside the network. - ## Operational Requirements - Compliance: Beacons must comply with the ELIXIR Beacon Network v2 specifications and standards. @@ -115,14 +105,12 @@ This section outlines the standards and expectations for maintaining an Operatio - Data Quality: Beacons must ensure the accuracy, completeness, and timeliness of the genomic data they host. - ## Performance Metrics - Response Time: Beacons must respond to queries within 30 seconds under normal operating conditions. - Throughput: Beacons must handle a minimum of 100 concurrent queries without performance degradation. - ## Service Availability - Uptime: Beacons must maintain a minimum uptime of 99.5% on a monthly basis. @@ -131,7 +119,6 @@ This section outlines the standards and expectations for maintaining an Operatio - Unscheduled Downtime: In the event of unscheduled downtime, Beacon operators must notify the ELIXIR Beacon Network Management within 30 minutes of the incident. - ## Incident Management - Incident Reporting: Beacon operators must report any incidents affecting service availability or performance to the ELIXIR Beacon Network Management immediately. @@ -140,16 +127,14 @@ This section outlines the standards and expectations for maintaining an Operatio - Escalation: If an incident cannot be resolved within the stipulated time, it must be escalated to the ELIXIR Beacon Network Management for further assistance. - ## Support and Maintenance - Support Availability: Beacon maintainers must provide support for their Beacons during regular business hours. - Maintenance Practices: Beacon maintainers must perform regular maintenance to ensure optimal performance and compliance with security standards. This includes applying software updates, patching vulnerabilities, and monitoring system health. - ## Responsibilities -- Beacon Maintainers: Ensure compliance with all operational requirements and performance metrics outlined in this SLA. Maintain the accuracy and quality of the data hosted by the Beacon. Provide timely support and incident resolution as specified. +- Beacon Maintainers: Ensure compliance with all operational requirements and performance metrics outlined in this section. Maintain the accuracy and quality of the data hosted by the Beacon. Provide timely support and incident resolution as specified. -- ELIXIR Beacon Network Maintainer: Monitor the performance and availability of Beacons within the network. Provide guidance and support to Beacon operators to help them meet SLA commitments. Coordinate network-wide maintenance and updates to ensure interoperability and performance. Review incident reports and facilitate root cause analysis and resolution. +- ELIXIR Beacon Network Maintainer: Monitor the performance and availability of Beacons within the network. Provide guidance and support to Beacon operators to help them meet the requirements. Coordinate network-wide maintenance and updates to ensure interoperability and performance. Review incident reports and facilitate root cause analysis and resolution. \ No newline at end of file diff --git a/docs/mainDocumentation/governanceModel.md b/docs/mainDocumentation/governanceModel.md index f80d28d..6920f9f 100644 --- a/docs/mainDocumentation/governanceModel.md +++ b/docs/mainDocumentation/governanceModel.md @@ -36,7 +36,6 @@ The main objectives of the ELIXIR Beacon Network are: - Knowledge exchange: Bringing different data providers together serves to identify commonalities and differences across sites, facilitating expert knowledge exchange and the promotion and adoption of standardised protocols across the community. - ## Structure The governance structure is designed to facilitate transparent decision-making, both strategic and operational, and community involvement. The key parts are: @@ -47,29 +46,24 @@ The governance structure is designed to facilitate transparent decision-making, - Appendixes that describe details on particular aspects. -The considerations for expected operations, such as relevant and contextual considerations for the governance in the different operations inside the EBN and what makes a Beacon operational in the network are in the [ELIXIR Beacon Network Operations document](https://docs.google.com/document/d/1GfCztXyPIN3m0dY-1RGZQac0EUqzFCACnAdnq4XrgDQ/edit). - +The considerations for expected operations, such as relevant and contextual considerations for the governance in the different operations inside the EBN and what makes a Beacon operational in the network are in the [Expected Operations document]({{ site.baseurl }}/docs/mainDocumentation/expectedOperations). # 3. Roles, Bodies and Responsibilities This section lists roles, bodies and responsibilities in the ELIXIR Beacon Network: - ## Users User is anyone querying EBN. As an example, a user can be a researcher searching for individuals with a certain disease across multiple beacons. Users could be anonymous or registered. - ### Anonymous Users Anonymous users refer to individuals who are not registered or do not pass any authentication in the ELIXIR Beacon Network. Such users are limited to accessing only the public beacons, with access restricted to the default level of granularity of each beacon. - ### Registered Users Registered users are those who have logged into EBN. Whenever these users initiate a query, EBN will transmit their identity to the beacons within the network. - ## Beacon Maintainer Beacon maintainers are the people in charge of the beacons that have been included in the network, or want to be in the network. They are responsible for overseeing the operations and functionalities of their respective beacons. @@ -78,7 +72,6 @@ They are the primary point of contact with the EBN Maintainer, facilitating the Before asking permission to enter the ELIXIR Beacon Network, they must pass their beacon to the [validator](https://github.com/elixir-europe/neat-beacon-v2-validator) to ensure their beacon is complying with the specification. - ## ELIXIR Beacon Network Maintainer Responsible for the operations of the ELIXIR Beacon Network instance or instances. They control the actual addition or updating of beacons within the network. Also, they serve as the primary operational point of contact for beacon owners and are responsible for notifying them of any issues, such as beacon downtime or errors. @@ -89,14 +82,12 @@ This role could be split into several individuals or subroles, e.g.: customer su The EBN Maintainer is selected by the Steering Committee. It must be a person with access to the system where the EBN backend is located. - ## Contributors Contributors are community members who help maintain and develop the ELIXIR Beacon Network. Any person can contribute. Participation is open to anyone, with no expectation of long-term commitment, specific skill requirements, or selection process. Contributions can take multiple forms such as reporting bugs, writing documentation, contributing code (e.g. new model schemas). Any form of contribution is welcome, and it will be recognized. - ## Steering CommitteeBeacon Maintainer at least one member from the contributing communities. The members are typically nominated and elected by the existing committee (Derived from the Service Founding Committee at M1.1) or through a vote by the contributing community members. The selection criteria prioritise diversity in expertise and community representation, with a balance between technical and project perspectives. @@ -111,21 +102,20 @@ The Steering Committee holds regular mandatory meetings, typically on a quarterl 4. Policy Development and Updates: Discussing and approving new policies or modifications to existing ones. - ## Operations Team Specialists responsible for the technical infrastructure and development of the network. Their primary focus is on developing the network, implementing extensions and ensuring interoperability to enhance its functionality and efficiency. This committee is composed by contributors of the ELIXIR Beacon Network. It is also encouraged that the members of contributing communities help the development together with the Steering Committee. -Disaster Recovery team +## Disaster Recovery team +People in charge on recovering the ELIXIR Beacon Network in case of a disruptive event that impact the network functionalities. It must be composed by technical people and the EBN maintainer maintainer. ## Training and outreach Anyone related to the EBN can do training or participate in outreach activities. Before doing so, they must send a mail to to inform them of the activity, and get any possible help from the community or any other valuable assistance. - ## SC Chair The SC Chair is a single individual, a member of the Steering Committee, and elected for a 2-year non-renewable term by the SC, with the expectation that this role should rotate between its members. The Chair has no additional authority over other members of the Steering Committee: the role is one of coordinator. The Chair is also expected to ensure that all governance processes are adhered to, and has the casting vote when the project fails to reach consensus. diff --git a/index.md b/index.md index a1e015e..3f5cf75 100644 --- a/index.md +++ b/index.md @@ -9,7 +9,7 @@ Welcome to the ELIXIR Beacon v2 Network documentation! After the approval of Beacon v2 as an official GA4GH standard and the success of the ELIXIR Beacon v1 Network, there was a need of create a new implementation of the ELIXIR Beacon Network adding the functionalities of the new version. -With this new version, the Beacon Network is able to query genomic and pheno-clinical data of the patients across the many instances of the network. +With this new version, the ELIXIR Beacon Network is able to query genomic and pheno-clinical data of the patients across the many instances of the network. The documentation is divided in two parts: