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
In #130 and #131, we declare our intention to modify the Bohairic Bible text.
In #123, we defined our data/ directory conventions.
Regarding directory names:
We should read all data under data/raw/, since these will be displayed as is.
We will probably only read the Bohairic from data/input/ because that is the only language that we are interested in editing at the moment.
Since, for languages other than Bohairic, the data under data/raw/ and data/input/ will likely remain identical, then they should be deleted from input/ to avoid confusion, and simply read from raw/. An input/ copy should be created only if we have an intention to edit the data, otherwise it would cause confusion.
Regarding format:
To facilitate this editing, we should probably take the input from a TSV that synchronizes with a Google Sheet. JSON is not particularly user-friendly. If you can edit the text in a website or a more user-friendly UI, that would be even better. But since that's not feasible in the time being, let's just do a TSV and a Google Sheet, as we did with the Crum appendices ([Crum] Non-media Content (including Appendices) should Be Viewable in a Single GSheet #78).
The text was updated successfully, but these errors were encountered:
This essentially reverts 72c791f and
5714157.
We no longer intend to use JSON as the input (as opposed to raw) format.
To make the pipeline simpler, we will use TSV for input.
We also don't intend to edit all languages. We will only edit Bohairic.
This will make it possible to keep the data private. The current setup,
which uses `curl`, forces us to make the data public.
Retrieve `JSON_KEYFILE_NAME` from the environment variables.
In #130 and #131, we declare our intention to modify the Bohairic Bible text.
In #123, we defined our
data/
directory conventions.Regarding directory names:
data/raw/
, since these will be displayed as is.data/input/
because that is the only language that we are interested in editing at the moment.data/raw/
anddata/input/
will likely remain identical, then they should be deleted frominput/
to avoid confusion, and simply read fromraw/
. Aninput/
copy should be created only if we have an intention to edit the data, otherwise it would cause confusion.Regarding format:
The text was updated successfully, but these errors were encountered: