I'm developing a host of transformation scripts in Python, and I've been successful so far getting a couple examples to function. However, now I would like to be able to access more input variables, shall I say metadata, that I'm also storing in the parent LabKey Project folder as a List. I can access what is in the runProperties.tsv file, but I don't think this or the paths within will get me where I need to go.

What I'd like to do is validate naming conventions of incoming data columns against a directory of valid names within the transformation script. (Of course I could just use the Assay design itself to validate against during the import process, but I need to actually do this within the transformation script for my application.) I had initially thought of storing this directory in a text file next to the transformation script or also creating a list/set/dictionary object directly in the script. However, placing this data as a transparent and easily accessible LabKey List (or some other type of LK object) is most desirable.

Is there a preferred method of accessing LK Assay/List/DataClass tables from a transformation script? I could try using the LK API tools, but I'd like to avoid additional outside module import/usage within the script, and also avoid needing user credentials within the script, if there is a more direct method.

Thanks!