Skip to main content
Workforce LibreTexts

1.16: Local Files

  • Page ID
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    Learning Outcomes

    • Discuss proper file management techniques for local files

    File management includes folder structures and naming conventions, plus the choice of appropriate formats. Before we begin our discussion, take a moment to think about how you name files that you create.

    With regards to folder structures, a good way to go about organizing your data is to create a hierarchy of folders. As an example, you could use a folder for each project, with two subfolders:

    • “Data,” to store your research data, including images, databases, media, etc.
    • “Documentation,” to store all relevant project documents, including, e.g. methodology and consent forms.

    The more complex the project, the more detailed your folder structure can be. If you are working alone or in a small team, you might wish to use just a handful of subfolders. However, if you work on a large project you could create a range of subfolders to suit the team’s needs. As an example, under “Data,” you might create a subfolder for each data type, such as “Databases,” “Images,” and “Sounds.” Similarly, under “Documentation” you might create a subfolder for each category of document, such as “Methodology,” “Consent forms,” and “Information sheets.”

    When it comes to file naming, we recommend using simple but meaningful names. Best practice includes the following:

    • Capital letters should be used to delimit words in the place of spaces or underscores
    • File names and paths should avoid unnecessary repetition and redundancy
    • Numbers should always include at least two digits (i.e. 01 to 09 instead of 1 to 9)

    Naming will follow a convention chosen by you and other project members. For instance, you may decide that “InterviewTra07JD20180214” means “Interview Transcript 7, written by John Doe, on 14/02/2018.” You will need to describe such conventions as part of your study metadata.

    Finally, choosing appropriate file formats is key to ensuring data is reusable, as some formats become obsolete in time and may make your research inaccessible. You can use whatever software or format is convenient during your work, but when sharing the data you should follow best practice and ensure future reusability of your work. The US Library of Congress maintains a recommended formats statement , which we invite you to consult. This lists a series of file formats in order of preference by output type, including recommended metadata fields.

    When saving data for sharing, you might need to convert your working files. If you do so, always ensure that the conversion was successful and that no errors appear (e.g. missing values, wrong characters, text formatting, resolution, etc.).

    Contributors and Attributions

    CC licensed content, Original
    • Local Files. Authored by: Robert Danielson. Provided by: Lumen Learning. License: CC BY: Attribution
    • Practice Questions. Authored by: Sherri Pendleton. Provided by: Lumen Learning. License: CC BY: Attribution
    CC licensed content, Shared previously

    1.16: Local Files is shared under a not declared license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?