Skip to main content

A toolkit for accessing and working with data from the CRITT Translation Process Research Database (TPR-DB).

Project description

tprdb-utilities

PyPI version Python License: MIT

A Python toolkit for downloading and reading data tables from the CRITT Translation Process Research Database (TPR-DB).

Three functions cover the full workflow:

Function What it does
fetch_TPRDB_tables Downloads study tables from the CRITT API and saves them to a local directory structure
read_TPRDB_tables Reads those tables from a local clone into a single pandas.DataFrame
prep_parallel_texts Builds segment-aligned bitext and tritext DataFrames ready for MT evaluation
recompute_pause_based_metrics Recomputes typing-burst metrics (TB, TG, TD) for a custom pause threshold and appends them to an SG DataFrame

Installation

# pip
pip install tprdb-utilities

# uv
uv add tprdb-utilities

# poetry
poetry add tprdb-utilities

Quick Start

1 — Download data (fetcher)

Public study (no credentials needed):

from tprdb_utilities import fetch_TPRDB_tables

fetch_TPRDB_tables(
    path="/path/to/local/data",
    studies=["DG21"],
    extensions=["ss", "st"],
    public=True,
)

Private study (requires your TPR-DB username and API token):

from tprdb_utilities import fetch_TPRDB_tables

fetch_TPRDB_tables(
    path="/path/to/local/data",
    studies=["MYSTUDY"],
    extensions=["st"],
    public=False,
    username="myTPRDBusername",   # case-sensitive, must match your account
    token="my-api-token",
)

After downloading, the function always prints a summary like this:

DG21 [ss]: Done fetching (^_^)
DG21 [st]: Done fetching (^_^)

=== fetch_TPRDB_tables Summary ===
StudyID  : DG21
Clone dir: /path/to/local/data/tprdb-mothership-clone
User dir : PUBLIC

Extension  Status            Time
---------  ----------------  ------
ss         Downloaded        1.23s
st         Downloaded        0.98s

To read these files with read_TPRDB_tables:
  path      = "/path/to/local/data/tprdb-mothership-clone"
  user      = "PUBLIC"
  studies   = ["DG21"]

Copy those argument values directly into read_TPRDB_tables.

Subsequent calls are bandwidth-efficient. When files for an extension are already present, fetch_TPRDB_tables sends the X-Client-Tables-Timestamp header (sourced from the studySummary.xml bundled with the study). The server returns 304 Not Modified when nothing has changed, so no data is transferred. The timestamp is read once per study, before the first request, so all conditional requests in the same call are checked against the state of your clone as it was before the call. The summary will reflect the outcome:

Extension  Status            Time
---------  ----------------  ------
ss         Up to date (304)  0.21s
st         Updated           1.05s

Stale clones are re-synced automatically. If a response reveals that the server data for a study is newer than your local clone (the study's tables were regenerated on the server), every extension already present locally for that study is re-downloaded — even extensions you did not request in that call. This guarantees that all table files in the clone stay in step with the study's studySummary.xml, and therefore with the data on the server. Re-downloaded extensions appear in the summary as Auto-updated:

Extension  Status             Time
---------  -----------------  ------
ss         Updated            1.05s
kd         Auto-updated.      2.31s

2 — Read data (reader)

Use the path and user values printed by fetch_TPRDB_tables at the end of its summary output.

Public study (user="PUBLIC"):

from tprdb_utilities import read_TPRDB_tables

df = read_TPRDB_tables(
    studies=["DG21", "AR22"],
    extension="st",
    path="/path/to/local/data/tprdb-mothership-clone",
    user="PUBLIC",
)

Private study (user="<your TPR-DB username>"):

from tprdb_utilities import read_TPRDB_tables

df = read_TPRDB_tables(
    studies=["MYSTUDY"],
    extension="st",
    path="/path/to/local/data/tprdb-mothership-clone",
    user="USER_DIRECTORY_NAME",
)

3 — Transform data (transformer)

Once you have the SG, ST, and TT tables loaded, prep_parallel_texts aligns translation segments across participants and builds parallel-text DataFrames suitable for automatic MT evaluation with tools like BLEU or COMET.

from tprdb_utilities import read_TPRDB_tables, prep_parallel_texts

path = "/path/to/local/data/tprdb-mothership-clone"

sg = read_TPRDB_tables(["RUC17"], "sg", path)
st = read_TPRDB_tables(["RUC17"], "st", path)
tt = read_TPRDB_tables(["RUC17"], "tt", path)

parallel_texts = prep_parallel_texts(sg, st, tt)

The return value is a dictionary. Keys follow two patterns:

Key pattern Contains
"ST_{part}" Bitext — source text + one participant's translations
"ST_{p1}_{p2}" Tritext — source text + two participants' translations
# Bitext: source text aligned with P01's translations
parallel_texts["ST_P01"]
# Study  Task  Text  STseg  String_ST                   String_P01
# RUC17  P     4     1      Developing countries are …  发展中国家不愿 …
# …

# Tritext: source text aligned with P01's and P02's translations
parallel_texts["ST_P01_P02"]
# Study  Task  Text  STseg  String_ST                   String_P01       String_P02
# RUC17  P     4     1      Developing countries are …  发展中国家不愿 …  虽然我们可以 …
# …

# Extract just the text columns for evaluation
bitext = parallel_texts["ST_P01"][["String_ST", "String_P01"]]
tritext = parallel_texts["ST_P01_P02"][["String_ST", "String_P01", "String_P02"]]

By default both bitexts and tritexts are produced. To generate only one kind:

# Bitexts only
parallel_texts = prep_parallel_texts(sg, st, tt, prep_tritexts=False)

# Tritexts only
parallel_texts = prep_parallel_texts(sg, st, tt, prep_bitexts=False)

Tritext DataFrames contain only source segments that both participants translated (inner join on study, task, text, and segment number). Merged segments that could not be split are included in bitexts (with the component source strings concatenated) but excluded from tritexts.


4 — Recompute pause-based metrics (transformer)

SG tables already include typing-burst metrics computed at the standard 1000 ms pause threshold (TB1000, TG1000, TD1000). Use recompute_pause_based_metrics to compute the same three metrics at any other threshold and append them as new columns.

from tprdb_utilities import read_TPRDB_tables, recompute_pause_based_metrics

path = "/path/to/local/data/tprdb-mothership-clone"

sg = read_TPRDB_tables(["BML12"], "sg", path)
kd = read_TPRDB_tables(["BML12"], "kd", path)

sg_500 = recompute_pause_based_metrics(sg, kd, threshold=500)

This appends three new columns to the returned DataFrame:

Column Description
TB500 Number of typing bursts per segment
TG500 Total inter-burst pause time (ms) per segment
TD500 Total active typing duration (ms) per segment

The column names reflect the threshold you pass in, so threshold=250 would add TB250, TG250, and TD250. Calling with threshold=1000 raises a ValueError since those columns are already in the table.

If you call the function a second time with the same threshold, the existing columns are silently replaced (the call is idempotent).


Directory Structure

fetch_TPRDB_tables creates the following layout under path:

<path>/
└── tprdb-mothership-clone/
    ├── PUBLIC/                  ← public studies
    │   └── <StudyID>/
    │       ├── studySummary.xml
    │       └── Tables/
    │           ├── session1.st
    │           └── ...
    └── <username>/             ← private studies
        └── <StudyID>/
            ├── studySummary.xml
            └── Tables/
                ├── session1.st
                └── ...

Each zip response bundles a studySummary.xml file alongside the table files. fetch_TPRDB_tables places it in the <StudyID>/ directory (one level above Tables/) and uses it on subsequent calls to detect whether the server data has changed. When it has, all locally present extensions for the study are re-downloaded so every table file matches the new studySummary.xml.

read_TPRDB_tables expects this exact layout, so the two functions are designed to work together seamlessly.


Supported Table Extensions

ag, au, ex, fd, fu, hc, hs, kd, ku, pu, sg, ss, st, tt

License

MIT — see LICENSE.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

tprdb_utilities-0.8.0.tar.gz (18.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

tprdb_utilities-0.8.0-py3-none-any.whl (22.3 kB view details)

Uploaded Python 3

File details

Details for the file tprdb_utilities-0.8.0.tar.gz.

File metadata

  • Download URL: tprdb_utilities-0.8.0.tar.gz
  • Upload date:
  • Size: 18.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.5

File hashes

Hashes for tprdb_utilities-0.8.0.tar.gz
Algorithm Hash digest
SHA256 0797edf311c40c1b5321ae40cc0ca11908c9235c2426f3ff58a2e1cee10c4b93
MD5 fe0f95b86d16aa5451d203d30f540f36
BLAKE2b-256 ae6f66c3ea770637f76538a11fc634b035fe84a91dfb0eab236601750a2e37e1

See more details on using hashes here.

File details

Details for the file tprdb_utilities-0.8.0-py3-none-any.whl.

File metadata

File hashes

Hashes for tprdb_utilities-0.8.0-py3-none-any.whl
Algorithm Hash digest
SHA256 57058d307b4397279239283ff25f29f43917b644cabb54be97e47214dc7df02b
MD5 0626cbd86b12b4b2b67b30d2507e169f
BLAKE2b-256 ba989fc3a62827c1f758a67cc0cd8946c79192181475a9f2b6de237a1e96c838

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page