Toggle menu
17
24
14
1.7K
Landrace.Wiki - The Landrace Cannabis Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Template:Accession/FormLanding: Difference between revisions

Template page
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
<templatestyles src="Accession/FormLanding/styles.css" />
<templatestyles src="Accession/FormLanding/styles.css" />
<div class="form-landing">
<div class="form-landing">


<div class="landing-header">
<div class="landing-header">
  <div class="landing-kicker">Accession Intake</div>
<h1>Create New Accession</h1>
  <h1>Create New Accession</h1>
<p>Document landrace cannabis populations for long-term conservation.</p>
  <p>Document landrace cannabis populations for long-term conservation.</p>
</div>
</div>


<div class="warning-box">
<div class="warning-box">
  <h3>⚠️ Read this before creating an accession</h3>
<h3>⚠️ Read this before creating an accession</h3>


  <p><strong>1. Search for existing entries first:</strong></p>
'''1. Search for existing entries first:'''
  <ul>
* Check if this population/field is already documented
    <li>Check if this population/field is already documented</li>
* Use [[Special:Search|Search]] to look for location names, collector names, dates
    <li>Use [[Special:Search|Search]] to look for location names, collector names, dates</li>
* Avoid creating duplicates – it's better to add to an existing entry
    <li>Avoid creating duplicates – it's better to add to an existing entry</li>
  </ul>


  <p><strong>2. Understand what makes a unique accession:</strong></p>
'''2. Understand what makes a unique accession:'''
  <ul>
* Each accession = ONE collection event from ONE specific location on ONE date
    <li>Each accession = ONE collection event from ONE specific location on ONE date</li>
* Same field, different years = different accessions
    <li>Same field, different years = different accessions</li>
* Same year, different fields = different accessions
    <li>Same year, different fields = different accessions</li>
* General population vs specific plant selection = different accessions
    <li>General population vs specific plant selection = different accessions</li>
  </ul>


  <p><strong>3. Know your tier level (handled automatically in the form):</strong></p>
'''3. Know your tier level (handled automatically in the form):'''
  <ul>
* '''Tier 1 (Essential)''': Minimum viable documentation – GPS, date, basic provenance
    <li><strong>Tier 1 (Essential):</strong> Minimum viable documentation – GPS, date, basic provenance</li>
* '''Tier 2 (Enhanced)''': Scientific utility – botanical descriptions, cultural context
    <li><strong>Tier 2 (Enhanced):</strong> Scientific utility – botanical descriptions, cultural context</li>
* '''Tier 3 (Research Grade)''': Publication-ready – lab results, comprehensive preservation
    <li><strong>Tier 3 (Research Grade):</strong> Publication-ready – lab results, comprehensive preservation</li>
  </ul>
</div>
</div>


<div class="content-box">
<div class="content-box">
  <div class="content-header">
<h2>Naming convention (critical)</h2>
    <h2>Naming convention (critical)</h2>
    <p>Good names prevent duplicate accessions and keep the hierarchy usable.</p>
  </div>


  <p class="content-intro">
<p><strong>Use descriptive names that uniquely identify the collection:</strong></p>
    <strong>Use descriptive names that uniquely identify the collection:</strong>
  </p>


  <div class="name-examples">
<div class="name-examples">


    <div class="name-card name-good">
<div class="name-good">
      <div class="name-card-header">
<div class="name-good-header">✅ Recommended</div>
        <span class="name-pill name-pill-good">✅ Recommended</span>
<ul>
        <div class="name-card-title">GOOD NAMES</div>
<li>2023 Atolang General Population</li>
      </div>
<li>2024 Malana Village Selection #3</li>
      <ul>
<li>Kut Bak 2022 November Collection</li>
        <li>2023 Atolang General Population</li>
<li>Parvati Valley Point of Origin 2023</li>
        <li>2024 Malana Village Selection #3</li>
<li>Mae Hong Son Highland Seeds 2024-03</li>
        <li>Kut Bak 2022 November Collection</li>
</ul>
        <li>Parvati Valley Point of Origin 2023</li>
<div class="name-good-why">
        <li>Mae Hong Son Highland Seeds 2024-03</li>
<strong>Why good:</strong> Specific location, year/date, collection type
      </ul>
</div>
      <div class="name-why">
</div>
        <strong>Why good:</strong> Specific location, year/date, collection type
      </div>
    </div>


    <div class="name-card name-bad">
<div class="name-bad">
      <div class="name-card-header">
<div class="name-bad-header">❌ Avoid</div>
        <span class="name-pill name-pill-bad">❌ Avoid</span>
<ul>
        <div class="name-card-title">BAD NAMES</div>
<li>Thai Landrace</li>
      </div>
<li>Indian Strain</li>
      <ul>
<li>Colombian</li>
        <li>Thai Landrace</li>
<li>Himalayan #2</li>
        <li>Indian Strain</li>
<li>Local Variety</li>
        <li>Colombian</li>
</ul>
        <li>Himalayan #2</li>
<div class="name-bad-why">
        <li>Local Variety</li>
<strong>Why bad:</strong> Too generic, no date, no specific location, will cause duplicates
      </ul>
</div>
      <div class="name-why">
</div>
        <strong>Why bad:</strong> Too generic, no date, no specific location, will cause duplicates
      </div>
    </div>


  </div>
</div>


  <div class="formula-box">
<div class="formula-box">
    <div class="formula-label">Naming formula</div>
<div class="formula-label">NAMING FORMULA</div>
    <code>[Year] [Specific Location] [Collection Type/Details]</code>
<code>[Year] [Specific Location] [Collection Type/Details]</code>
    <div class="formula-example">
<p>e.g. 2024 Malana Village General Population</p>
      e.g. <span>2024 Malana Village General Population</span>
</div>
    </div>
  </div>
</div>
</div>


<div class="content-box">
<div class="content-box">
  <div class="content-header">
<h2>Documentation tiers</h2>
    <h2>Documentation tiers</h2>
    <p>All accessions start at Tier 1. Extra fields in the form push them toward Tier 2 and Tier 3.</p>
  </div>


  <div class="tier-grid">
<p>All accessions start at Tier 1. Extra fields in the form push them toward Tier 2 and Tier 3.</p>


    <details open class="tier-box tier-1">
<div class="tier-box tier-1">
      <summary>
<div class="tier-box-header">
        <span class="tier-pill tier-pill-1">Tier 1</span>
<span class="tier-label tier-label-1">TIER 1</span>
        <span class="tier-title">Essential field collection</span>
<span class="tier-title">Essential field collection</span>
        <span class="tier-count">(≈ 46 fields)</span>
<span class="tier-count">(≈ 46 fields)</span>
      </summary>
</div>
      <div class="tier-content">
<p class="tier-subtitle">Required for ANY accession:</p>
        <p><strong>Required for ANY accession:</strong></p>
<ul>
        <ul>
<li>Accession ID (formal identifier)</li>
          <li>Accession ID (formal identifier)</li>
<li>Collection date</li>
          <li>Collection date</li>
<li>GPS coordinates + elevation</li>
          <li>GPS coordinates + elevation</li>
<li>Complete geographic hierarchy (country → province → locality)</li>
          <li>Complete geographic hierarchy (country → province → locality)</li>
<li>Growing region → Appellation → Field</li>
          <li>Growing region → Appellation → Field</li>
<li>Collector name</li>
          <li>Collector name</li>
<li>Collection method (seeds/cuttings/tissue)</li>
          <li>Collection method (seeds/cuttings/tissue)</li>
<li>Sample size</li>
          <li>Sample size</li>
<li>Traditional local name</li>
          <li>Traditional local name</li>
<li>Classification (Landrace/Feral/Other)</li>
          <li>Classification (Landrace/Feral/Other)</li>
<li>Basic conservation assessment</li>
          <li>Basic conservation assessment</li>
<li>Photo evidence (minimum: whole plant + inflorescences + habitat)</li>
          <li>Photo evidence (minimum: whole plant + inflorescences + habitat)</li>
</ul>
        </ul>
<p class="tier-warning">⚠️ If you don't have this minimum data, don't create the accession yet. Gather more information first.</p>
</div>


        <p class="tier-warning">
<div class="tier-box tier-2">
          ⚠️ If you don't have this minimum data, don't create the accession yet. Gather more information first.
<div class="tier-box-header">
        </p>
<span class="tier-label tier-label-2">TIER 2</span>
      </div>
<span class="tier-title">Enhanced scientific documentation</span>
    </details>
<span class="tier-count">(≈ 98 additional fields)</span>
</div>
<p class="tier-subtitle">Adds scientific utility:</p>
<ul>
<li>Detailed botanical descriptions (plant height, leaf shape, flowering traits)</li>
<li>Environmental context (climate, soil, associated flora)</li>
<li>Cultural uses and traditional practices</li>
<li>Cultivation methods and farmer practices</li>
<li>Detailed conservation threat assessments</li>
<li>Extended photographic documentation</li>
</ul>
<p class="tier-note">Complete when: Conducting research, writing reports, building comprehensive databases.</p>
</div>


    <details class="tier-box tier-2">
<div class="tier-box tier-3">
      <summary>
<div class="tier-box-header">
        <span class="tier-pill tier-pill-2">Tier 2</span>
<span class="tier-label tier-label-3">TIER 3</span>
        <span class="tier-title">Enhanced scientific documentation</span>
<span class="tier-title">Research-grade documentation</span>
        <span class="tier-count">(≈ 98 additional fields)</span>
<span class="tier-count">(≈ 83 additional fields)</span>
      </summary>
</div>
      <div class="tier-content">
<p class="tier-subtitle">Publication-ready with lab results:</p>
        <p><strong>Adds scientific utility:</strong></p>
<ul>
        <ul>
<li>Complete cannabinoid profile (THC, CBD, CBG, CBN, CBC, THCV, CBDV)</li>
          <li>Detailed botanical descriptions (plant height, leaf shape, flowering traits)</li>
<li>Complete terpene profile (10+ terpenes)</li>
          <li>Environmental context (climate, soil, associated flora)</li>
<li>Genetic analysis results</li>
          <li>Cultural uses and traditional practices</li>
<li>Laboratory reports and dates</li>
          <li>Cultivation methods and farmer practices</li>
<li>Detailed preservation status (seed banks, tissue culture)</li>
          <li>Detailed conservation threat assessments</li>
<li>Material transfer agreements</li>
          <li>Extended photographic documentation</li>
<li>Literature references and citations</li>
        </ul>
<li>Complete research priorities</li>
</ul>
<p class="tier-note">Complete when: Working with research institutions, publishing papers, or formal conservation programs.</p>
</div>


        <p><strong>Complete when:</strong> Conducting research, writing reports, building comprehensive databases.</p>
</div>
      </div>
    </details>


    <details class="tier-box tier-3">
<div class="content-box">
      <summary>
<h2>Common mistakes to avoid</h2>
        <span class="tier-pill tier-pill-3">Tier 3</span>
        <span class="tier-title">Research-grade documentation</span>
        <span class="tier-count">(≈ 83 additional fields)</span>
      </summary>
      <div class="tier-content">
        <p><strong>Publication-ready with lab results:</strong></p>
        <ul>
          <li>Complete cannabinoid profile (THC, CBD, CBG, CBN, CBC, THCV, CBDV)</li>
          <li>Complete terpene profile (10+ terpenes)</li>
          <li>Genetic analysis results</li>
          <li>Laboratory reports and dates</li>
          <li>Detailed preservation status (seed banks, tissue culture)</li>
          <li>Material transfer agreements</li>
          <li>Literature references and citations</li>
          <li>Complete research priorities</li>
        </ul>


        <p><strong>Complete when:</strong> Working with research institutions, publishing papers, or formal conservation programs.</p>
<div class="mistake-grid">
      </div>
    </details>


  </div>
<div class="mistake-box">
<div class="mistake-title">❌ Creating "placeholder" entries</div>
<div class="mistake-text">Don't create an accession just because you heard about a location. Wait until you have actual samples and data.</div>
</div>
</div>


<div class="content-box">
<div class="mistake-box">
  <div class="content-header">
<div class="mistake-title">❌ Using only generic location names</div>
    <h2>Common mistakes to avoid</h2>
<div class="mistake-text">"Colombian Gold" or "Thai Stick" are not specific enough. You need: specific village/field + year + collector.</div>
    <p>If you catch these before saving, you save yourself clean-up later.</p>
</div>
  </div>


  <div class="mistake-grid">
<div class="mistake-box">
<div class="mistake-title">❌ Mixing multiple collection events</div>
<div class="mistake-text">Each accession = one collection event. If you collected from the same field in 2023 and 2024, create two separate accessions.</div>
</div>


    <div class="mistake-box">
<div class="mistake-box">
      <div class="mistake-title">❌ Creating “placeholder” entries</div>
<div class="mistake-title">❌ Skipping required Tier 1 fields</div>
      <div class="mistake-text">
<div class="mistake-text">If you don't have GPS coordinates, collection date, or collector name, the entry is not valid. Gather this information before creating the accession.</div>
        Don't create an accession just because you heard about a location. Wait until you have actual samples and data.
</div>
      </div>
    </div>


    <div class="mistake-box">
<div class="mistake-box">
      <div class="mistake-title">❌ Using only generic location names</div>
<div class="mistake-title">❌ Creating duplicates instead of searching</div>
      <div class="mistake-text">
<div class="mistake-text">ALWAYS search first. Multiple entries for the same collection creates chaos in the database.</div>
        "Colombian Gold" or "Thai Stick" are not specific enough. You need: specific village/field + year + collector.
</div>
      </div>
    </div>


    <div class="mistake-box">
</div>
      <div class="mistake-title">❌ Mixing multiple collection events</div>
</div>
      <div class="mistake-text">
        Each accession = one collection event. If you collected from the same field in 2023 and 2024, create two separate accessions.
      </div>
    </div>


    <div class="mistake-box">
<div class="content-box">
      <div class="mistake-title">❌ Skipping required Tier 1 fields</div>
<h2>Best practices when filling the form</h2>
      <div class="mistake-text">
        If you don't have GPS coordinates, collection date, or collector name, the entry is not valid. Gather this information before creating the accession.
      </div>
    </div>


    <div class="mistake-box">
<div class="practice-grid">
      <div class="mistake-title">❌ Creating duplicates instead of searching</div>
      <div class="mistake-text">
        ALWAYS search first. Multiple entries for the same collection creates chaos in the database.
      </div>
    </div>


  </div>
<div class="practice-box">
<div class="practice-title">✅ Fill out what you know, skip what you don't.</div>
<div class="practice-text">Don't guess or make up data.</div>
</div>
</div>


<div class="content-box">
<div class="practice-box">
  <div class="content-header">
<div class="practice-title">✅ You can always add more later.</div>
    <h2>Best practices when filling the form</h2>
<div class="practice-text">Start with Tier 1, then upgrade to Tier 2/3 as you gather more data.</div>
    <p>These keep the database usable for you and everyone else later.</p>
</div>
  </div>


  <div class="practice-list">
<div class="practice-box">
    <div class="practice-box">
<div class="practice-title">✅ Use consistent formatting.</div>
      <span class="practice-icon">✅</span>
<div class="practice-text">Dates as <code>YYYY-MM-DD</code>, coordinates as decimal degrees.</div>
      <div class="practice-body">
</div>
        <strong>Fill out what you know, skip what you don't.</strong>
        <span>Don't guess or make up data.</span>
      </div>
    </div>


    <div class="practice-box">
<div class="practice-box">
      <span class="practice-icon">✅</span>
<div class="practice-title">✅ Document your sources.</div>
      <div class="practice-body">
<div class="practice-text">Record who you talked to and where information came from.</div>
        <strong>You can always add more later.</strong>
</div>
        <span>Start with Tier 1, then upgrade to Tier 2/3 as you gather more data.</span>
      </div>
    </div>


    <div class="practice-box">
<div class="practice-box">
      <span class="practice-icon">✅</span>
<div class="practice-title">✅ Take photos in the field.</div>
      <div class="practice-body">
<div class="practice-text">Photo documentation is crucial for verification.</div>
        <strong>Use consistent formatting.</strong>
</div>
        <span>Dates as <code>YYYY-MM-DD</code>, coordinates as decimal degrees.</span>
      </div>
    </div>


    <div class="practice-box">
<div class="practice-box">
      <span class="practice-icon">✅</span>
<div class="practice-title">✅ Preserve GPS metadata in photos.</div>
      <div class="practice-body">
<div class="practice-text">Don't strip EXIF data from field photos.</div>
        <strong>Document your sources.</strong>
</div>
        <span>Record who you talked to and where information came from.</span>
      </div>
    </div>


    <div class="practice-box">
</div>
      <span class="practice-icon">✅</span>
      <div class="practice-body">
        <strong>Take photos in the field.</strong>
        <span>Photo documentation is crucial for verification.</span>
      </div>
    </div>
 
    <div class="practice-box">
      <span class="practice-icon">✅</span>
      <div class="practice-body">
        <strong>Preserve GPS metadata in photos.</strong>
        <span>Don't strip EXIF data from field photos.</span>
      </div>
    </div>
  </div>
</div>
</div>


<div class="cta-box">
<div class="cta-box">
  <div class="cta-inner">
<div class="cta-inner">
    <h3>Ready to create an accession?</h3>
<h3>Ready to create an accession?</h3>
    <p>
<p>Start by choosing a clear page name.</p>
      Start by choosing a clear page name.<br />
      <span class="cta-formula">[Year] [Specific Location] [Collection Type]</span>
    </p>


    <div class="cta-input">
<div class="cta-formula">
      {{#forminput:form=Accession
<span class="cta-formula-label">Pattern</span>
        |placeholder=e.g., 2024 Malana Village General Population
<span class="cta-formula-text">[Year] [Specific Location] [Collection Type]</span>
        |button text=Create Accession
</div>
      }}
    </div>


    <div class="cta-tip">
<div class="cta-form">
      📋 <strong>Tip:</strong> If a page with that name already exists, you'll be taken to edit that existing accession instead of creating a duplicate.
{{#forminput:form=Accession
    </div>
|placeholder=e.g., 2024 Malana Village General Population
  </div>
|button text=Create Accession
}}
</div>
 
<div class="cta-tip">
📋 <strong>Tip:</strong> If a page with that name already exists, you'll be taken to edit that existing accession instead of creating a duplicate.
</div>
</div>
</div>
</div>


<div class="landing-footer">
<div class="landing-footer">
  <span class="footer-label">Need help?</span>
<strong>Need help?</strong> [[Project:Documentation|Full documentation]] • [[Special:Search|Search existing accessions]] • [[Special:Ask|Browse by property]]
  [[Project:Documentation|Full documentation]] • [[Special:Search|Search existing accessions]] • [[Special:Ask|Browse by property]]
</div>
</div>


</div>
</div>

Latest revision as of 09:49, 20 November 2025

Create New Accession

Document landrace cannabis populations for long-term conservation.

⚠️ Read this before creating an accession

1. Search for existing entries first:

  • Check if this population/field is already documented
  • Use Search to look for location names, collector names, dates
  • Avoid creating duplicates – it's better to add to an existing entry

2. Understand what makes a unique accession:

  • Each accession = ONE collection event from ONE specific location on ONE date
  • Same field, different years = different accessions
  • Same year, different fields = different accessions
  • General population vs specific plant selection = different accessions

3. Know your tier level (handled automatically in the form):

  • Tier 1 (Essential): Minimum viable documentation – GPS, date, basic provenance
  • Tier 2 (Enhanced): Scientific utility – botanical descriptions, cultural context
  • Tier 3 (Research Grade): Publication-ready – lab results, comprehensive preservation

Naming convention (critical)

Use descriptive names that uniquely identify the collection:

✅ Recommended
  • 2023 Atolang General Population
  • 2024 Malana Village Selection #3
  • Kut Bak 2022 November Collection
  • Parvati Valley Point of Origin 2023
  • Mae Hong Son Highland Seeds 2024-03

Why good: Specific location, year/date, collection type

❌ Avoid
  • Thai Landrace
  • Indian Strain
  • Colombian
  • Himalayan #2
  • Local Variety

Why bad: Too generic, no date, no specific location, will cause duplicates

NAMING FORMULA

[Year] [Specific Location] [Collection Type/Details]

e.g. 2024 Malana Village General Population

Documentation tiers

All accessions start at Tier 1. Extra fields in the form push them toward Tier 2 and Tier 3.

TIER 1 Essential field collection (≈ 46 fields)

Required for ANY accession:

  • Accession ID (formal identifier)
  • Collection date
  • GPS coordinates + elevation
  • Complete geographic hierarchy (country → province → locality)
  • Growing region → Appellation → Field
  • Collector name
  • Collection method (seeds/cuttings/tissue)
  • Sample size
  • Traditional local name
  • Classification (Landrace/Feral/Other)
  • Basic conservation assessment
  • Photo evidence (minimum: whole plant + inflorescences + habitat)

⚠️ If you don't have this minimum data, don't create the accession yet. Gather more information first.

TIER 2 Enhanced scientific documentation (≈ 98 additional fields)

Adds scientific utility:

  • Detailed botanical descriptions (plant height, leaf shape, flowering traits)
  • Environmental context (climate, soil, associated flora)
  • Cultural uses and traditional practices
  • Cultivation methods and farmer practices
  • Detailed conservation threat assessments
  • Extended photographic documentation

Complete when: Conducting research, writing reports, building comprehensive databases.

TIER 3 Research-grade documentation (≈ 83 additional fields)

Publication-ready with lab results:

  • Complete cannabinoid profile (THC, CBD, CBG, CBN, CBC, THCV, CBDV)
  • Complete terpene profile (10+ terpenes)
  • Genetic analysis results
  • Laboratory reports and dates
  • Detailed preservation status (seed banks, tissue culture)
  • Material transfer agreements
  • Literature references and citations
  • Complete research priorities

Complete when: Working with research institutions, publishing papers, or formal conservation programs.

Common mistakes to avoid

❌ Creating "placeholder" entries
Don't create an accession just because you heard about a location. Wait until you have actual samples and data.
❌ Using only generic location names
"Colombian Gold" or "Thai Stick" are not specific enough. You need: specific village/field + year + collector.
❌ Mixing multiple collection events
Each accession = one collection event. If you collected from the same field in 2023 and 2024, create two separate accessions.
❌ Skipping required Tier 1 fields
If you don't have GPS coordinates, collection date, or collector name, the entry is not valid. Gather this information before creating the accession.
❌ Creating duplicates instead of searching
ALWAYS search first. Multiple entries for the same collection creates chaos in the database.

Best practices when filling the form

✅ Fill out what you know, skip what you don't.
Don't guess or make up data.
✅ You can always add more later.
Start with Tier 1, then upgrade to Tier 2/3 as you gather more data.
✅ Use consistent formatting.
Dates as YYYY-MM-DD, coordinates as decimal degrees.
✅ Document your sources.
Record who you talked to and where information came from.
✅ Take photos in the field.
Photo documentation is crucial for verification.
✅ Preserve GPS metadata in photos.
Don't strip EXIF data from field photos.

Ready to create an accession?

Start by choosing a clear page name.

Pattern [Year] [Specific Location] [Collection Type]

📋 Tip: If a page with that name already exists, you'll be taken to edit that existing accession instead of creating a duplicate.