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
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">
<h1>Create New Accession</h1>
    <div class="landing-kicker">Accession Intake</div>
<p>Document landrace cannabis genetic resources for conservation</p>
    <h1>Create New Accession</h1>
</div>
    <p>Document landrace cannabis populations for long-term conservation.</p>
  </div>
 
  <div class="warning-box">
    <h3>⚠️ Read this before creating an accession</h3>
 
    '''1. Search for existing entries first:'''
    * Check if this population/field is already documented
    * Use [[Special:Search|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
  </div>


<div class="warning-box">
  <div class="content-box">
<h3>⚠️ READ THIS FIRST - Before Creating an Accession</h3>
    <div class="content-header">
      <h2>Naming convention (critical)</h2>
      <p>Good names prevent duplicate accessions and keep the hierarchy usable.</p>
    </div>


'''1. Search for existing entries first:'''
    <p class="content-intro">
* Check if this population/field is already documented
      <strong>Use descriptive names that uniquely identify the collection:</strong>
* Use [[Special:Search|Search]] to look for location names, collector names, dates
    </p>
* Avoid creating duplicates - it's better to add to an existing entry


'''2. Understand what makes a unique accession:'''
    <div class="name-examples">
* 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:'''
      <div class="name-card name-good">
* '''Tier 1 (Essential)''': Minimum viable documentation - GPS, date, basic provenance
        <div class="name-card-header">
* '''Tier 2 (Enhanced)''': Scientific utility - botanical descriptions, cultural context
          <span class="name-pill name-pill-good">✅ Recommended</span>
* '''Tier 3 (Research Grade)''': Publication-ready - lab results, comprehensive preservation
          <div class="name-card-title">GOOD NAMES</div>
</div>
        </div>
        <ul>
          <li>2023 Atolang General Population</li>
          <li>2024 Malana Village Selection #3</li>
          <li>Kut Bak 2022 November Collection</li>
          <li>Parvati Valley Point of Origin 2023</li>
          <li>Mae Hong Son Highland Seeds 2024-03</li>
        </ul>
        <div class="name-why">
          <strong>Why good:</strong> Specific location, year/date, collection type
        </div>
      </div>


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


<p><strong>Use descriptive names that uniquely identify the collection:</strong></p>
    </div>


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


<div class="name-good">
  <div class="content-box">
<div class="name-good-header">✅ GOOD NAMES</div>
    <div class="content-header">
* 2023 Atolang General Population
      <h2>Documentation tiers</h2>
* 2024 Malana Village Selection #3
      <p>All accessions start at Tier 1. Extra fields in the form push them toward Tier 2 and Tier 3.</p>
* Kut Bak 2022 November Collection
    </div>
* Parvati Valley Point of Origin 2023
* Mae Hong Son Highland Seeds 2024-03
<div class="name-good-why">
<strong>Why good:</strong> Specific location, year/date, collection type
</div>
</div>


<div class="name-bad">
    <div class="tier-grid">
<div class="name-bad-header">❌ BAD NAMES</div>
* Thai Landrace
* Indian Strain
* Colombian
* Himalayan #2
* Local Variety
<div class="name-bad-why">
<strong>Why bad:</strong> Too generic, no date, no specific location, will cause duplicates
</div>
</div>


</div>
      <details open class="tier-box tier-1">
        <summary>
          <span class="tier-pill tier-pill-1">Tier 1</span>
          <span class="tier-title">Essential field collection</span>
          <span class="tier-count">(≈ 46 fields)</span>
        </summary>
        <div class="tier-content">
          <p><strong>Required for ANY accession:</strong></p>
          <ul>
            <li>Accession ID (formal identifier)</li>
            <li>Collection date</li>
            <li>GPS coordinates + elevation</li>
            <li>Complete geographic hierarchy (country → province → locality)</li>
            <li>Growing region → Appellation → Field</li>
            <li>Collector name</li>
            <li>Collection method (seeds/cuttings/tissue)</li>
            <li>Sample size</li>
            <li>Traditional local name</li>
            <li>Classification (Landrace/Feral/Other)</li>
            <li>Basic conservation assessment</li>
            <li>Photo evidence (minimum: whole plant + inflorescences + habitat)</li>
          </ul>


<div class="formula-box">
          <p class="tier-warning">
<strong>Naming Formula:</strong><br>
            ⚠️ If you don't have this minimum data, don't create the accession yet. Gather more information first.
<code>[Year] [Specific Location] [Collection Type/Details]</code>
          </p>
</div>
        </div>
</div>
      </details>


<div class="content-box">
      <details class="tier-box tier-2">
<h2>Documentation Tier Requirements</h2>
        <summary>
          <span class="tier-pill tier-pill-2">Tier 2</span>
          <span class="tier-title">Enhanced scientific documentation</span>
          <span class="tier-count">(≈ 98 additional fields)</span>
        </summary>
        <div class="tier-content">
          <p><strong>Adds scientific utility:</strong></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>


<details open class="tier-box tier-1">
          <p><strong>Complete when:</strong> Conducting research, writing reports, building comprehensive databases.</p>
<summary>Tier 1: Essential Field Collection (46 fields)</summary>
        </div>
<div class="tier-content">
      </details>
<strong>Required for ANY accession:</strong>
* 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)


<p class="tier-warning">⚠️ If you don't have this minimum data, don't create the accession yet. Gather more information first.</p>
      <details class="tier-box tier-3">
</div>
        <summary>
</details>
          <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>


<details class="tier-box tier-2">
          <p><strong>Complete when:</strong> Working with research institutions, publishing papers, or formal conservation programs.</p>
<summary>Tier 2: Enhanced Scientific Documentation (98 additional fields)</summary>
        </div>
<div class="tier-content">
      </details>
<strong>Adds scientific utility:</strong>
* 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


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


<details class="tier-box tier-3">
  <div class="content-box">
<summary>Tier 3: Research Grade Documentation (83 additional fields)</summary>
    <div class="content-header">
<div class="tier-content">
      <h2>Common mistakes to avoid</h2>
<strong>Publication-ready with lab results:</strong>
      <p>If you catch these before saving, you save yourself clean-up later.</p>
* Complete cannabinoid profile (THC, CBD, CBG, CBN, CBC, THCV, CBDV)
    </div>
* 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


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


<div class="content-box">
      <div class="mistake-box">
<h2>Common Mistakes to Avoid</h2>
        <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 class="mistake-box">
      <div class="mistake-box">
<div class="mistake-title">❌ Creating "placeholder" entries</div>
        <div class="mistake-title">❌ Using only generic location names</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 class="mistake-text">
</div>
          "Colombian Gold" or "Thai Stick" are not specific enough. You need: specific village/field + year + collector.
        </div>
      </div>


<div class="mistake-box">
      <div class="mistake-box">
<div class="mistake-title">❌ Using only generic location names</div>
        <div class="mistake-title">❌ Mixing multiple collection events</div>
<div class="mistake-text">"Colombian Gold" or "Thai Stick" are not specific enough. You need: specific village/field + year + collector.</div>
        <div class="mistake-text">
</div>
          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">❌ Mixing multiple collection events in one entry</div>
        <div class="mistake-title">❌ Skipping required Tier 1 fields</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 class="mistake-text">
</div>
          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="mistake-box">
<div class="mistake-title">❌ Leaving required Tier 1 fields blank</div>
        <div class="mistake-title">❌ Creating duplicates instead of searching</div>
<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 class="mistake-text">
</div>
          ALWAYS search first. Multiple entries for the same collection creates chaos in the database.
        </div>
      </div>


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


<div class="content-box">
  <div class="content-box">
<h2>Best Practices</h2>
    <div class="content-header">
      <h2>Best practices when filling the form</h2>
      <p>These keep the database usable for you and everyone else later.</p>
    </div>


<div class="practice-box">
    <div class="practice-list">
✅ <strong>Fill out what you know, skip what you don't</strong> - Don't guess or make up data
      <div class="practice-box">
</div>
        <span class="practice-icon"></span>
        <div class="practice-body">
          <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">
✅ <strong>You can always add more later</strong> - Start with Tier 1, upgrade to Tier 2/3 as you gather more data
        <span class="practice-icon"></span>
</div>
        <div class="practice-body">
          <strong>You can always add more later.</strong>
          <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">
✅ <strong>Use consistent formatting</strong> - Follow the suggested formats (dates as YYYY-MM-DD, coordinates as decimal degrees)
        <span class="practice-icon"></span>
</div>
        <div class="practice-body">
          <strong>Use consistent formatting.</strong>
          <span>Dates as <code>YYYY-MM-DD</code>, coordinates as decimal degrees.</span>
        </div>
      </div>


<div class="practice-box">
      <div class="practice-box">
✅ <strong>Document your sources</strong> - Record who you talked to, where information came from
        <span class="practice-icon"></span>
</div>
        <div class="practice-body">
          <strong>Document your sources.</strong>
          <span>Record who you talked to and where information came from.</span>
        </div>
      </div>


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


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


{{#forminput:form=Accession|placeholder=e.g., 2024 Malana Village General Population|button text=Create Accession}}
      <div class="cta-input">
        {{#forminput:form=Accession
          |placeholder=e.g., 2024 Malana Village General Population
          |button text=Create Accession
        }}
      </div>


<div class="cta-tip">
      <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.
        📋 <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>


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


</div>
</div>

Revision as of 08:53, 20 November 2025

Accession Intake

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)

Good names prevent duplicate accessions and keep the hierarchy usable.

Use descriptive names that uniquely identify the collection:

         ✅ Recommended
GOOD NAMES
  • 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
BAD NAMES
  • 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.

     <details open class="tier-box tier-1">
       <summary>
         Tier 1
         Essential field collection
         (≈ 46 fields)
       </summary>

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.

     </details>
     <details class="tier-box tier-2">
       <summary>
         Tier 2
         Enhanced scientific documentation
         (≈ 98 additional fields)
       </summary>

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.

     </details>
     <details class="tier-box tier-3">
       <summary>
         Tier 3
         Research-grade documentation
         (≈ 83 additional fields)
       </summary>

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.

     </details>

Common mistakes to avoid

If you catch these before saving, you save yourself clean-up later.

❌ 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

These keep the database usable for you and everyone else later.

       
         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. [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.