Add pages needed for new profile labprocess

pages/_groups/LabProtocols.md

@@ -4,22 +4,36 @@ identifier: labprotocols
 name: Laboratory Protocols
 collection: groups
 active: true
-type: biological
-description: Specification for biological laboratory protocol Type
-lead: 
+type: generic
+description: Specification of protocols and processes as used in a lab.
+lead:
+- person: SebastianBeier
+  start-date: 2023-12-11
+- person: FlorianWetzels
+  start-date: 2023-12-11
+- person: LeylaGarcia
+  start-date: 2023-12-11  
+former-lead:
 - person: OlgaXimenaGiraldo
+  start-date: 2020-10-01
+  end-date: 2023-12-10
 - person: AlexanderGarcia
+  start-date: 2020-10-01
+  end-date: 2023-12-10
 email: [email protected]
 issues: https://github.com/Bioschemas/bioschemas/labels/type%3A%20LabProtocol
 folder: https://drive.google.com/drive/folders/0B0fE3oOZIq44TzFwejFEbE9WdXM
 
 # Page attributes
-abstract: 'In schema.org we cannot find life science types (eg. protein, gene, biological pathway) except those types that overlap with healthcare and medicine domains defined by the health schema.org extension (eg. drug, artery). These life science types share many elements which can be captured in a common biological entity type.'
+abstract: 'The LabProtocols group aims at providing specifications related to studies, for instance protocol and process, as used in a lab, whether wet- or dry-lab. While specifications at the generic level are the initial target, specializations to better cover wet- or dry-lab are also within the scope of this group (either with sub-types or profiles). It is loosely based on the Investigation/Study/Assay (ISA) model.'
+
 objectives:
-  [
-    'Describe biological laboratory protocols using Bioschemas compliant markup so protocols can be more easily indexed by search engines and registries.',
-    'Evaluating the issues and benefits about how to work with laboratory protocols in schema.org and Bioschemas'
-  ]
+[
+  'Describe lab protocols and processes using Bioschemas compliant markup so they can be more easily indexed by search engines and registries.',
+  'Evaluating the issues and benefits about how to work with laboratory protocols and processes in schema.org and Bioschemas',
+  'Establish a distinct separation between LabProtocol (akin to a Recipe / SOP) and LabProcess (akin to the Action described by such LabProtocol, analogous to a lab notebook in a real-world scenario)',
+  '(wet-lab protocol) Describe biological laboratory protocols using Bioschemas compliant markup so protocols can be more easily indexed by search engines and registries.',
+]
 
 specifications:
   [
@@ -32,15 +46,26 @@ types:
     ]
 
 members:
-    - FedericoLópezGómez
-    - LeylaGarcia
+    - OlgaXimenaGiraldo
+    - GwenMoncoiffe
+    - BarbaraMagagna
+    - TimoMuehlhaus
+    - StuartOwen
+    - DominikBrilhaus
+    - LukasWeil
+    - CyrilPommier
+    - GajendraDoniparthi
+    - DanielArend
+    - ManuelFeser
+
+former-members:
+    - FedericoLopezGomez
     - GianluigiZanetti
     - AndraWaagmeester
     - HeimoMüller
     - MorrisSwertz
     - KaisaSilander
     - PetrHolub
     - DavidvanEnckevort
-    - GwenMoncoiffe
-    - BarbaraMagagna
+    - AlexanderGarcia
 ---

pages/_people/DanielArend.md

@@ -0,0 +1,11 @@
+---
+layout: person-details
+id: DanielArend
+first-name: Daniel
+last-name: Arend
+collection: people
+affiliation:
+homepage:
+github_username: 
+orcid: 
+---

pages/_people/DominikBrilhaus.md

@@ -0,0 +1,11 @@
+---
+layout: person-details
+id: DominikBrilhaus
+first-name: Dominik
+last-name: Brilhaus
+collection: people
+affiliation:
+homepage:
+github_username: 
+orcid: 
+---

pages/_people/FlorianWetzels.md

@@ -0,0 +1,11 @@
+---
+layout: person-details
+id: FlorianWetzels
+first-name: Florian
+last-name: Wetzels
+collection: people
+affiliation:
+homepage:
+github_username: 
+orcid: 
+---

pages/_people/GajendraDoniparthi.md

@@ -0,0 +1,11 @@
+---
+layout: person-details
+id: GajendraDoniparthi
+first-name: Gajendra
+last-name: Doniparthi
+collection: people
+affiliation:
+homepage:
+github_username: 
+orcid: 
+---

pages/_people/LukasWeil.md

@@ -0,0 +1,11 @@
+---
+layout: person-details
+id: LukasWeil
+first-name: Lukas
+last-name: Weil
+collection: people
+affiliation:
+homepage:
+github_username: 
+orcid: 
+---

pages/_people/ManuelFeser.md

@@ -0,0 +1,11 @@
+---
+layout: person-details
+id: ManuelFeser
+first-name: Manuel
+last-name: Feser
+collection: people
+affiliation:
+homepage:
+github_username: 
+orcid: 
+---

pages/_people/SebastianBeier.md

@@ -0,0 +1,11 @@
+---
+layout: person-details
+id: SebastianBeier
+first-name: Sebastian
+last-name: Beier
+collection: people
+affiliation:
+homepage:
+github_username: 
+orcid: 
+---

pages/_people/TimoMuehlhaus.md

@@ -0,0 +1,11 @@
+---
+layout: person-details
+id: TimoMuehlhaus
+first-name: Timo
+last-name: Muehlhaus
+collection: people
+affiliation:
+homepage:
+github_username: 
+orcid: 
+---

pages/_useCases/LabProcess.md

@@ -0,0 +1,59 @@
+---
+layout: use-case
+name: Laboratory Processes
+group: labprotocols
+active: true
+redirect_from: 
+- "/useCases/LabProcesses/"
+- "/useCases/LabProcesses"
+- "/useCases/LabProcess/"
+- "/useCases/LabProcess"
+---
+
+### Findability
+
+#### Findability for comparative analysis
+A user is seeking experimental data for the purpose of conducting a comparative
+analysis. Their primary interest lies in identifying and comparing experiments with
+specific factors. In individual experiments, these factors are not the primary focus of
+the studies; instead, they serve as fixed parameters within the experimental
+processes. These seemingly "uninteresting" parameters need to be easily accessible
+for their research. The user aims to search for various parameters, factors, and
+characteristics within the specific context of different parts of the experimental setup.
+For example, consider an experiment comprising two distinct processes: one for
+growth and another for measurement under heat stress, both involving the
+parameter "temperature." However, for their comparative analysis, they are
+interested in a specific instance of this parameter, and they need the capability to
+search for it. Consequently, this parameter must be structured and accessible within
+the schema markup of the original experiment. In the event that all this information is
+associated with a dataset object, manual creation of the markup becomes
+necessary, as it demands a semantic understanding of formal parameters. The ISA's
+straightforward process graph model excels in capturing these nuances. Therefore,
+we recommend integrating the LabProcess object type into Bioschemas, as this will
+facilitate the structured markup of the formal parameters associated with experiment
+steps.
+
+#### Findability for fine-grained data acquisition
+Improve the findability for datasets providing (raw) files which can be used for
+bioinformaticians to get data that was created using a dedicated facility or
+instrument. Imagine a bioinformatician developing a new image analysis algorithm to
+calculate plant growth based on drone images. Now he wants to improve the
+underlying calculation and need more drone images which have a minimal resolution
+or were generated with a certain camera sensor, he is not interested in the original
+experimental design, just looking for data based on any equipment.
+
+#### Findability for Input-based dataset search
+In a plant phenomic dataset that includes both direct measures and computed data
+elaborated to characterize the plant varieties, the LabProcess type will allow to
+document the relationship between datafiles. Hence, a user, through a search
+engine, would be able to identify reproducible datasets that include both raw and
+derived data. Also, a search engine would be able to point to raw data that have
+been used to extract specific traits. For instance, a raw images dataset from which a
+trait disease dataset has been derived could be easily found thanks to LabProcess,
+hence identifying potential training dataset for challenges such as the global wheat
+challenge.
+
+### Overview
+Overview of LabProcess and how it relates to other specifications in Bioschemas, for instance LabProtcol and Sample.
+
+![Overview](/images/labProcessOverview.png)