From fd0408622fdd50d1cf6af3ebfabf83e9f5764a26 Mon Sep 17 00:00:00 2001
From: Martin Cook <martin.cook@elixir-europe.org>
Date: Fri, 26 Jul 2024 12:18:53 +0100
Subject: [PATCH] Create cancer_data_management.md

---
 pages/your_domain/cancer_data_management.md | 43 +++++++++++++++++++++
 1 file changed, 43 insertions(+)
 create mode 100644 pages/your_domain/cancer_data_management.md

diff --git a/pages/your_domain/cancer_data_management.md b/pages/your_domain/cancer_data_management.md
new file mode 100644
index 000000000..d576a8cf8
--- /dev/null
+++ b/pages/your_domain/cancer_data_management.md
@@ -0,0 +1,43 @@
+---
+title: Cancer Data Management
+description: <!---REPLACE THIS with a one sentence description of the page--->
+contributors: [<!---REPLACE THIS with comma separated list of contributors--->]
+page_id: <!---REPLACE THIS with a shortened page name. The shortened page name should be in lowercase and separated by underscore(s) if needed. For example, page_id of structural bioinformatics will be struct_bioinfo
+related_pages: 
+  your_tasks: [<!---REPLACE THIS with the page ID of the your_tasks pages that you want to list here as related pages--->]
+  tool_assembly: [<!---REPLACE THIS with the page ID of the tool_assembly pages that you want to list here as related pages--->]
+# More information on which page id you can use can be found at https://rdmkit.elixir-europe.org/website_overview
+training:
+  - name:
+    registry:
+    url:
+# More information on how to fill in this metadata section can be found here https://rdmkit.elixir-europe.org/page_metadata
+---
+
+<!-- Please take in mind our style guide https://rdmkit.elixir-europe.org/style_guide when writing the content of this page. -->
+
+<!--- Domain pages should detail the particular data management challenges of the domain, typically by complementing and extending one or more existing Problem pages.
+In the event that no adequate Problem page exists for a problem that can be generalized across domains, consider first contributing to create one or raising a GitHub issue. However, if a problem is entirely domain specific, then it should be fully detailed within the respective Domain page. --->
+
+## Introduction
+
+<!--- In this section you should provide a brief overview of the domain from the data management perspective, mentioning and putting into context the challenges that are particular to the domain, which will be the object of sections below. --->
+
+
+## section 1 title
+ 
+### Description
+<!--- Sections within Domain pages (aside from "Introduction" at the start and "Tools and resources on this page" at the end) should focus on particular data management problems, which should be described in this first sub-section.
+For problems that are fully domain-specific, a detailed description is merited.
+For detailing the domain-specific challenges of a problem that is generic, please link to the corresponding generic Problem page before going into the domain-specific challenges. --->
+
+### Considerations <!--- (optional) --->
+<!---  Direct and concise considerations, structured in bullet points and typically framed as questions RDMkit reader should ask themselves in order to arrive at the best solution among those listed below. One level of nesting of bullet points within considerations is fine, but more levels should be avoided. --->
+
+
+### Solutions
+<!--- Detail, either in normal text or in bullet points, the domain-specific solutions to the problem. Do not merely list tools or resources, as they will be automatically listed in the bottom section, but you can and should mention tools and resources listed below if you detail their usage to solve the problem. --->
+
+<!--- ## Section 2 Title --->
+<!--- Add more sections as needed, with the same subsections as above. --->
+...