Part V — In your pocket and at harvest
10 · The harvest: good practices and glossary
Harvesting also means leaving fruit on the tree for those who come after.
Before publishing
- Consent. The person in the photo, the voice in the recording, the family behind the recipe: do they know, and do they want it? Do they want their name on it? If in doubt, ask — or use Restricted.
- What belongs inside. Some knowledge the community keeps to itself (prayers, rituals, sacred places). Agree in the circle on what goes public, what stays restricted, and what doesn't go in at all.
- Who may use it. The licence says so. "Use upon consulting the council" is as valid a licence as the open ones.
A good saber
- A title that says what it is: "Jongo at the baobab festival, 2024", not "IMG_2031".
- A description with who, where, when, why — in a few lines.
- Tags agreed on by the community, always written the same way (
jongo, notJongoin one andjongosin another). - Territory and place, when it makes sense: the saber appears on the Map and in the territory.
- A caption on every important photo: it helps people who can't see and people who are searching.
- Vocabulary in the transcription: local names the machine doesn't know.
The machine helps, people review
Transcription, text recognition and automatic translation make drafts. They get names, community words, metaphors and songs wrong. Review — and correct in the editor: whatever you correct, the machine won't overwrite again.
Looking after the archive
- Prefer one saber with several photos of the same occasion to twenty saberes with one photo each.
- Gather in Roots what tells a story.
- Use the languages the community speaks — and ask someone who speaks the language to review.
- Made a mistake? The History keeps everything: you can go back.
Glossary
| Word | Means |
|---|---|
| archive | the set of saberes; also the app that shows them all |
| article | a text saber (with images inside), shown on the Blog |
| attachment / file | photo, video, audio or document inside a saber |
| copy | a file present on a mucua; requesting a copy = bringing it here |
| draft | an article not published yet; or a text made by the machine for review |
| encrypted | protection that stores the saber encrypted: only readers open it |
| galaxy | a whole archive, shared by several mucuas |
| group | a named set of people, used for readers and editors |
| history | the list of changes of a saber or a galaxy |
| book | a root in chapters, with contents |
| mocambola | a person with a Baobáxia account |
| live | a broadcast happening now, through a channel; the recording becomes a private saber |
| channel | the radio or TV made from the archive, playing on its own from the schedule |
| schedule | the channel's time slots and what plays in each one |
| work | album, audiobook or podcast: a saber with tracks, chapters or episodes |
| mucua | the community's computer that keeps the archive |
| OXALÁ / PAJÉ / USER | the roles: administers the galaxy / looks after the mucua / takes part |
| restricted | protection: only the chosen readers read it |
| root | a collection of saberes: list, story or book |
| saber | anything kept in Baobáxia |
| sync | two mucuas exchanging what each has that is new |
| tag | a word that groups saberes on the same subject |
| territory | a place, physical or symbolic, that saberes belong to |
| type (nature) | the kind of saber: media, article, event… |
| writing in | the language you write a new saber's text in |
| XMPP | free messaging; Baobáxia's bot talks through it |
To talk about in the circle
- What agreements does the community want to write down (about consent, licences, tags, languages)? How about publishing them as an article?
- What do you want someone to find in this archive a hundred years from now?