Eve library

Nisaba Scholar User Guide

Guide

Revision 1

On this page

A comprehensive guide for researchers using Nisaba, the ancient text analysis and cross-tradition scholarly research platform.

Version: 1.0 Last Updated: 2026-03-02


Table of Contents#

  1. Getting Started
  2. Workspace Configuration
  3. Corpus Browsing and Search
  4. Translation Comparison
  5. Collation Workflow
  6. Annotation and Commentary
  7. Critical Edition Creation
  8. Concept Mapping
  9. Export Options
  10. Personal Library

1. Getting Started#

1.1 What Is Nisaba?#

Nisaba is a digital humanities platform purpose-built for rigorous analysis of ancient texts across all major world traditions. Named after the Sumerian goddess of writing, learning, and scribal arts, the platform provides state-of-the-art tools for:

  • Reading and analyzing texts in their original ancient languages (Hebrew, Greek, Aramaic, Sanskrit, Pali, Classical Chinese, Arabic, Coptic, Latin, Cuneiform scripts, and many more)
  • Comparing translations with word-level and sentence-level alignment
  • Performing textual criticism: collating manuscripts, classifying variants, building stemmata, and generating critical apparatus
  • Discovering and documenting cross-tradition parallels and conceptual connections with scholarly rigor
  • Producing publication-ready critical editions with full apparatus

Nisaba is designed for biblical scholars, classicists, ancient Near East specialists, Indologists, Buddhist text scholars, Quranic studies researchers, and anyone working with humanity's oldest written heritage. The platform treats every textual tradition with equal scholarly depth and does not privilege any single canon or approach.

1.2 Account Setup#

To begin using Nisaba, you need an account.

  1. Navigate to the Nisaba landing page and select Create Account.
  2. Enter your institutional email address. Nisaba supports single sign-on (SSO) through most university identity providers. If your institution is listed, select it and authenticate through your university portal.
  3. If your institution does not support SSO, create a local account with an email and password. You will receive a verification email; click the link within it to activate your account.
  4. On first login, the platform will prompt you to complete your Scholar Profile:
    • Name and Affiliation: Your name and institutional affiliation, displayed on collaborative projects and published editions.
    • Research Interests: Select from a list of fields (e.g., New Testament Studies, Assyriology, Buddhist Textual Studies, Quranic Manuscript Traditions). These are used to recommend corpora and suggest relevant concept mappings.
    • Primary Languages: Indicate which ancient languages you read. This configures default fonts, keyboard layouts, and script-specific tools.
    • ORCID (optional): Link your ORCID identifier for citation tracking.

1.3 Workspace Overview#

After logging in, you land on the Workspace Dashboard. This is your research home base and provides quick access to all major features.

The dashboard is organized into the following areas:

  • Project Panel (left sidebar): Lists your active research projects. Each project is a container for texts, annotations, collation data, editions, and search results related to a particular line of inquiry. You can create new projects here or open existing ones.
  • Reading Area (center): The main content area where texts, translations, apparatus, and commentary are displayed. This area supports configurable split-pane layouts (covered in Section 2).
  • Tool Panel (right sidebar): Context-sensitive tools including the lexicon lookup, morphological parser, search interface, and annotation controls. The contents change based on what you are doing in the reading area.
  • Navigation Bar (top): Global controls for account settings, notification center, keyboard shortcut reference, and the corpus browser.
  • Status Bar (bottom): Displays the current text reference (e.g., nisaba://bible/gen/1:1), cursor position, current font, and sync status.

1.4 System Requirements#

Nisaba runs entirely in the web browser. No desktop installation is required.

Recommended browsers:

  • Google Chrome 110 or later
  • Mozilla Firefox 110 or later
  • Microsoft Edge 110 or later
  • Safari 16.4 or later

Minimum requirements:

  • A display resolution of at least 1280 x 800 pixels. For effective use of split-pane layouts and critical apparatus views, 1920 x 1080 or higher is recommended.
  • A stable internet connection for real-time collaboration and corpus access. After initial load, most reading and annotation features work offline with local caching; changes synchronize when connectivity resumes.
  • Unicode-capable operating system. All modern operating systems (Windows 10/11, macOS 11+, recent Linux distributions) meet this requirement.

Font considerations:

Nisaba ships bundled web fonts for all supported ancient scripts. If you prefer to use system-installed scholarly fonts (such as SBL Hebrew, SBL Greek, Gandhari Unicode, or Noto Sans Egyptian Hieroglyphs), you can configure this in workspace settings. See Section 2.3 for details.


2. Workspace Configuration#

2.1 Setting Up Your Research Environment#

Each research project in Nisaba has its own configurable environment. When you create a new project, you choose a Research Type from the following templates, each of which pre-configures the workspace layout and available tools:

Research Type Default Layout Pre-enabled Tools
Critical Edition Source text + Apparatus + Witnesses Collation engine, apparatus editor, stemma viewer
Translation Study Source + 2-3 translations side-by-side Alignment tool, divergence detector, interlinear toggle
Comparative Study Synoptic multi-tradition view Concept mapper, parallel finder, influence graph
Philological Analysis Text + Lexicon + Morphology panel Word frequency, hapax finder, discourse analyzer
Manuscript Survey Image viewer + Transcription Paleography tools, hand identifier, dating estimator

You can start from any template and customize freely. The template simply provides a sensible starting point.

To create a new project:

  1. In the Project Panel, select New Project.
  2. Enter a project title (e.g., "Isaiah 7:14 Translation History").
  3. Choose a Research Type template.
  4. Optionally add collaborators by email. Collaborators can be assigned roles: Owner, Editor, Commenter, or Viewer.
  5. Select Create. The workspace opens with the template layout.

2.2 Configuring Split-Pane Layout#

The reading area supports up to six simultaneous panes arranged in rows and columns. Each pane can display one of the following content types:

  • Source Text: The original-language text, optionally with morphological parsing displayed inline or on hover.
  • Translation: Any loaded translation of the source text.
  • Apparatus: The critical apparatus for the currently displayed passage.
  • Commentary: Scholarly commentary (your own annotations or imported commentaries).
  • Lexicon: Dictionary entries for the selected word.
  • Manuscript Image: IIIF-linked facsimile images of manuscript witnesses.
  • Search Results: Results from a corpus search, pinned for reference.
  • Concept Map: An interactive visualization of cross-tradition concept relationships.

To configure panes:

  1. Right-click in the reading area to open the Layout Menu.
  2. Select Split Horizontal or Split Vertical to add a pane.
  3. In the new pane, click the Content Selector (the dropdown at the top of the pane) and choose what to display.
  4. Panes can be resized by dragging the divider between them.
  5. To remove a pane, click the X button in its top-right corner.
  6. To save a layout for reuse, open Layout Menu > Save Layout As... and give it a name. Saved layouts are available from Layout Menu > Load Layout.

Synchronized scrolling: By default, all panes showing the same text or aligned translations scroll together. When you scroll the source text to Genesis 1:3, aligned translations and apparatus panes follow. You can disable sync for a specific pane by clicking the chain link icon in its title bar.

2.3 Setting Fonts for Ancient Scripts#

Nisaba bundles high-quality web fonts for every supported writing system. However, many scholars prefer specific typefaces for readability or aesthetic reasons. You can override the default font for any script.

To configure fonts:

  1. Open Settings > Fonts & Scripts.
  2. You will see a table listing every writing system with its current font.
  3. To change a font, click the font name and select from the dropdown, which includes:
    • Bundled fonts: Noto Sans/Serif families for all Unicode scripts, Aegean for Linear B, and specialized fonts for Cuneiform.
    • System fonts: Any font installed on your computer that covers the relevant Unicode range will appear here.
    • Custom web fonts: You can provide a URL to a WOFF2 font file if you have a license for a proprietary scholarly font.
  4. Adjust the font size per script (ancient scripts often benefit from larger sizes than Latin text).
  5. Select Apply to update all open panes.

Recommended scholarly fonts:

Script Recommended Font Notes
Biblical Hebrew SBL Hebrew, Ezra SIL Full cantillation mark support
Ancient Greek SBL Greek, Gentium Plus Polytonic accentuation
Syriac (Estrangela) Estrangelo Edessa, Noto Sans Syriac All Syriac script variants
Syriac (Serto) Serto Jerusalem, Noto Sans Syriac Western Syriac
Arabic (Quranic) Amiri, Scheherazade New Tajweed color markers
Cuneiform Noto Sans Cuneiform Sumerian, Akkadian, Hittite signs
Coptic Antinoou, Noto Sans Coptic All dialects
Devanagari (Sanskrit) Noto Sans Devanagari, Sanskrit 2003 Vedic extensions
Egyptian Hieroglyphic Noto Sans Egyptian Hieroglyphs Gardiner sign list coverage
Ethiopic (Ge'ez) Noto Sans Ethiopic, Abyssinica SIL Full syllabary
Classical Chinese Noto Serif CJK, Source Han Serif Traditional character forms
Tibetan Noto Sans Tibetan, Jomolhari Wylie transliteration toggle
Latin (Medieval) Junicode, Brill Medieval abbreviations and ligatures

2.4 Theme Selection#

Nisaba offers several visual themes optimized for extended reading sessions:

  • Light (Default): Clean white background suitable for daytime use and screen sharing.
  • Sepia: Warm, paper-toned background that reduces eye strain during long reading sessions. Particularly popular with scholars who spend hours reading continuous text.
  • Dark: Dark background with light text, suitable for low-light environments. All script renderings are tested for legibility in dark mode.
  • High Contrast: Meets WCAG AAA standards for accessibility.

To change themes, open Settings > Appearance > Theme and select your preference. Themes apply globally across all projects.

2.5 Keyboard Shortcuts#

Nisaba provides extensive keyboard shortcuts for efficient navigation and editing. All shortcuts can be viewed by pressing ? (question mark) at any time, or by opening Settings > Keyboard Shortcuts.

Navigation shortcuts:

Shortcut Action
Ctrl+Shift+P Open command palette
Ctrl+B Toggle Project Panel (left sidebar)
Ctrl+J Toggle Tool Panel (right sidebar)
Ctrl+\ Split pane vertically
Ctrl+Shift+\ Split pane horizontally
Ctrl+W Close current pane
Ctrl+Tab Cycle focus to next pane
Ctrl+G Go to reference (opens jump-to dialog)
Ctrl+F Open search in current pane
Ctrl+Shift+F Open cross-corpora search

Text interaction shortcuts:

Shortcut Action
Ctrl+Click Look up word in lexicon
Alt+Click Show morphological parse
Ctrl+Shift+A Create annotation on selected text
Ctrl+Shift+C Copy text with reference citation
Ctrl+Shift+T Toggle transliteration mode
Ctrl+Shift+I Toggle interlinear display

Vim mode:

For scholars who prefer modal editing, Nisaba supports a vim-style keybinding mode. Enable it in Settings > Keyboard Shortcuts > Mode > Vim.

In vim mode:

  • Normal mode (Esc): Navigate with h, j, k, l. Jump between verses with { and }. Jump to next/previous chapter with [[ and ]].
  • Search with / (forward) and ? (backward).
  • gd on a word opens the lexicon definition.
  • gm on a word shows the morphological parse.
  • ga opens the annotation panel for the current selection.
  • zc and zo fold and unfold apparatus entries.
  • :goto Gen 1:1 jumps to a canonical reference.
  • :search lemma:logos executes a lemma-aware search.

3.1 Browsing Available Corpora#

Nisaba integrates texts from dozens of open-access digital repositories. To browse the available corpora:

  1. Open the Corpus Browser from the navigation bar (or press Ctrl+Shift+B).
  2. The browser displays corpora grouped by tradition:
    • Ancient Near East: ETCSL (Sumerian literature), CDLI (cuneiform tablets), ORACC (annotated cuneiform)
    • Biblical & Jewish: SWORD modules (Bible translations and original language texts), Dead Sea Scrolls Digital Library, Sefaria (Talmud, Midrash, Halakha), ETCBC (morphologically analyzed Hebrew Bible)
    • Classical Greco-Roman: Perseus Digital Library, TLG, PHI Latin texts, Corpus Inscriptionum Latinarum
    • South & East Asian: SuttaCentral (Pali/Chinese/Sanskrit Buddhist texts), CBETA (Chinese Buddhist canon), SARIT (Sanskrit and Prakrit), GRETIL, Digital Corpus of Sanskrit, Chinese Text Project
    • Islamic: Quranic Arabic Corpus, classical Arabic literature collections
    • Early Christian: Patristic texts, Coptic manuscripts, Syriac corpora
  3. Select a corpus to view its contents. Texts are organized by their tradition's canonical structure (e.g., for the Hebrew Bible: Torah, Nevi'im, Ketuvim; for the Pali Canon: Vinaya Pitaka, Sutta Pitaka, Abhidhamma Pitaka).
  4. Click any text to open it in the reading area.

The simplest way to find text is a plain-text search. Open the search interface with Ctrl+Shift+F or click the search icon in the Tool Panel.

Type your query in any script. Nisaba automatically detects the writing system and searches the appropriate corpora. For example:

  • Typing בראשית searches Hebrew corpora for that word.
  • Typing logos searches all corpora with Latin-script content (Greek in transliteration, Latin, English translations).
  • Typing λόγος searches Greek corpora for that specific form.

Results appear as a list of passages with the matched term highlighted, along with the canonical reference, corpus name, and a brief context snippet.

Ancient languages are heavily inflected, meaning a single word can appear in dozens of surface forms. A search for the Greek verb form ἔλυσεν ("he loosed") would miss λύω, λύεις, ἐλύθη, λελυμένος, and hundreds of other forms from the same root.

Lemma-aware search solves this problem. Instead of searching for a specific surface form, you search by the dictionary headword (lemma), and Nisaba finds all inflected forms.

Syntax:

text
lemma:λύω

This returns every occurrence of any form of the verb λύω across all Greek corpora. The results indicate which specific inflected form was found in each passage.

You can combine lemma search with a specific corpus:

text
lemma:λύω corpus:na28

For Hebrew, lemma search uses the three-letter root system:

text
lemma:כתב

This finds all forms derived from the root k-t-b (writing), including כָּתַב, כְּתֹב, מִכְתָּב, כְּתוּבִים, and so on.

For Arabic, lemma search similarly uses root-pattern morphology:

text
lemma:كتب

When you need to find a specific grammatical form rather than all forms of a lemma, use morphology-aware search. This lets you specify morphological features alongside the lemma.

Syntax:

text
lemma:λύω morph:verb.aorist.passive.indicative.3sg

This finds only the third-person singular aorist passive indicative of λύω (i.e., ἐλύθη).

Available morphological features vary by language but follow a consistent pattern:

Greek morphological features:

text
morph:part_of_speech.tense.voice.mood.person.number
morph:noun.nominative.singular.masculine
morph:verb.present.active.participle.nominative.singular.masculine

Hebrew morphological features:

text
morph:verb.qal.perfect.3ms          # Qal perfect 3rd masculine singular
morph:verb.hiphil.imperfect.2fs     # Hiphil imperfect 2nd feminine singular
morph:noun.construct.plural         # Noun in construct state, plural

Sanskrit morphological features:

text
morph:verb.present.active.3sg       # Present active 3rd singular
morph:noun.accusative.singular      # Accusative singular

You can use wildcards for unspecified features:

text
lemma:λύω morph:verb.*.passive.*.*.*

This finds all passive forms of λύω regardless of tense, mood, person, or number.

Nisaba supports standard Boolean operators for combining search terms:

Operator Syntax Meaning
AND term1 AND term2 Both terms must appear in the passage
OR term1 OR term2 Either term may appear
NOT NOT term Term must not appear
Grouping (a OR b) AND c Parentheses control evaluation order

Proximity search finds terms that appear near each other within a specified window:

text
"logos" NEAR/5 "theos"

This finds passages where logos and theos appear within five words of each other. The proximity window is specified as a word count.

For lemma-aware proximity:

text
lemma:λόγος NEAR/5 lemma:θεός

This finds any forms of λόγος within five words of any forms of θεός.

Phrase search finds exact sequences of words:

text
"ἐν ἀρχῇ ἦν ὁ λόγος"

You can restrict searches to specific metadata fields to narrow results:

Field Syntax Meaning
corpus: corpus:lxx Search only in the Septuagint
tradition: tradition:buddhist Search Buddhist texts only
language: language:hebrew Search Hebrew-language texts
genre: genre:prophetic Search prophetic literature
date: date:300bce-100ce Search texts from this period
author: author:plato Search texts attributed to Plato
reference: reference:gen.1 Search within Genesis chapter 1

Fields can be combined with any other search operators:

text
lemma:חסד tradition:jewish genre:poetry date:1000bce-500bce

This searches for all forms of the Hebrew root ch-s-d in Jewish poetic texts dated between 1000 and 500 BCE.

3.7 Saving and Managing Searches#

Searches that you run frequently or that produce important results can be saved for future use.

  1. After running a search, click Save Search (the bookmark icon next to the search bar).
  2. Give the search a descriptive name (e.g., "Chesed in Psalms").
  3. Optionally assign it to a project.
  4. Saved searches appear in your Personal Library (Section 10) and in the search dropdown for quick access.

Saved searches are live: when new texts are added to a corpus, your saved search automatically picks up new results. You can subscribe to notifications for saved searches to be alerted when new matches appear.


4. Translation Comparison#

4.1 Loading Source Texts#

To begin a translation comparison, first load a source text:

  1. Open the Corpus Browser and navigate to the text you wish to study.
  2. Click the text to open it in the reading area.
  3. Alternatively, use the Go to Reference dialog (Ctrl+G) and type a canonical reference like Gen 1:1, John 1:1, DN 22, BG 2.47, Quran 2:255, or Iliad 1.1.

The source text opens with the original language displayed. If the text has morphological parsing data available (most major corpora do), hovering over any word displays a tooltip with the lemma, morphological parse, and a brief glossary definition.

4.2 Adding Translations#

Once a source text is loaded, you can add translations alongside it:

  1. Right-click in the reading area and select Add Translation, or use Ctrl+Shift+T.
  2. A dialog lists all available translations for the currently displayed text. For biblical texts, this may include dozens of English translations (KJV, RSV, NRSV, ESV, NIV, NASB, etc.) plus translations in other modern languages.
  3. Select one or more translations. Each opens in its own pane.
  4. Panes automatically synchronize by verse or section reference. Scrolling the source text scrolls the translations to the corresponding passage.

You can add as many translations as your screen accommodates. For intensive comparison work, a two-monitor setup is recommended, with the source text and apparatus on one screen and translations on the other.

4.3 Sentence and Word Alignment#

Nisaba provides automatic alignment between source texts and their translations at two granularity levels:

Sentence alignment:

Sentence-level alignment is computed automatically when you load a translation alongside a source text. The algorithm uses the Gale-Church statistical method supplemented by anchor points from known parallel structures (verse boundaries in biblical texts, section markers in Buddhist sutras, etc.). Aligned sentences are visually connected: clicking a sentence in the source highlights the corresponding sentence in each translation pane.

Word alignment:

Word-level alignment provides more granular correspondence. When available from the corpus data, pre-computed word alignments are displayed. For translations that lack pre-computed alignment, Nisaba offers on-demand neural alignment using transformer-based cross-lingual models fine-tuned for ancient language pairs.

To view word alignment:

  1. Select a sentence in the source text.
  2. Click Show Word Alignment in the Tool Panel (or press Ctrl+Shift+W).
  3. Colored lines connect source words to their translation equivalents.
  4. Hover over any alignment line to see confidence score and alternative alignment possibilities.

If the automatic alignment is incorrect, you can manually adjust it:

  1. Click on a misaligned word in the source.
  2. Drag to the correct word in the translation.
  3. The alignment is updated and saved to your project.

Manual alignment corrections contribute to improving the underlying models for future users (with your permission).

4.4 Viewing Interlinear Displays#

The interlinear view displays source text with morphological data and a gloss beneath each word. This is the traditional scholarly format for reading a text with grammatical analysis.

To activate interlinear display:

  1. With a source text open, press Ctrl+Shift+I or select View > Interlinear from the menu.
  2. The display changes to show each source word on its own line with the following rows beneath it:
    • Transliteration: The word in a standard romanization scheme.
    • Morphological Parse: Part of speech, stem/tense/mood/voice, person, number, gender, and other relevant categories.
    • Lemma: The dictionary headword.
    • Gloss: A brief English (or other target language) translation of the specific form.

You can toggle which rows are visible. For example, if you read Hebrew fluently and only need the morphological parse, you can hide the transliteration and gloss rows.

Reverse interlinear: This format starts with the English (or other modern language) translation text and places the source language information above each translated word. It is useful for beginning students or when presenting to audiences unfamiliar with the original language. Activate it via View > Reverse Interlinear.

4.5 Identifying Divergences#

When comparing translations, Nisaba automatically identifies and highlights passages where translations diverge from each other or from the source text.

Divergence types:

Type Description Visual Indicator
Semantic divergence Translations convey different meanings Red underline
Omission Material present in source but absent in translation Strikethrough
Addition Material present in translation but absent in source Blue highlight
Paraphrase Same meaning expressed with substantially different wording Yellow highlight
Formal vs. dynamic Different translation philosophy (literal vs. idiomatic) Dashed underline

To view divergences:

  1. With source text and at least two translations loaded, select Analysis > Show Divergences (or press Ctrl+Shift+D).
  2. Divergent passages are highlighted with the appropriate visual indicator.
  3. Click a highlighted divergence to open a detail panel showing:
    • The source text with morphological parse.
    • Each translation's rendering.
    • A divergence score (0-1 scale) quantifying the degree of difference.
    • Scholarly notes explaining the divergence (where available from commentary data).

4.6 Theological Divergence Flagging#

A distinctive feature of Nisaba is automatic detection of translation choices that reflect theological or doctrinal positions. These are cases where the original text is ambiguous and different translations resolve the ambiguity in ways that align with particular theological traditions.

Nisaba maintains a curated registry of known theological divergence points. When you view a text that contains one, a flag icon appears in the margin. Clicking the flag opens a detailed explanation including:

  • The original-language text and its range of possible meanings.
  • How different translations render the passage, grouped by theological tradition.
  • Scholarly literature discussing the translation decision.
  • Links to related passages where the same interpretive pattern appears.

Theological divergence flagging is informational, not evaluative. Nisaba does not judge which translation is "correct." It provides the evidence for scholars to form their own assessments.


5. Collation Workflow#

Textual criticism is the scholarly discipline of establishing the most authoritative text of a work by comparing all surviving manuscript witnesses. Nisaba provides a complete collation workflow from witness registration through apparatus generation.

5.1 Creating Manuscripts and Witnesses#

Before you can collate, you must register the manuscript witnesses you will compare.

  1. In your project, open the Witness Registry from the Tool Panel.
  2. Select Add Witness to register a new manuscript.
  3. Enter the witness metadata:
    • Siglum: The conventional abbreviation (e.g., "P46" for Papyrus 46, "A" for Codex Alexandrinus, "4QSam-a" for a Dead Sea Scrolls fragment).
    • Full Name: Descriptive name (e.g., "Chester Beatty Papyrus II").
    • Date: Approximate date or date range (e.g., "ca. 200 CE").
    • Provenance: Where the manuscript was found or is held (e.g., "Chester Beatty Library, Dublin").
    • Script Type: The type of handwriting (e.g., Greek uncial, Hebrew square script, Syriac Estrangela).
    • Material: Papyrus, parchment, paper, clay tablet, stone.
    • Classification: For New Testament witnesses, assign to a text family (Alexandrian, Byzantine, Western, Caesarean). For Hebrew Bible, indicate proto-Masoretic, Septuagintal, Samaritan, or Qumran type.
    • IIIF Manifest URL (optional): If the manuscript has a digital facsimile available via IIIF, provide the manifest URL. This enables side-by-side viewing of the actual manuscript images alongside the transcribed text.
  4. Enter or import the transcription of the witness. Nisaba accepts:
    • Manual transcription typed directly into the editor.
    • TEI-XML import with <rdg> and <app> elements.
    • Plain text with Leiden convention markup.
    • ATF format for cuneiform texts.

5.2 Running Automatic Collation#

Once you have registered at least two witnesses:

  1. Open the Collation Engine from the Tool Panel.
  2. Select the witnesses you wish to collate.
  3. Choose a base text (the text against which others will be compared). For biblical texts, this is commonly a standard critical edition (e.g., NA28 for the Greek New Testament, BHS for the Hebrew Bible). For other traditions, choose the most authoritative or best-preserved witness.
  4. Configure collation options:
    • Normalization: Select which orthographic differences should be treated as equivalent (e.g., itacism in Greek, matres lectionis variation in Hebrew, sandhi variation in Sanskrit). The system provides language-specific normalization presets that you can customize.
    • Fuzzy Matching Threshold: Set the sensitivity for detecting orthographic variants (0-100 scale; higher values catch more variants but may produce false positives).
    • Transposition Detection: Enable or disable detection of word-order changes.
    • Block Alignment: Enable for detecting larger structural variants (paragraph rearrangement, major additions or omissions).
  5. Select Run Collation. The engine processes the witnesses and produces a variant graph showing all points of variation.

5.3 Reviewing Variant Units#

After collation, the results are displayed in two views:

Alignment Table View:

A traditional columnar table where each column represents a witness and each row represents a variation unit. Cells contain the reading of each witness at that point. Cells where witnesses agree with the base text are empty or lightly shaded; cells with variant readings are highlighted.

Variant Graph View:

An interactive directed graph where nodes represent readings and edges represent the flow of text through each witness. Paths through the graph correspond to individual witnesses. This view is especially useful for understanding complex variation patterns with multiple overlapping variants.

To review variant units:

  1. Click on a row in the alignment table (or a node in the variant graph) to open the Variant Detail Panel.
  2. The panel shows:
    • The base text reading.
    • Each variant reading with the sigla of supporting witnesses.
    • The type of variant (automatically classified; see Section 5.4).
    • A thumbnail image of the relevant portion of each manuscript (if IIIF images are linked).
  3. You can accept or reject the automatic analysis, merge variant units, or split them if the algorithm grouped readings incorrectly.

5.4 Classifying Variants#

Nisaba automatically classifies each variant into one of the following categories:

Category Description Example
Orthographic Spelling difference with no semantic impact θεος / θεός (accent difference)
Morphological Different grammatical form, same lexeme ειπεν / ειπαν (aorist form variation)
Lexical Synonym substitution κυριος / θεος in parallel passages
Syntactic Word order change Χριστος Ιησους / Ιησους Χριστος
Semantic Meaning-affecting change Addition of "nor the Son" in Mk 13:32
Substantial Major addition, omission, or transposition of clauses Long ending of Mark (16:9-20)
Nonsense Scribal error producing a non-word Dittography, skipped lines

Each classification includes a confidence score. You can override any automatic classification.

Additionally, each variant may be tagged with a probable scribal cause:

  • Haplography: Omission due to similar adjacent text.
  • Dittography: Accidental repetition.
  • Homoioteleuton: Eye-skip due to similar line endings.
  • Homoioarcton: Eye-skip due to similar line beginnings.
  • Metathesis: Transposition of adjacent letters.
  • Itacism: Vowel confusion (common in later Greek manuscripts).
  • Harmonization: Assimilation to a parallel passage.
  • Theological alteration: Deliberate change for doctrinal reasons.

5.5 Building Stemmata#

A stemma (plural: stemmata) is a family tree of manuscripts showing their genealogical relationships. Nisaba supports multiple methods of stemmatic analysis:

Classical Lachmannian Method:

  1. Navigate to Collation > Stemmatic Analysis > Lachmannian.
  2. The system analyzes shared errors to identify conjunctive and separative errors between witnesses.
  3. An archetype is reconstructed based on the error genealogy.
  4. The resulting stemma is displayed as an interactive tree diagram.

Phylogenetic Methods:

  1. Navigate to Collation > Stemmatic Analysis > Phylogenetics.
  2. Select the algorithm:
    • Maximum Parsimony: Finds the tree requiring the fewest changes (Fitch algorithm).
    • Maximum Likelihood: Estimates the tree most likely to produce the observed data.
    • Bayesian: Produces a probability distribution over possible trees (adapted from MrBayes approaches).
    • NeighborNet: Produces a network rather than a tree, useful for detecting contamination (mixed manuscript traditions).
  3. Run the analysis and view the resulting tree or network.

CBGM (Coherence-Based Genealogical Method):

For New Testament textual criticism, Nisaba implements the CBGM as developed by the Institut fur Neutestamentliche Textforschung. This method analyzes the coherence of textual flow between witnesses.

  1. Navigate to Collation > Stemmatic Analysis > CBGM.
  2. Select the text range and witnesses.
  3. Run the coherence analysis.
  4. View the resulting textual flow diagrams and priority assessments.

All stemma visualizations are interactive. You can drag nodes, adjust the layout, and export the stemma as SVG, PNG, or in Newick/Nexus format for use with external phylogenetic software.

5.6 Generating Critical Apparatus#

The critical apparatus is the scholarly record of textual variation that accompanies a critical edition. Nisaba generates apparatus entries automatically from your collation data.

  1. Navigate to Collation > Apparatus.
  2. Select the apparatus format:
    • Positive: Lists all witnesses for each reading (used for small sets of witnesses).
    • Negative: Lists only witnesses that diverge from the base text (used for large traditions like the Greek New Testament).
    • Mixed: Combines positive and negative citation depending on the nature of the variant (Nestle-Aland style).
    • Leiden Conventions: For epigraphic and papyrological texts.
  3. Configure witness grouping and shorthand notation (e.g., "Byz" for the Byzantine majority, "it" for Old Latin witnesses collectively).
  4. Review and refine the generated apparatus entries. Each entry shows the lemma (base text reading) and variant readings with their supporting witnesses.
  5. Add scholarly judgments (e.g., marking one reading as "preferred" with a rationale).

The apparatus can be exported in TEI-XML, LaTeX (reledmac), or Nisaba's own JSON format. See Section 9 for export details.


6. Annotation and Commentary#

6.1 Creating Annotations#

Annotations are the fundamental unit of scholarly commentary in Nisaba. An annotation is a piece of text (or other content) attached to a specific passage in a source text.

To create an annotation:

  1. Select the text you wish to annotate by clicking and dragging.
  2. Press Ctrl+Shift+A or right-click and select Annotate.
  3. The Annotation Editor opens with the following fields:
    • Type: Select the annotation type (see Section 6.2).
    • Body: Write your annotation. The editor supports Markdown formatting, inline citations, and cross-references to other passages.
    • Tags: Add descriptive tags for organization and search.
    • Visibility: Choose whether this annotation is private (visible only to you), shared with project collaborators, or public.
  4. Select Save to attach the annotation to the text.

Annotations are stored using the W3C Web Annotation Data Model, ensuring interoperability with other annotation tools and long-term preservation.

Annotations are standoff: they reference the base text by position but do not modify it. This means multiple annotations can overlap on the same passage without conflict, and the base text remains untouched.

6.2 Annotation Layers#

Annotations are organized into layers. Each layer represents a distinct perspective or category of commentary. Layers can be toggled on and off independently, allowing you to focus on one type of analysis at a time.

Default annotation layers:

Layer Purpose
Textual Notes on text-critical issues (variants, readings, lacunae)
Linguistic Morphological, syntactic, and lexical observations
Translation Comments on translation choices and alternatives
Critical Historical-critical observations (source, form, redaction)
Comparative Cross-tradition parallels and concept connections
Structural Literary structure (chiasmus, inclusio, ring composition)
Pedagogical Teaching notes and simplified explanations

You can create custom layers for your project. For example, a Qumran specialist might create a "Sectarian Terminology" layer, or a classicist might create a "Meter and Prosody" layer.

To toggle layers:

  1. In the Tool Panel, open the Layers tab.
  2. Check or uncheck layers to show or hide their annotations.
  3. Each layer is displayed in a distinct color for visual clarity.

6.3 Commentary Generation Types#

When writing annotations, you can select from several scholarly commentary types, each of which provides a structured template appropriate for the discipline:

Exegetical Commentary:

Focused on the meaning and interpretation of the text. The template includes fields for: text-critical basis, grammatical analysis, word study, literary context, theological significance, and history of interpretation (Wirkungsgeschichte).

Historical-Critical Commentary:

Focused on the historical setting and composition of the text. Fields include: source analysis (J, E, D, P for Pentateuch; Q, Mark, M, L for Synoptic Gospels), form classification (Gattung), Sitz im Leben (sociological setting), redaction-critical observations, and chronological assessment.

Philological Commentary:

Focused on language and text. Fields include: morphological analysis, etymological notes, comparative Semitic/Indo-European evidence, semantic field analysis, and textual emendation proposals with supporting evidence.

Liturgical Commentary:

Focused on how texts are used in worship across traditions. Fields include: lectionary placement, liturgical season, historical usage, musical settings (if applicable), and pastoral notes.

Philosophical Commentary:

Focused on conceptual and argumentative analysis. Fields include: logical structure, key terms and definitions, philosophical context (school of thought), and relation to other philosophical texts.

6.4 Collaborative Annotation#

Nisaba supports real-time collaborative annotation within a project.

Roles and permissions:

  • Owner: Full control over the project and all annotations.
  • Editor: Can create, edit, and delete their own annotations, and edit annotations marked as collaborative.
  • Commenter: Can create annotations but cannot edit others' work. Can reply to existing annotations.
  • Viewer: Can read annotations but cannot create or modify them.

Collaborative features:

  • Threaded discussions: Any annotation can have a threaded reply chain. This supports scholarly dialogue where multiple researchers discuss a point of interpretation.
  • Revision tracking: Every edit to an annotation is versioned. You can view the history of any annotation and compare versions.
  • Conflict resolution: If two collaborators edit the same annotation simultaneously, Nisaba detects the conflict and presents both versions for manual resolution.
  • Mention system: Use @username in an annotation to notify a collaborator and draw their attention to a specific point.

7. Critical Edition Creation#

7.1 Starting a New Edition#

A critical edition in Nisaba is a formal project that produces a scholarly text with full critical apparatus.

  1. From the Project Panel, select New Project > Critical Edition.
  2. Configure the edition:
    • Title: The title of your edition (e.g., "Critical Edition of the Epistle of Barnabas").
    • Base Text: Select or import the text that will serve as the starting point. This is typically the text of the best manuscript or a previous critical edition.
    • Witnesses: Select the manuscript witnesses to include (from your Witness Registry).
    • Apparatus Format: Choose positive, negative, mixed, or Leiden.
    • Citation Style: Select the citation format for your apparatus (standard sigla, abbreviated form, etc.).
    • Target Publication: Optionally specify the series or journal (this configures export formatting).
  3. Select Create Edition to open the edition workspace.

The edition workspace provides a dedicated environment with the base text in the central pane, the apparatus below it, and a witness selector on the side.

7.2 Working with Apparatus#

The apparatus editor is the core tool for building your critical edition.

Adding apparatus entries:

  1. Select a word or phrase in the base text.
  2. Right-click and select Add Apparatus Entry.
  3. Enter the variant readings and their supporting witnesses.
  4. Classify each variant (see Section 5.4 for variant categories).
  5. Optionally add a scholarly judgment indicating which reading you consider original, with a rationale.

Editing existing entries:

Click any apparatus entry below the base text to open it for editing. You can add or remove readings, change witness attributions, or update your textual judgments.

Apparatus navigation:

  • Press Alt+Down to jump to the next apparatus entry.
  • Press Alt+Up to jump to the previous entry.
  • Entries with unresolved variants (no scholarly judgment entered) are marked with a yellow indicator.

7.3 Adding Translations#

Critical editions often include a translation alongside the established text.

  1. In the edition workspace, select Add Translation Pane.
  2. Choose an existing translation or create a new one.
  3. If creating a new translation, the editor provides a split view with the established text on the left and a text editor on the right.
  4. As you type the translation, Nisaba automatically creates sentence-level alignment with the source.
  5. You can manually adjust word-level alignment for precision.

7.4 Publishing Editions#

When your edition is complete and has passed review:

  1. Change the edition status from Draft to Review by selecting Edition > Submit for Review.
  2. Collaborators with editorial roles review the edition.
  3. After all reviews are approved, select Edition > Publish.
  4. The published edition receives a permanent identifier and becomes available in the Nisaba corpus browser.
  5. Published editions are versioned. If you later discover an error or wish to incorporate new evidence, you can create a new version while preserving the original.

7.5 Export Formats#

Published editions can be exported in the formats described in Section 9.


8. Concept Mapping#

8.1 Creating Concept Maps Across Traditions#

Concept mapping is the distinctive scholarly tool that sets Nisaba apart. It enables rigorous, evidence-based comparison of concepts across the world's philosophical and religious traditions.

To create a concept map:

  1. Navigate to Tools > Concept Mapper (or press Ctrl+Shift+M).
  2. Select New Concept Map.
  3. Enter the central concept you wish to explore (e.g., "Ineffability of the Ultimate" or "Liberation from suffering").
  4. The Concept Mapper displays a radial graph with the central concept at the center and related concepts from different traditions arranged around it.

Each concept node displays:

  • The concept name in the tradition's original language and script.
  • The tradition it belongs to.
  • A similarity rating (how closely it parallels the central concept, on a five-point scale from "strong parallel" to "loose analogy").
  • The classification of the relationship: genetic (historical influence), typological (independent parallel), analogical (structural similarity), or contested (scholarly disagreement).

Adding concepts to the map:

  1. Click the + button on the map canvas.
  2. Search for a concept by name, tradition, or keyword.
  3. Select a concept from the registry. If the concept you need does not exist, you can propose a new one.
  4. Draw a connection line between concepts to indicate a relationship.
  5. Classify the relationship type and add supporting evidence (textual references, scholarly citations).

8.2 Detecting Parallel Passages#

Nisaba includes algorithms for automatically detecting passages across traditions that may be thematically parallel.

  1. Open a text in the reading area.
  2. Select a passage of interest.
  3. Right-click and choose Find Cross-Tradition Parallels.
  4. Nisaba searches across all loaded corpora for passages with similar themes, vocabulary patterns, or narrative structures.
  5. Results are ranked by similarity score and displayed with the following information:
    • The parallel passage with its canonical reference.
    • The tradition and approximate date.
    • The type of parallel (verbatim, close, thematic, structural, or typological).
    • A confidence score.
    • Whether the parallel has been previously noted in scholarly literature.

8.3 Tracking Motif Attestations#

Motifs are recurring narrative, thematic, or symbolic elements that appear across traditions. Nisaba maintains a comprehensive motif catalog compatible with Thompson's Motif-Index of Folk-Literature and extended to cover philosophical and religious motifs.

To track a motif:

  1. Open Tools > Motif Tracker.
  2. Search for a motif (e.g., "Flood narrative" or "Descent to the underworld").
  3. The Motif Tracker displays a timeline showing every known attestation of the motif across traditions, sorted chronologically.
  4. Each attestation includes:
    • The text reference and a link to the passage.
    • The tradition and approximate date.
    • A brief description of how the motif appears in this text.
    • Scholarly commentary on the significance of this attestation.
  5. You can add new attestations that you discover in your research.

8.4 Building Influence Networks#

Influence networks visualize the documented and proposed channels through which ideas, texts, and practices moved between traditions across history.

  1. Open Tools > Influence Network.
  2. Select the traditions you wish to include (e.g., Zoroastrian, Jewish, Christian, Islamic).
  3. The network displays as a directed graph where:
    • Nodes represent traditions, schools of thought, or individual texts.
    • Edges represent channels of influence, graded by evidence quality: documented (explicit citation), strong (scholarly consensus), probable (majority view), possible (debated), or speculative (proposed but weakly supported).
    • Edge thickness corresponds to the volume of documented influence.
    • Hovering over an edge displays the specific evidence supporting the influence claim.
  4. You can filter the network by time period, geographic region, or evidence quality.

8.5 Synoptic Views#

The synoptic view places thematically parallel passages from multiple traditions side by side for direct comparison.

  1. Open Tools > Synoptic Reader.
  2. Select a comparison set (e.g., "Creation narratives," "Golden Rule formulations," "Meditation instructions across traditions").
  3. The synoptic view displays the passages in parallel columns, one per tradition.
  4. Corresponding elements are visually aligned across columns.
  5. An annotation layer specific to the synoptic view allows you to note parallels, differences, and scholarly observations.

You can create custom comparison sets by selecting passages from different traditions and grouping them under a descriptive title.


9. Export Options#

9.1 PDF Export with Critical Apparatus#

Nisaba generates publication-quality PDFs with properly formatted critical apparatus.

  1. Navigate to Export > PDF.
  2. Configure the export:
    • Page size: A4, US Letter, or custom dimensions.
    • Margins: Top, bottom, left, right (with wider inner margin for bound volumes).
    • Font selection: Choose fonts for the main text, apparatus, and each script that appears.
    • Apparatus placement: Footnote (below text on same page), endnote (at end of section), or inline (embedded in text).
    • Line numbering: Enable line numbers in the margin for the source text.
    • Headers and footers: Include canonical references, page numbers, and a running title.
  3. Select Generate PDF. The system produces a typographically correct document suitable for submission to scholarly publishers.

9.2 DOCX for Journal Submission#

For submission to journals that require Microsoft Word format:

  1. Navigate to Export > DOCX.
  2. Select a journal template. Nisaba includes pre-configured templates for major journals:
    • Journal of Biblical Literature (JBL)
    • New Testament Studies (NTS)
    • Vetus Testamentum (VT)
    • Journal of the American Oriental Society (JAOS)
    • Harvard Theological Review (HTR)
    • Bulletin of the School of Oriental and African Studies (BSOAS)
    • Indo-Iranian Journal
  3. The export applies the journal's required formatting (margins, font sizes, heading styles, citation format, apparatus layout).
  4. Critical apparatus is formatted as footnotes or endnotes per the journal's convention.
  5. Hebrew, Greek, and other scripts are embedded with appropriate fonts.

9.3 LaTeX with reledmac for Critical Editions#

For scholars who work with LaTeX, Nisaba exports full LaTeX source files using the reledmac package (the standard for typesetting critical editions in LaTeX).

  1. Navigate to Export > LaTeX.
  2. Configure the export:
    • Document class: book, article, or a publisher-specific class.
    • reledmac options: Number of apparatus levels (up to five), apparatus format (paragraph, block, or column), line numbering interval.
    • Polyglossia/Babel configuration: Automatically configured based on the scripts in your edition.
    • Font configuration (for XeLaTeX/LuaLaTeX): Maps to your preferred system fonts for each script.
  3. Select Generate LaTeX. The output includes:
    • A main .tex file with the established text and apparatus entries.
    • A preamble file with all necessary package configurations.
    • Font mapping files if custom fonts are specified.
    • A Makefile for compiling the document.

The generated LaTeX compiles correctly with XeLaTeX or LuaLaTeX without manual intervention.

9.4 HTML Standalone#

For web-based distribution of your edition or analysis:

  1. Navigate to Export > HTML.
  2. Configure the export:
    • Self-contained: All fonts, styles, and scripts embedded in a single HTML file.
    • Static site: A folder of HTML, CSS, and JavaScript files suitable for hosting on any web server.
    • Interactive apparatus: Whether the apparatus should be clickable with manuscript image popups.
  3. The HTML export produces a responsive, accessible page that works in all modern browsers and correctly renders all ancient scripts.

9.5 Citation Styles#

Nisaba generates bibliographic citations for texts and editions in all major academic citation formats:

  • SBL (Society of Biblical Literature): The standard for biblical and ancient Near Eastern studies.
  • Chicago/Turabian: Notes-bibliography and author-date styles.
  • MLA: For humanities publications.
  • APA: For social science contexts.
  • Harvard: Author-date style common in British scholarship.
  • DIN 1505: German academic standard.
  • Custom: You can define your own citation template.

To copy a citation:

  1. Right-click on any text passage.
  2. Select Copy Citation.
  3. Choose the citation format.
  4. The citation is copied to your clipboard, formatted according to the selected style.

9.6 Export Templates#

If you regularly export in a specific configuration, you can save your export settings as a template:

  1. Configure an export as described above.
  2. Before generating, select Save as Template.
  3. Name the template (e.g., "JBL Submission" or "Personal Study PDF").
  4. The template appears in the export dialog for future use.

10. Personal Library#

10.1 Uploading Documents#

Your Personal Library is a private collection of texts, notes, and references within Nisaba.

To upload a document:

  1. Open Library from the navigation bar.
  2. Select Upload.
  3. Choose a file from your computer. Supported formats include:
    • TEI-XML: Full text with markup, including apparatus and annotations.
    • USFM/USX: Bible text in United Bible Societies standard format.
    • Plain text: UTF-8 encoded text in any language.
    • PDF: The text is extracted for search and annotation (original PDF is preserved for viewing).
    • EPUB: Electronic publication format.
    • OSIS: Open Scripture Information Standard XML.
    • ATF: ASCII Transliteration Format for cuneiform texts.
  4. After upload, Nisaba processes the document:
    • Language detection and script identification.
    • Automatic tokenization and (where possible) morphological analysis.
    • Indexing for search.
  5. The document appears in your library and can be opened in the reading area, annotated, and included in projects.

10.2 Organizing Collections#

Collections are folders for organizing your library materials.

  • Create collections by selecting Library > New Collection and providing a name and optional description.
  • Drag documents into collections, or right-click a document and select Move to Collection.
  • Collections can be nested (sub-collections within collections) for hierarchical organization.
  • Tag documents with custom labels for cross-cutting organization (e.g., a document can be in the "Qumran Studies" collection and also tagged with "Eschatology" and "Dualism").

Smart collections are dynamically populated based on criteria you define:

  1. Select Library > New Smart Collection.
  2. Define the criteria (e.g., "all documents in Hebrew dated before 200 BCE" or "all documents tagged 'Christology'").
  3. The smart collection automatically includes any library item matching the criteria, including future additions.

10.3 Reading Lists and Progress#

Reading lists help you plan and track your research reading.

  1. Select Library > New Reading List.
  2. Add documents or specific text passages to the list.
  3. For each item, Nisaba tracks your reading progress:
    • Unread: You have not opened this item.
    • In Progress: You have opened it and read part of it (the system tracks your last position).
    • Completed: You have scrolled through the entire text.
    • Reviewed: You have marked it as reviewed (a manual action indicating you have engaged with the content sufficiently for your purposes).
  4. The reading list displays a progress bar showing your overall completion.

10.4 Bookmarks and Highlights#

As you read texts in Nisaba, you can create bookmarks and highlights for quick reference.

Bookmarks:

  • Click the bookmark icon in the margin next to any passage, or press Ctrl+Shift+K with the cursor on a line.
  • The bookmark saves the canonical reference (e.g., nisaba://bible/ps/23:1) along with an optional note.
  • All bookmarks are listed in Library > Bookmarks, organized by text and date created.
  • Click a bookmark to jump directly to the passage.

Highlights:

  • Select text and press Ctrl+Shift+H to highlight it.
  • Choose a highlight color (six colors available, each customizable with a label, e.g., "Key vocabulary" = yellow, "Textual problem" = red, "Cross-reference" = blue).
  • Highlights are visible whenever you view the text and appear in Library > Highlights as a collected list.
  • Highlights can be exported as a summary document listing all highlighted passages with their notes and colors.

Citation manager integration:

Nisaba integrates with major citation managers for exporting references:

  • Zotero: Direct export via the Zotero Connector browser extension. Select any text or edition and click the Zotero icon to add it to your Zotero library with full metadata.
  • Mendeley: Export references in RIS format for import into Mendeley.
  • BibTeX: Export individual references or bulk-export your entire library in BibTeX format for use with LaTeX.
  • EndNote: Export in ENW or RIS format.

Appendix A: Canonical Reference URI Scheme#

Nisaba uses a canonical URI scheme to identify any passage in any tradition unambiguously:

text
nisaba://tradition/work/reference

Examples:

URI Passage
nisaba://bible/gen/1:1 Genesis 1:1
nisaba://bible/john/1:1-18 John 1:1-18
nisaba://quran/2:255 Quran, Surah 2 (Al-Baqarah), Ayah 255
nisaba://pali/dn/22 Digha Nikaya, Sutta 22
nisaba://gita/2/47 Bhagavad Gita, Chapter 2, Verse 47
nisaba://talmud/berakhot/6a Talmud Bavli, Berakhot 6a
nisaba://greek/plato/rep/514a Plato, Republic 514a (Stephanus)
nisaba://latin/vergil/aen/1.1 Vergil, Aeneid, Book 1, Line 1
nisaba://rigveda/1/1/1 Rigveda, Mandala 1, Sukta 1, Mantra 1
nisaba://daodejing/1 Daodejing, Chapter 1
nisaba://avesta/yasna/28/1 Avesta, Yasna 28, Stanza 1

The URI scheme is compatible with the Canonical Text Services (CTS) protocol used by the Perseus Digital Library and other digital humanities infrastructure.


Appendix B: Supported Languages and Writing Systems#

The following table lists all writing systems supported by Nisaba, with the level of morphological analysis available for each:

Writing System Script Direction Morphological Analysis Lexicon Integration
Biblical Hebrew RTL Full paradigm BDB, HALOT
Aramaic (Imperial) RTL Full paradigm CAL, HALOT
Aramaic (Syriac) RTL Full paradigm Payne Smith
Arabic (Classical) RTL Full root-pattern Lane, Wehr
Ancient Greek LTR Full paradigm LSJ, BDAG
Latin (Classical) LTR Full paradigm Lewis & Short
Sanskrit LTR Full sandhi + compound Monier-Williams
Pali LTR Full paradigm PTS Dictionary
Classical Chinese TTB/LTR Segmentation CTP Dictionary
Coptic (Sahidic) LTR Full paradigm Crum
Coptic (Bohairic) LTR Full paradigm Crum
Ge'ez (Ethiopic) LTR Full paradigm Leslau
Sumerian LTR Sign-level + glossing ePSD2
Akkadian LTR Full paradigm CAD
Ugaritic LTR Root-based DUL
Hittite LTR Basic paradigm CHD
Avestan RTL Basic paradigm Bartholomae
Old Persian LTR Basic paradigm Kent
Tibetan LTR Syllable-level Jaschke
Old Church Slavonic LTR Basic paradigm SJS
Egyptian Hieroglyphic RTL/LTR Sign-level Faulkner
Egyptian Hieratic RTL Sign-level Faulkner
Demotic RTL Basic CDD
Linear B LTR Syllable-level Ventris-Chadwick
Phoenician RTL Basic DNWSI
Samaritan RTL Basic paradigm Tal

Appendix C: Keyboard Shortcut Reference#

Global Shortcuts#

Shortcut Action
? Show keyboard shortcut help
Ctrl+Shift+P Open command palette
Ctrl+Shift+F Open cross-corpora search
Ctrl+Shift+B Open corpus browser
Ctrl+G Go to reference
Ctrl+B Toggle Project Panel
Ctrl+J Toggle Tool Panel
Ctrl+S Save current work
Ctrl+Z Undo
Ctrl+Shift+Z Redo

Reading Area Shortcuts#

Shortcut Action
Ctrl+\ Split pane vertically
Ctrl+Shift+\ Split pane horizontally
Ctrl+W Close current pane
Ctrl+Tab Cycle focus to next pane
Ctrl+Shift+Tab Cycle focus to previous pane
Ctrl+Click Look up word in lexicon
Alt+Click Show morphological parse
Ctrl+Shift+I Toggle interlinear display
Ctrl+Shift+T Toggle transliteration
Ctrl+Shift+D Show divergences
Ctrl+Shift+W Show word alignment

Annotation Shortcuts#

Shortcut Action
Ctrl+Shift+A Create annotation
Ctrl+Shift+H Highlight selected text
Ctrl+Shift+K Create bookmark
Ctrl+Shift+C Copy text with citation

Apparatus Shortcuts#

Shortcut Action
Alt+Down Jump to next apparatus entry
Alt+Up Jump to previous apparatus entry
Alt+Enter Open apparatus entry for editing
Alt+A Add apparatus entry for selection

Vim Mode Shortcuts#

Key Sequence Action
h / j / k / l Move cursor left/down/up/right
{ / } Jump to previous/next verse
[[ / ]] Jump to previous/next chapter
gd Open lexicon definition for word
gm Show morphological parse for word
ga Open annotation for selection
zc / zo Fold/unfold apparatus entries
/ Forward search
? Backward search
n / N Next/previous search result
:goto REF Jump to canonical reference
:search QUERY Execute search query
:export FORMAT Export current text

Appendix D: Glossary#

Apparatus (Critical Apparatus): A systematic record of textual variants found across manuscript witnesses, presented alongside the established text in a critical edition.

Collation: The process of comparing multiple manuscript witnesses of a text to identify variant readings.

Hapax Legomenon: A word that occurs only once in a given corpus.

Interlinear: A display format in which morphological information, glosses, and transliteration appear on separate lines beneath (or above) the source text.

Lemma (pl. Lemmata): The canonical or dictionary form of a word, used as a headword in lexica and as the basis for lemma-aware search.

Leiden Conventions: A standardized system for indicating the state of ancient texts in transcription (e.g., brackets for lacunae, dots for uncertain readings).

Morphological Analysis: The parsing of a word into its component parts (root, prefix, suffix, inflectional ending) and the identification of its grammatical properties (person, number, gender, tense, mood, voice, case).

Pericope: A self-contained passage or unit within a larger text, typically used in biblical studies.

Siglum (pl. Sigla): A conventional symbol (usually a letter or number) used to refer to a specific manuscript witness in textual criticism.

Standoff Annotation: An annotation system where the annotations are stored separately from the base text and reference it by position, allowing multiple overlapping annotation layers without modifying the source.

Stemma (pl. Stemmata): A diagram representing the genealogical relationships among manuscript witnesses, analogous to a family tree.

TEI-XML: The Text Encoding Initiative's XML schema for representing texts in digital form, widely used in digital humanities.

Transliteration: The representation of text from one writing system using the characters of another, following a defined convention (e.g., representing Hebrew letters with Latin characters according to SBL transliteration standards).

Variant (Textual Variant): A reading found in one or more manuscript witnesses that differs from the reading in other witnesses or in the base text.

Witness: A manuscript or other textual source that preserves a copy of a text. In textual criticism, different witnesses are compared to reconstruct the original text.


Getting Help#

If you encounter issues or have questions:

  • In-app help: Press ? at any time for context-sensitive help.
  • Documentation: The full Nisaba documentation is available at the help center accessible from the navigation bar.
  • Community forum: Join the Nisaba Scholars Forum to ask questions, share research, and connect with other users.
  • Bug reports: Report technical issues through Help > Report a Problem.
  • Feature requests: Suggest new features through Help > Request a Feature.

Nisaba: Named for the Sumerian goddess of writing, learning, and scribal arts. The divine scribe whose temple was the first library.