The README described a pink node and a double-click; the code drew a green node and opened its detail view on a single click. I found that mismatch while looking through ClinLine’s RWD Lineage Tool. The repository already contained a runnable example, so I focused my contribution on making its instructions match what was there.
The tool draws how datasets and variables are connected through mapping and transformation steps. Its input is an example Excel workbook describing those relationships, rather than patient records for the tool to transform. The arrows visualize mapping metadata; they do not establish that the transformations were executed.
Documenting the example already in the repository
I added the Python dependency-installation and Lineage1.py launch steps to the README. I also stated that the script reads LineageExcel/Mapping_MIMIC_DM_v05_lim.xlsx relative to the repository root, so the starting directory is explicit. The overview instructions now describe green mapping nodes, blue datasets and the single-click action implemented by the code.
I corrected the descriptions of the dataset boxes, join symbols and transformation boxes in the detail view as well. The Parkinson use-case section still described files as forthcoming, so I linked the mock protocol, example mapping workbook and DM Define document already present. The PR changes only the README; it adds no data-processing or visualization implementation.
What I checked
I ran Lineage1.py with the included workbook using a noninteractive Matplotlib backend and confirmed that the process exited successfully. That checks the example’s execution path, rather than a full set of on-screen click interactions. I submitted the changes and this verification scope in PR #2 on 23 September 2026. As of 28 September, the PR remained open and had not been merged.