Skip to content

Workflow: Approval of Sample Types

  1. Ask for membership in group Sample Type Lab
  2. Scan the existing sample types or drafts in the group. You can find the drafts and the approved sample types under Configuration -> Sample Types
    • There is one sample type that is similar to the sample type you need? Contact the Labspace Team, or ask in the Labspace Community we connect you with the users or developers of the sample type.
    • There is no sample type like the one you need? Go to step 3
  3. In the group Sample Type Lab create a new experiment and sample type:
    • Go to Journal -> Experiment Browser
    • Press Add Experiment
    • Choose Experiment from template
    • Choose template New sample type
    • Set the name to your desired sample type and press create
    • Set the status, add collaborators and fill the sections as needed
    • Go to Configuration -> Sample Types and press Add Sample type and choose Add a custom sample type
    • Please do not use an existing sample type for customizing! Especially not if it says "Approved" in the description.
    • Put - DRAFT - in the description
    • Now you can start configuring your sample type!
    • If you have questions you can consult the product documentation write an email to labspace@ufz.de or ask in the Labspace Community
    • Once you have a version that you want to discuss or have approved, add a task to the experiment and assign it to one of the administrators.

If you are interested in developing a controlled vocabulary for a persistent identifier (PID) for your samples, please contact our colleague Johann Wurz who is in charge for this topic in the HMC. Together, we will support you on your way there.

Permissions to see all experiments

To see all existing experiments, you have to change the filter in the top of the experiment browser to All users. The permissions in the group Sample Type Lab are configured so that everyone can see and edit every experiment.

FAQs

Why are we so strict when it comes to developing and customizing sample types?

Being strict about sample types is essential to ensure consistency, interoperability, and long-term usability of sample data.

As our goal is to move toward controlled vocabularies for IGSN as a persistent identifier (PID) for samples, having clearly defined and standardised sample types becomes important. If we use different or loosely defined sample types, samples cannot be reliably shared or exchanged.

In practical terms:

  • Samples can only be exchanged between groups if their sample types match. Inconsistent or customised types break sample and data exchange.
  • Controlled vocabularies require precise, standardised sample descriptions which is important if we speak about PIDs
  • Standardised sample types improve searchability, reporting, automation, and reuse of samples and data.

While customisation can feel convenient in the short term, it creates fragmentation that limits sharing and scalability. Being strict upfront ensures samples remain portable, interoperable, and valuable over their full lifecycle.

Why do we need to create an experiment in the group in order to create a new sample type?

The experiment in this group is kind of a version control during the process of customizing your sample type. Also it is a place for enhancing discussion and collaboration. Feel free to use it so it fits your needs! Be aware that there is no automation so you have to document your changes yourself.