0% found this document useful (0 votes)
19 views

Learning Log - Review File Structure and Naming Conventions

This document provides guidance on creating an effective file structure and naming conventions for projects. It recommends (1) establishing conventions early, aligning with your team, and using meaningful, short filenames. Best practices include formatting dates as YYYYMMDD and using hyphens, underscores, or capital letters. The reflection questions ask about why organization is important for data analysts, how to structure folders and files, and appealing naming convention choices.

Uploaded by

Javi Vega
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views

Learning Log - Review File Structure and Naming Conventions

This document provides guidance on creating an effective file structure and naming conventions for projects. It recommends (1) establishing conventions early, aligning with your team, and using meaningful, short filenames. Best practices include formatting dates as YYYYMMDD and using hyphens, underscores, or capital letters. The reflection questions ask about why organization is important for data analysts, how to structure folders and files, and appealing naming convention choices.

Uploaded by

Javi Vega
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

____________________________________________________________________________________

Learning Log: Review file structure and naming conventions


Instructions
You can use this document as a template for the learning log activity: Consider how data analysts approach tasks.
Type your answers in this document, and save it on your computer or Google Drive.

We recommend that you save every learning log in one folder and include a date in the file name to help you stay
organized. Important information like course number, title, and activity name are already included. After you
finish your learning log entry, you can come back and reread your responses later to understand how your
opinions on different topics may have changed throughout the courses.

To review detailed instructions on how to complete this activity, please return to Coursera: Learning Log: Review
file structure and naming conventions.

Date: <enter Course/topic: Course 3: Prepare Data for Exploration


date>
Learning Log: Review file structure and naming conventions

Review best When creating a file structure and naming convention pattern for a project, you should
practices always:

● Work out your conventions early in your project. The earlier you start, the more
organized you’ll be.
● Align file naming conventions with your team. Conventions are most useful when
everyone follows them.
● Make sure filenames are meaningful. Stick to a consistent pattern that contains the
most useful information needed.
● Keep file names short and to the point.

Remember, there are some stylistic choices you’ll need to make when it comes to filename
conventions. However, there are still best practices you should follow here, too:

Formatt Exampl
ing e
Convent
ion

Format SalesRep
Dates as ort20201
‘yyyym 125
mdd’

Lead SalesRep
revision ort20201
numbers 125v02
with 0

Classification : Internal
____________________________________________________________________________________
_

Use SalesRep
hyphens, ort_2020
undersco _11_25_
res, or v02
capitaliz
ed letters

Reflection: Write 2-3 sentences (40-60 words) responding to each of the questions about file
structuring and naming conventions below:

Questions and
responses: ● Why are file structure and naming conventions so important? What are the
consequences of poor organization for data analysts at work?
Align file naming conventions with your team. Conventions are most useful when
everyone follows them.
Make sure filenames are meaningful. Stick to a consistent pattern that contains the
most useful information needed.

● How would you structure folders and files? What naming conventions would you
use?
Date, following the proper order, naming the version each one use,

● What appeals to you about these choices?


It makes sense to me, there is a need to have a proper order related to the store of
the files.

Classification : Internal

You might also like