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
 
(4 intermediate revisions by the same user not shown)
Line 4: Line 4:
<div class="landing-header">
<div class="landing-header">
<h1>Create New Accession</h1>
<h1>Create New Accession</h1>
<p>Document landrace cannabis genetic resources for 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 FIRST - Before Creating an Accession</h3>
<h3>⚠️ Read this before creating an accession</h3>


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


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


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


<div class="content-box">
<div class="content-box">
<h2>Naming Convention - CRITICAL</h2>
<h2>Naming convention (critical)</h2>


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


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


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


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


<div class="content-box">
<div class="content-box">
<h2>Documentation Tier Requirements</h2>
<h2>Documentation tiers</h2>


<details open class="tier-box tier-1">
<p>All accessions start at Tier 1. Extra fields in the form push them toward Tier 2 and Tier 3.</p>
<summary>Tier 1: Essential Field Collection (46 fields)</summary>
<div class="tier-content">
<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)


<div class="tier-box tier-1">
<div class="tier-box-header">
<span class="tier-label tier-label-1">TIER 1</span>
<span class="tier-title">Essential field collection</span>
<span class="tier-count">(≈ 46 fields)</span>
</div>
<p class="tier-subtitle">Required for ANY accession:</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>
<p class="tier-warning">⚠️ If you don't have this minimum data, don't create the accession yet. Gather more information first.</p>
<p class="tier-warning">⚠️ If you don't have this minimum data, don't create the accession yet. Gather more information first.</p>
</div>
</div>
</details>


<details class="tier-box tier-2">
<div class="tier-box tier-2">
<summary>Tier 2: Enhanced Scientific Documentation (98 additional fields)</summary>
<div class="tier-box-header">
<div class="tier-content">
<span class="tier-label tier-label-2">TIER 2</span>
<strong>Adds scientific utility:</strong>
<span class="tier-title">Enhanced scientific documentation</span>
* Detailed botanical descriptions (plant height, leaf shape, flowering traits)
<span class="tier-count">(98 additional fields)</span>
* Environmental context (climate, soil, associated flora)
</div>
* Cultural uses and traditional practices
<p class="tier-subtitle">Adds scientific utility:</p>
* Cultivation methods and farmer practices
<ul>
* Detailed conservation threat assessments
<li>Detailed botanical descriptions (plant height, leaf shape, flowering traits)</li>
* Extended photographic documentation
<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>


<strong>Complete when:</strong> Conducting research, writing reports, building comprehensive databases
<div class="tier-box tier-3">
<div class="tier-box-header">
<span class="tier-label tier-label-3">TIER 3</span>
<span class="tier-title">Research-grade documentation</span>
<span class="tier-count">(≈ 83 additional fields)</span>
</div>
<p class="tier-subtitle">Publication-ready with lab results:</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 class="tier-note">Complete when: Working with research institutions, publishing papers, or formal conservation programs.</p>
</div>
</div>
</details>
<details class="tier-box tier-3">
<summary>Tier 3: Research Grade Documentation (83 additional fields)</summary>
<div class="tier-content">
<strong>Publication-ready with lab results:</strong>
* 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


<strong>Complete when:</strong> Working with research institutions, publishing papers, formal conservation programs
</div>
</details>
</div>
</div>


<div class="content-box">
<div class="content-box">
<h2>Common Mistakes to Avoid</h2>
<h2>Common mistakes to avoid</h2>
 
<div class="mistake-grid">


<div class="mistake-box">
<div class="mistake-box">
Line 137: Line 156:


<div class="mistake-box">
<div class="mistake-box">
<div class="mistake-title">❌ Mixing multiple collection events in one entry</div>
<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 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>


<div class="mistake-box">
<div class="mistake-box">
<div class="mistake-title">❌ Leaving required Tier 1 fields blank</div>
<div class="mistake-title">❌ Skipping required Tier 1 fields</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">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>
Line 149: Line 168:
<div class="mistake-title">❌ Creating duplicates instead of searching</div>
<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 class="mistake-text">ALWAYS search first. Multiple entries for the same collection creates chaos in the database.</div>
</div>
</div>
</div>
</div>
</div>


<div class="content-box">
<div class="content-box">
<h2>Best Practices</h2>
<h2>Best practices when filling the form</h2>
 
<div class="practice-grid">


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


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


<div class="practice-box">
<div class="practice-box">
<strong>Take photos in the field</strong> - Photo documentation is crucial for verification
<div class="practice-title">Take photos in the field.</div>
<div class="practice-text">Photo documentation is crucial for verification.</div>
</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
<div class="practice-title">Preserve GPS metadata in photos.</div>
<div class="practice-text">Don't strip EXIF data from field photos.</div>
</div>
 
</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.</p>
 
<div class="cta-formula">
<span class="cta-formula-label">Pattern</span>
<span class="cta-formula-text">[Year] [Specific Location] [Collection Type]</span>
</div>


{{#forminput:form=Accession|placeholder=e.g., 2024 Malana Village General Population|button text=Create Accession}}
<div class="cta-form">
{{#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]]
<strong>Need help?</strong> [[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.