- Introduction to the ERDERA GitHub Structure and Governance
- Governance of Repository Creation
- ERDERA GitHub Layers
- Navigating and using the ERDERA GitHub
- How to Engage
- 👥 GitHub Coordinators
- Repositories details coordination
- Private GitHub Repositories
- Public GitHub Repositories
The ERDERA GitHub organization serves as the backbone for coordinating the digital resources and collaborative efforts of the ERDERA project. Designed to streamline the development, dissemination, and governance of various work packages and deliverables, the GitHub structure integrates multiple repositories and teams tailored to address specific tasks and objectives within the project.
At the core of this structure is the central coordination repository, which acts as the hub for managing the GitHub organization. It ensures collaboration by standardizing processes such as requesting new repositories, forming teams, and managing access rights. The repository also facilitates cloning and adapting resources from the prior EJP RD project, thus ensuring continuity and leveraging past work.
The ERDERA GitHub organization operates under a distributed governance structure, which ensures that responsibilities for repository creation are shared among central coordination, work package leaders (WPL), and task leaders. This decentralized approach facilitates efficient collaboration and ensures that repositories are created in alignment with project needs and objectives.
Roles and Responsibilities for Repository Creation :
Role |
Responsibilities |
|---|---|
| Central Coordination Team | - Oversee structure: Manages the overall organization of the ERDERA GitHub. - Set guidelines: Maintains repository naming conventions, access control, and usage policies. - Support repository creation: Facilitates repositories for cross-cutting tasks or central infrastructure needs. - Handle special requests: Manages cloning of repositories from the EJP RD project. |
| Work Package Leaders (WPL) | - Create repositories: Authorized to establish repositories for their work packages. - Ensure alignment: Guarantees that repositories meet deliverables and objectives. - Manage access: Controls permissions for their work package team. |
| Task Leaders | - Issue task-specific repositories: Can create repositories tailored to their task needs. - Define scope and structure: Ensures repositories are appropriately focused. - Coordinate practices: Works with WPLs and central coordination for consistency. |
The ERDERA infrastructure is organized into three primary layers to provide clarity and functional separation:
Layer |
Purpose |
Key Functions |
|---|---|---|
| Layer 1: SharePoint | Collaboration & Documentation | - Centralized document management. - File sharing and storage for project materials. |
| Layer 2: GitHub | Heart of Technical Coordination | - Core development platform. - Hosts private, public, and semantic artifacts repositories. - Supports SPARQL examples, semantic models, and other essential resources. |
| Layer 3: Zenodo | Archiving & FAIR Compliance | - Ensures long-term availability and accessibility of project deliverables. - Aligns with FAIR principles (Findable, Accessible, Interoperable, and Reusable). |
A github team is a group of people that have access to a set of repositories. The teams are used to manage the access to the repositories.
The following teams are currently available in the ERDERA github organization: Teams
A project is a task management tool within a repository that helps organize and track progress toward goals.
The following Projects are currently available ERDERA github organization: Projects
A repository is a storage space for code, resources, or documentation related to a specific project or task.
The following Repositories are currently available ERDERA github organization: Repositories
graph TD
subgraph ClusterA [Layer 1: SharePoint]
SP[(SharePoint)]
DSW[(Data Steward Wizard)]
end
subgraph ClusterB [Layer 2: GitHub]
direction LR
EGH[(ERDERA GitHub)] --> PrivR[Private Repositories]
EGH --> PubR[Public Repositories]
PubR --> SPARQLEX[ERDERA SPARQL Examples]
PrivR --> CC[Central coordination]
CC --> WPL[Work package leaders]
CC --> AMC[AmsterdamUMC]
CC --> MR[molgenis-rd3]
WPL --> 13.1[Task 13.1]
WPL --> 13.2[Task 13.2]
WPL --> 13.3[Task 13.3]
WPL --> 14.1[Task 14.1]
WPL --> 14.2[Task 14.2]
WPL --> 14.3[Task 14.3]
WPL --> 16.5[Task 16.5]
16.5 --> OP[ontology_parsing]
16.5 --> SPARQLEX
16.5 --> OFCO[OFCO_Mapping]
end
subgraph ClusterC [Layer 3: Zenodo]
EZD[(ERDERA Zenodo)]
end
ClusterA --> |is coordinated through| ClusterB
ClusterB --> |is archived and diseminated on| ClusterC
click OP "https://github.com/ERDERA/ontology_parsing"
click OFCO "https://github.com/ERDERA/OFCO_Mapping"
click SPARQLEX "https://github.com/ERDERA/sparql-examples"
click 16.5 "https://github.com/ERDERA/Task-16.5-coordination"
click 13.3 "https://github.com/ERDERA/Task-13.3"
click 14.1 "https://github.com/ERDERA/Task-14.1-coordination"
click 14.2 "https://github.com/ERDERA/Task-14.2"
click 14.3 "https://github.com/ERDERA/Task-14.3"
click 13.2 "https://github.com/ERDERA/Task-13.2"
click 13.1 "https://github.com/ERDERA/Task-13.1"
click MR "https://github.com/ERDERA/molgenis-rd3"
click AMC "https://github.com/ERDERA/AmsterdamUMC"
%% Legend
subgraph ClusterB [Legend]
direction TB
Repo(Private Repo)
Repo2(Public Repo)
WP(Work package)
end
%% Colors
classDef repo2 fill:#efab5d
classDef repo fill:#a0d2ed
classDef wp fill:#9fecbf
class 16.5,OP,OFCO,13.3,14.1,14.2,14.3,13.2,13.1,Repo,MR,AMC repo;
class Repo2,SPARQLEX repo2;
class WPL,WP wp;
To promote transparency and collaboration, ERDERA provides simple mechanisms for partners to request new resources or include existing repositories from EJP-RD and other related projects:
- New Team Requests: Facilitates the formation of teams with clearly defined access permissions.
- New Repository Requests: Allows contributors to propose new repositories for specific tasks or deliverables.
- Repository Cloning: Enables the reuse of resources from the EJP RD project to build on prior work.
By leveraging these mechanisms, partners can efficiently create, manage, and access the digital resources needed to drive the ERDERA project forward. The ERDERA GitHub organization is designed to support the collaborative efforts of the project partners and ensure the successful development and dissemination of project deliverables.
- Request a new team
- Request a new repository
- Request a clone of a repository from the previous EJP RD project
The following people are the coordinators for this Github repository:
- Andra Waagmeester (AmsterdamUMC)
- Luiz Olavo Bonino da Silva Santos (UTwente)
- Mark Hanauer (Orphanet)
- Heena Lad
- Ronald Cornet (AmsterdamUMC)
- Andra Waagmeester (AmsterdamUMC)
- Luiz Olavo Bonino da Silva Santos (UTwente)
- Mark Hanauer (Orphanet)
- Heena Lad
- Ronald Cornet (AmsterdamUMC)
#Todo: Add the work package leaders
Availability: private
Availability: public
Availability: public
Availability: public
SPARQL examples is intended to be a collection of SPARQL examples for various ERDERA projects. This repository is a fork of the SIB-Swiss sparql-examples repository and follows the same structure and guidelines. The repository is used to store SPARQL queries in a structured way, with each query stored in a separate file. The queries are stored in the examples folder, with each project having its own subfolder. The repository also contains a README file with information about the project and how to contribute to it.