The dashboard team is going to be relying on the morpheme-mapping file so that ClearEngine can utilize the existing verse-based trees while the rest of the Dashboard can rely on the active work happening in the lowfat trees.
While looking at the aforementioned mapping file, I noticed the following issues:
The attribute that represents the current lowfat identifiers seems to be called n. Conversely, I expected to find an id or xml:id attribute which represents the lowfat trees in main.
The values that represent the current lowfat identifiers seem to be out of date. They do not have the leading o character and I did not see an instances where trailing hebrew consonants are included for handling the implied article.
There also may be other issues that were not obvious to me.
The dashboard team is going to be relying on the morpheme-mapping file so that ClearEngine can utilize the existing verse-based trees while the rest of the Dashboard can rely on the active work happening in the lowfat trees.
While looking at the aforementioned mapping file, I noticed the following issues:
n
. Conversely, I expected to find anid
orxml:id
attribute which represents the lowfat trees inmain
.o
character and I did not see an instances where trailing hebrew consonants are included for handling the implied article.There also may be other issues that were not obvious to me.