Interview
An Interview is one person’s pass through a question script, led by an Agent, whose answers become Evidence.
Its answers feed the Story word for word.
Properties
| Property | Type | Required | Description |
|---|---|---|---|
script | Template | required | The questions asked. |
transcript | text | What was said. |
Inherited from Thread: 1 property
| Property | Type | Required | Description |
|---|---|---|---|
subject | string | What the Thread is about. |
Object
{
"$id": "https: //api.sb/ routewise.dev/ interviews/ interview_1",
"$type": "Interview",
"subject": "Example subject",
"script": "template_1",
"transcript": "Example transcript"
}Relationships
- An Interview is quoted in many Stories: the Interviews whose words the Story reuses.
quotedIn, inversequotes. - An Interview yields many pieces of Evidence: an Interview captures quotes and commitments, each graded as Evidence.
yields, inverseyieldedBy.
Verbs
createCreates an Interview.POST /{namespace}/interviewsgetReturns one Interview by id.GET /{namespace}/interviews/{id}listReturns Interviews, newest first, one page at a time.GET /{namespace}/interviews
An Interview is kept forever and never edited: it has no update or delete.
Permissions
Which Access level may call each Verb. One-way Verbs wait their delay window.
| Operation | owner | admin | member | viewer |
|---|---|---|---|---|
Interview.create | Yes | Yes | Yes | No |
Interview.get | Yes | Yes | Yes | Yes |
Interview.list | Yes | Yes | Yes | Yes |
Call it
Add an interview to LedgerLark with a template.Example
An Agent runs a five-question Interview with a music teacher about how she books lessons. Her answer, two lessons lost each week to text-message mixups, enters the transcript and becomes Evidence on the Problem.