Skip to content

Glossary

needs verification

Use these engineering names consistently. The concept pages explain the qualifications behind each short definition.

TermMeaning
2FATwo-factor authentication, an additional account sign-in check.
Acting contextThe identity an administrator selects when working on someone else's behalf; only administrators can change it.
AdministratorA Core admin-panel user who enters mobile workflows through impersonation.
Anonymous visitorA public website reader who does not sign in.
AnsibleInfrastructure provisioning and deployment automation.
APIApplication programming interface, the contract between software systems.
APKAndroid application package, an installable Android build.
ChapterA named recorded segment of an LT Work.
Cloudflare PagesThe hosting platform used by the public website.
Cloudflare R2Object storage for finished media.
CMSContent management system, such as Strapi or Pages CMS.
ConnectionA coordinator-to-researcher relationship with its own states.
CoordinatorAn institutional persona managing researchers and creating works on their behalf.
Coordinator groupA shared coordinator acting context.
CSVComma-separated values, a tabular import and export format.
Digital Object Identifier (DOI)A permanent citation identifier; video minting is not integrated.
DNSDomain Name System, which maps hostnames to services.
EASExpo Application Services, used for mobile builds and distribution.
EditorA Strapi content-management persona, separate from Core roles.
Expert VideoPublic-help name for a three-chapter profile introduction; mapping to Publication Plus conflicts with the help source.
FilamentThe framework behind the Core admin panel.
File uploadCore metadata and control record for an uploaded object.
GHCRGitHub Container Registry, which stores deployment images.
Hetzner Object StorageStorage used for raw uploads, covers and avatars.
HugoThe static-site generator used by lt-web.
InstitutionAn organization associated with researchers or coordinators.
Latest ThinkingThe research-video product and client organization.
LT PlayerThe configurable web video player package.
LT WorkThe central record connecting a video workflow, subject and lifecycle.
MCPModel Context Protocol, exposed by Core for agent integrations.
Media Processing Engine (MPE)The service that transforms recorded takes into finished media.
MeilisearchThe search engine supporting public content search.
OAuthAuthorization flow used to link and sign in with an ORCID account.
OpenAlexThe scholarly database used to find source papers and institutions.
ORCID iDA persistent researcher identifier; profile claims and OAuth proof are distinct.
OTPOne-time password or code delivered by email for authentication.
Pages CMSThe content-editing interface used by the public help site.
PosterThe still image representing a playable Video.
PostgreSQLRelational database used by core and Strapi.
Processing runOne saved media-processing attempt and its result.
Profile VideoAn app-created introduction to a researcher, without source papers or DOI eligibility.
ProjectA domain grouping associated with researchers.
PublicationAn app-created research video with three chapters and one to five source papers.
Publication PlusAn editorial research video with five chapters and one source paper.
RedisThe shared service supporting backend queue and cache operations.
RenditionA playable media version produced by processing.
ResearcherThe subject of research content and a primary application persona.
Researcher draftA coordinator-created record for a person without an account.
Researcher pageA public page gathering a researcher’s LT content.
SanctumLaravel authentication used for bearer-token API access.
Source publicationAn OpenAlex paper linked as the subject matter of an LT Work.
StatusA major workflow group and a derived minor state.
StrapiThe CMS holding public and editorial content.
SubtitleTimed text associated with a Video.
Superseded VideoA retained historical output replaced as the current Video.
TerraformInfrastructure-as-code tool used for Hetzner resources.
TestFlightThe distribution route for the staging iOS app.
VideoThe playable output projected from processing, distinct from the LT Work.
Video PublicationThe public-help and Core display name for Publication.
VitePressThe static documentation framework used by this site.
VMVirtual machine, an isolated server instance.
WelinkThe software vendor delivering the LT system.
welink-dev-servicesThe shared local-development services workspace.

The seed vocabulary comes from the stack glossary. Domain terms are corroborated by LT Work, Researcher, LT Work type configuration and media integration. Service and application definitions are sourced on Applications and their individual application pages.

Coordinator's institutional definition remains candidate knowledge. The Expert Video mapping needs client confirmation. DOI minting and automatic downstream delivery remain gaps. These qualifications are collected in Open questions.

For maintainers: source references

These references require repository access. Everything needed to understand this page is explained above.

Latest Thinking · Welink internal guide