Refactor ebible.py to simplify the tracking of translations through the system and to create more complete metadata. · Issue #62 · BibleNLP/ebible · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The translations.csv file from eBible.org contains a lot of data about each translation.
Can we consider updating the Translation class to store all that data about the translation. In addition to that we can add the missing metadata that we create - i.e. the final filename of the corpus file and the information extracted from the licence files copr.html.
This way all the metadata about each translation is in one place and that should facilitate the creation of a single metadata.parquet file that includes licencing information.
The text was updated successfully, but these errors were encountered:
The translations.csv file from eBible.org contains a lot of data about each translation.
Can we consider updating the Translation class to store all that data about the translation. In addition to that we can add the missing metadata that we create - i.e. the final filename of the corpus file and the information extracted from the licence files copr.html.
This way all the metadata about each translation is in one place and that should facilitate the creation of a single metadata.parquet file that includes licencing information.
The text was updated successfully, but these errors were encountered: