EPATADA
EPATADA copied to clipboard
User-specified column name as function input
For functions that only rely on one or two columns, we should explore the possibility of making the column name an input, such that someone can jump into the TADA process with their own dataset/headers for data tidying/organization/visualization. Conversely, we could have a sort of schema cross-walk table with all columns required to run functions and column names the user specifies from their unique dataset. They could save this schema for future use/TADA runs as well.