Unlocked Greek Lexicon Documentation

This site contains the official documentation for Door43’s Unlocked Greek Lexicon content creation.

Contents:

Note

In this documentation, the term View mode (sometimes called markdown mode) refers to what is visible from the Door43 access to a specific .md file. When moving to the Edit mode, all lines of the file are visible to support editing. Using the Preview button will, temporarily, take you to View mode, to verify the displayed contents of your edits. The convention of enclosing data descriptions within curly brackets has been used for the discussion below.

Assignments

  1. An Issue will be created for each letter of the alphabet and assigned to the individual responsible for editing all of the lemmas for that letter.
  2. To access individual lemma files, DO NOT open the contents folder. This has over 6000 folders within it, one per Strong’s Plus ID, and will take considerable time to open. Instead open the ugltoc.md file in the templates folder for a list of the TOC files for each letter, or open the letter’s TOC file: templates/{Greek letter}toc.md, e.g. templates/alphatoc.md. In ugltoc.md, three columns exist for each letter with links to the associated lemma files: “Instances” for words sorted by their instance count, “Word Sort” for words sorted by their Strong’s Plus ID, and “Undefined” for the lemmas that are assigned a temporary, undefined Strong’s Plus ID. For example, for the letter Alpha, the “Instances” file is named alphainsttoc.md, the “Word Sort” file is named alphatoc.md, and the “Undefined” file is named alphaundeftoc.md.

Each letter’s toc file lists all of its lemmas across and then down, showing both the Greek word and the Strong’s Plus ID. At the top of the file are links to the UGL toc file and to the “Undefined {Greek letter}” toc file, e.g. templates/alphaundeftoc.md. The latter of these also appears at the bottom of the file, along with a link back to the top of the file. For each letter there are a number of lemmas from the A-S lexicon and its parsing that did not have a Strong’s ID, had multiple Strong’s IDs, or had a letter appended to the Strong’s ID. These were arbitrarily assigned a Strong’s Plus ID greater than G99000. As editor for a letter, part of your responsibility is to identify (and possibly create) the Strong’s Plus ID (5 digits long) for each of these. That data, plus any others needed to complete the lemma file, should be entered and the file “committed”. You should then follow the steps for Creating a New Lemma file.

Note

The Strong’s Plus ID referenced above was initially developed by Alan Bunning, where he took the 4-digit Strong’s ID and appended a zero to create a 5-digit ID. This gave him extra IDs to be able to qualify different word forms than the standard Strong’s. We will be using this Strong’s Plus identification for this project.

Markdown

  1. All field markers (1 or more #-signs or an asterisk) and their associated data are required for each entity file, unless noted as Optional.
  2. Consecutive lines are merged together for View mode. A blank line is required before AND after each field marker line. Enter a blank line between any 2 lines that you enter, if you want them to appear on separate lines.
  3. Any line that starts with an Exclamation mark is considered a comment and IS visible in View mode.
  4. Any data that appears within “<!—“ and “–>” is considered a comment and IS NOT visible in View mode. This has been used for the two “tag” lines discussed below.
  5. The two lines shown below are “tag” lines, which must not be removed. For the 1st of these the valid Stage 2 Status values are “NeedsEdits”, “NeedsReview”, “NeedsFinalCheck”, and “ReadyforPub”. Each file was created with “NeedsEdits”. When your edits are complete, you should change the Status to “NeedsReview”. You should also list the lexica that you used for your edits on the 2nd “tag” line. (A list of values to enter for each lexicon source will be provided separately)

<!– Status: S2=NeedsEdits –>

<!– Lexica used for edits: {list of lexica} –>

Note

There is no blank line between these in the 01.md files, since these are non-displayed lines. There should be a blank line before and after this pair.

  1. References to other Greek lemmas should be entered in the format: [{Greek word}](../{Strong’s Plus ID}/01.md), e.g. [ἀγαπάω](../G00250/01.md). This is a little cumbersome to enter each time, but we are awaiting some Door43 tooling which will allow us to abbreviate the format. When the Door43 tooling is developed, we will write a script which will replace all of the long format with the abbreviated format, and notify you of this new format for future edits. There were many instances where the A-S lexicon and its processing did not provide a Strong’s ID for a word. This is indicated in the files with no characters between the parenthesis. Please update these, from your other sources.
  2. References to Hebrew lemmas should be entered in the form: [{Hebrew word}](//en-uhl/{Strong’s ID}), e.g. [טָהֳרָה](//en-uhl/H2893). Since that lexicon does not currently exist, following a Hebrew link will currently result in a 404 error, Page Not Found. Note that the Hebrew uses the standard 4-digit Strong’s ID.
  3. Citation references should be in the format: [{Standard form}]({USFM Form}), with each reference separated by a semicolon where:
  • Standard form: {Book name} {chapter}:{verse}, or an abbreviated form for references in the same book or same chapter
  • USFM form: {USFM Book name} {chapter}:{verse}, supplying all 3 pieces for every instance. See the USFM Formal Markers page for the list of USFM Book names.
  • Example: [I Co 7:11](1Co 7:11); [8:3](1Co 8:3); [7](1Co 8:7)

Creating a New Lemma file

A new lemma file can be created from an existing lemma file by following the steps below:

  1. Move to the existing lemma file in Door43.
  2. Mentally remember the new Strong’s Plus ID.
  3. Click the “Raw” option icon.
  4. Select every line and then use the Copy feature (pull-down menu or Ctrl-C).
  5. Click the Browser Back icon.
  6. Click the Files tab and then the contents tab (this will take a while).
  7. Click the Blue “New File” button.
  8. Paste the contents of the previous file into the area below “<> New File”.
  9. In the blank field to the right of “en-ugl / content / ” enter the new Strong’s Plus ID, followed by “/01.md”, e.g. “G45555/01.md” and click Commit Changes.
  10. It will take approximately 1 day for this new lemma file to appear in the letter’s toc file, and for the old undefined ID to be removed from the letter’s undefined toc.