Knowledge Base (KB) Licensor & Developer

Knowledge Base (KB) Licensor & Developer

Tongston Holdings is a brand for secondary schools, educators and students who dare to think, create and sell their ideas. We exist as a holding company currently with four subsidiaries - Tongston College, Tongston Institute, Tongston Ventures and Tongston Media.

Knowledge Base (KB) Licensor & Developer Job Type Remote Qualification BA/BSc/HND

Experience

Location

Job Field ICT / Computer

Overview

Tongston is looking for a Knowledge Base Licensor & Developer to support the Education workstream for T-World and the wider Tongston ecosystem. The role combines external-source licensing and permissions review with practical knowledge-base development: identifying relevant external sources, classifying their use status, sourcing approved knowledge materials, and converting cleared content into structured, tagged, traceable, AI-ready KB objects. This role sits under the Education workstream because the knowledge base is part of T-World’s learning, curriculum, teaching, assessment, recommendation and VIP development foundation. This role is for someone who can operate with ownership, good judgement, documentation discipline and weekly delivery accountability in a fast-moving AI-enabled product environment.

Role Purpose The purpose of this role is to own the first-line external knowledge-base pipeline: from source identification and licensing classification to KB object development, indexing, handoff and maintenance.

The role helps Tongston answer Which external sources are relevant to T-World’s education, enterprise, media, finance, user journey, functional industry, role, assessment, VIP Metrics and AI-use needs? What are the licensing, copyright, permissions, attribution, restriction, commercial-use or platform-use conditions attached to each source or content item? Which materials are green, yellow, orange, red, restricted, blocked, permission-pending or ready for development? How should cleared external materials be structured, tagged, stored, indexed and maintained as usable KB objects? What needs to be handed off to other team members.

Roles & Responsibilities

THINK (Source Strategy, Licensing Logic & KB Development Planning): Translate

Education

• Lead priorities into clear external-source plans, source lists, licensing-review priorities and KB development deliverables.
• Identify relevant source environments and content items, including websites, repositories, journals, books, courses, reports, policy documents, articles, chapters, datasets, attachments and other knowledge materials.
• Review licensing terms, copyright notices, IP notices, platform terms, permissions language, attribution requirements, commercial-use restrictions, modification/reuse rights, download restrictions, expiry conditions and object-level use terms.
• Classify sources and content items using Tongston’s approved traffic-light or permissions framework, including green, yellow, orange, red, restricted, unclear, mixed, permission-pending and blocked statuses. Distinguish between platform-level clearance and object-level clearance, especially where a website or database is broadly usable but a particular document, chapter, course or attachment has different conditions.
• Plan how approved or cleared materials should be converted into KB objects, including object type, scope, tags, metadata, source references, owner, review status and downstream AI use case.
• Flag legal, licensing, IP, confidentiality, source-quality, bias, sensitivity, currency or use-boundary risks early instead of making unsupported assumptions.

CREATE (Clear Sources, Build KB Objects & Maintain Registers):

• Populate and maintain the Licensing and Permissions Register with source name, URL, source type, content item, date accessed, licence/permission status, classification, restrictions, attribution requirements, evidence, rationale, owner and next action.
• Maintain evidence trails such as source links, screenshots, saved files, terms notes, permission notes, licence evidence, download records and use-boundary summaries.
• Source actual external KB materials only from approved, green, cleared or conditionally cleared sources, in line with the documented use restrictions.
• Extract, summarise, structure, tag and format cleared materials into KB-ready objects using approved templates, metadata fields, naming conventions, folder structures and version-control rules.
• Populate the Master KB Index and related KB trackers with object IDs, object titles, object types, short descriptions, sou