eis1600 0.9.1

EIS1600 project tools and utilities

EIS1600 Tools

• Workflow
• Process
• Installation
• Set Up
• Working Directory Structure
• Usage
  • convert_mARkdown_to_EIS1600TMP
  • insert_uids
  • update_uids
  • disassemble_into_miu_files
  • reassble-from-miu_files
  • annotate_mius
  • onomastic_annotation
  • miu_random_revision
  • yml_to_json

Workflow

(so that we do not forget again...)

1. Double-check text in the Google Spreadsheet; “tag” is as “double-checked” (Column PREPARED);

• These double-checked files have been converted to *.EIS1600 format

2. The names of these files are then collected into AUTOREPORT.md under DOUBLE-CHECKED Files (XX) - ready for MIU.
3. Running disassemble_into_mius takes the list from AUTOREPORT.md and disassembles these files into MIUs and stores them in the MIU repo.

Process

1. Convert from mARkdown to EIS1600TMP with convert_mARkdown_to_EIS1600
2. Check the .EIS1600TMP
3. Run insert_uids on the checked .EIS1600TMP
4. Check again. If anything was changed in the EIS1600 file, run update_uids
5. After double-check, the file can be disassembled by disassemble_into_miu_files <uri_of_that_file>.EIS1600

Installation

After creating and activating the eis16000_env (see Set Up), use:

$ pip install eis1600

In case you have an older version installed, use:

$ pip install --upgrade eis1600

Set Up Virtual Environment and Install the EIS1600 PKG there

To not mess with other python installations, we recommend installing the package in a virual environment. To create a new virtual environment with python, run:

python3 -m venv eis1600_env

NB: while creating your new virtual environment, you must use Python 3.7 or 3.8, as these are version required by CAMeL-Tools.

After creation of the environment it can be activated by:

source eis1600_env/bin/activate

The environment is now activated and the eis1600 package can be installed into that environment with pip:

$ pip install eis1600

This command installs all dependencies as well, so you should see lots of other libraries being installed. If you do not, you must have used a wrong version of Python while creating your virtual environment.

You can now use the commands listed in this README.

To use the environment, you have to activate it for every session, by:

source eis1600_env/bin/activate

After successful activation, your user has the pre-text (eis1600_env).

Probably, you want to create an alias for the source command in your alias file by adding the following line:

alias eis="source eis1600_env/bin/activate"

Alias files:

• on Linux:
  • ~.bash_aliases
• On Mac:
  • .zshrc if you use zsh (default in the latest versions Mac OS);

Structure of the working directory

The working directory is always the main EIS1600 directory which is a parent to all the different repositories. The EIS1600 directory has the following structure:

|
|---| eis_env
|---| EIS1600_MIUs
|---| gazetteers
|---| Master_Chronicle
|---| OpenITI_EIS1600_Texts
|---| Training_Data

Path variables are in the module eis1600/helper/repo.

Usage

Convert mARkdown to EIS1600 files

Converts mARkdown file to EIS1600TMP (without inserting UIDs). The .EIS1600TMP file will be created next to the .mARkdown file (you can insert .inProcess or .completed files as well). This command can be run from anywhere within the text repo - use auto complete (tab) to get the correct path to the file. Alternative: open command line from the folder which contains the file which shall be converted.

$ convert_mARkdown_to_EIS1600TMP <uri>.mARkdown

EIS1600TMP files do not contain UIDs yet, to insert UIDs run insert_uids on the .EIS1600TMP file. This command can be run from anywhere within the text repo - use auto complete (tab) to get the correct path to the file.

$ insert_uids <uri>.EIS1600TMP

Batch processing of mARkdown files

Use the -e option to process all files from the EIS1600 repo.

$ convert_mARkdown_to_EIS1600 -e <EIS1600_repo>
$ insert_uids -e <EIS1600_repo>

To process all mARkdown files in a directory, give an input AND an output directory. Resulting .EIS1600TMP files are stored in the output directory.

$ convert_mARkdown_to_EIS1600 <input_dir> <output_dir>
$ insert_uids <input_dir> <output_dir>

Disassembling

Disassemble files into individual MIU files. Run from the parent directory EIS1600, this will disassemble all files from the AUTOREPORT.

$ disassemble_into_miu_files

Can also be run from anywhere within the EIS1600_MIUs/ directory with a single files as input. E.G.:

$ disassemble_into_miu_files <uri_of_the_text>.EIS1600

Reassembling

Run inside MIU repo. Reassemble files into the TEXT repo, therefore, TEXT repo has to be next to MIU repo.

$ reassemble_from_miu_files <uri>.IDs

Use the -e option to process all files from the MIU repo. Must be run from the root of MIU repo.

$ reassemble_from_miu_files -e <MIU_repo>

Annotation

NER annotation for persons, toponyms, misc, and also dates, beginning and ending of onomastic information (NASAB), and onomastics.

To annotate all MIU files of a text give the IDs file as argument. Can be used with -p option to run in parallel.

$ annotate_mius <uri>.IDs

To annotate an individual MIU file, give MIU file as argument.

$ annotate_mius <uri>/MIUs/<uri>.<UID>.EIS1600

If no input is given, annotation is run for the whole repository. Can be used with -p option for parallelization. Run from the parent directory EIS1600 (internally used path starts with: OpenITI_EIS1600_MIUs/).

$ annotate_mius -p

Only Onomastic Annotation

Only for test purposes! Can be run with -D to process one file at a time, otherwise runs in parallel. Can be run with -T to use gold-standard data as input. Run from the parent directory EIS1600.

$ onomastic_annotation

MIU revision

Run the following command from the root of the MIU repo to revise automated annotated files:

$ miu_random_revisions

When first run, the file file_picker.yml is added to the root of the MIU repository. Make sure to specify your operating system and to set your initials and the path/command to/for Kate in this YAML file.

system: ... # options: mac, lin, win;
reviewer: eis1600researcher # change this to your name;
path_to_kate: kate # add absolute path to Kate on your machine; or a working alias (kate should already work)

Optional, you can specify a path from where to open files - e.g. if you only want to open training-data, set:

miu_main_path: ./training_data/

When revising files, remember to change

reviewed    : NOT REVIEWED

to

reviewed    : REVIEWED

Collect YAMLHeaders into JSON

Run from the parent directory EIS1600:

$ yml_to_json