Fieldwork Collection Consent Ethics Checklist
Record caller fieldwork consent/collection ethics evidence, not legal compliance or approval when any criterion is unknown. Community-specific restrictions prevail. Independently established criterion columns: informed consent independently recorded, withdrawal terms communicated, community permissions independently established, data handling and access independently reviewed, attribution/anonymity choices recorded. No certification or invented missing evidence.
Description
Folklore fieldwork creates records involving participants, communities and future reuse.
Folklore fieldwork creates records involving participants, communities and future reuse.1
Consent, withdrawal arrangements, permissions, data handling and attribution require separately documented evidence. Use this tool to separate witnessed, known missing and unknown criterion evidence.
When to use Fieldwork Collection Consent Ethics Checklist
Use this tool to separate witnessed, known missing and unknown criterion evidence. Identify the community, narrative version, source edition and interpretation context; prepare any annotations independently.
How to use Fieldwork Collection Consent Ethics Checklist and understand its results
- Identify the community, narrative version, source edition and interpretation context; prepare any annotations independently.
- Enter observedCriterionFlags, criterionKnownFlags, using the field meanings and rules below, then run the tool.
- Read result.witnessedCriteria, result.knownMissingCriteria, result.unknownCriteria. Interpret the fields using their units, signs and evidence conventions below.
- If input validation fails, correct the reported field and run again. Before applying the result, check reference scope, model assumptions and any missing evidence or placeholder values.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| observedCriterionFlags | Observed criterion flags; binary 0/1 under the definitions below | list of number | Required |
| criterionKnownFlags | Criterion known flags; binary 1=known, 0=unknown, in the order described below | list of number | Required |
Enter exactly 5 binary observation flags and binary known flags in the criterion order below. Return labels as witnessed when both flags are 1, known missing when known=1 and observed=0, and unknown whenever known=0 regardless of the observation placeholder. The checker does not inspect a narrative or site and does not turn these separate labels into an overall approval.
| Zero-based column | Criterion |
|---|---|
| 0 | informed consent independently recorded |
| 1 | withdrawal terms communicated |
| 2 | community permissions independently established |
| 3 | data handling and access independently reviewed |
| 4 | attribution/anonymity choices recorded |
witnessed={label_i:known_i=1 and observed_i=1}; missing={label_i:known_i=1 and observed_i=0}; unknown={label_i:known_i=0} Use the exact units, boundary rules, ordering and missing-evidence conventions above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Structured calculation or selected reference, with fields listed below | object |
| result.witnessedCriteria | Labels marked both known and observed present | list of string |
| result.knownMissingCriteria | Labels known but observed absent | list of values |
| result.unknownCriteria | Labels whose evidence is marked unknown | list of values |
{
"input": {
"observedCriterionFlags": [
1,
1,
1,
1,
1
],
"criterionKnownFlags": [
1,
1,
1,
1,
1
]
},
"output": {
"result": {
"witnessedCriteria": [
"informed consent independently recorded",
"withdrawal terms communicated",
"community permissions independently established",
"data handling and access independently reviewed",
"attribution/anonymity choices recorded"
],
"knownMissingCriteria": [],
"unknownCriteria": []
}
}
} Limitations and assumptions
Features and criteria are independent annotations. Compatible candidates and retained unknown evidence do not establish an identity, interpretation, overall pass or permission.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse evidence arrays fail validation; the specific bounds and alignment requirements are stated above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful result reporting false, no matches or missing evidence.
Alternative or Complementary methods
Use Child Ballads Francis Child Numbering Catalog Lookup for this related task: Child ballad numbers identify entries in a particular editorial collection.
Use Chapbook Broadside Popular Print Era Lookup when its separate inputs and assumptions fit the question: Chapbooks and broadsides are different formats associated with popular print circulation.
References
Similar or alternative tools
- Child Ballads Francis Child Numbering Catalog Lookup
Child ballad numbers identify entries in a particular editorial collection.
- Chapbook Broadside Popular Print Era Lookup
Chapbooks and broadsides are different formats associated with popular print circulation.