As of now, the loading data page uses explicit filepaths. This will be the way that the large majority of our walk-ins load in data, and, as least for me, running with it seems to be the path of least resistance.
Maybe it's worth it to try and be more principled about this, though? The here package addresses the issues of having to change file paths every time we hand scripts around, and is definitely current best practice. It might not make sense for our workflows in the mLab to be based around RStudio projects, though, which is what the here package is all about. A bit of outline here (pun intended). :-)
As of now, the loading data page uses explicit filepaths. This will be the way that the large majority of our walk-ins load in data, and, as least for me, running with it seems to be the path of least resistance.
Maybe it's worth it to try and be more principled about this, though? The
here
package addresses the issues of having to change file paths every time we hand scripts around, and is definitely current best practice. It might not make sense for our workflows in the mLab to be based around RStudio projects, though, which is what thehere
package is all about. A bit of outline here (pun intended). :-)What do yall think?