<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: notebooks naming convention in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/notebooks-naming-convention/m-p/54882#M30186</link>
    <description>&lt;P&gt;It is recommended to name notebooks descriptively so that it is easy to understand their purpose and content. A good practice is to follow a consistent naming convention to help keep notebooks organized. These are some of general practices&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Use naming conventions that describe the notebook's function and contents. This can include the project name, dataset used, task name or category.&lt;/LI&gt;
&lt;LI&gt;Use dashes (-) or underscores (_) instead of spaces when separating words in the notebook name.&lt;/LI&gt;
&lt;LI&gt;Begin each notebook name with a prefix representing the notebook type or project name to easily identify related notebooks.&lt;/LI&gt;
&lt;LI&gt;Keep notebook names concise and limit them to 30 characters or less to ensure the name is fully visible in the Databricks workspace.&lt;/LI&gt;
&lt;LI&gt;Avoid special characters or symbols in notebook names.&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Thu, 07 Dec 2023 19:03:34 GMT</pubDate>
    <dc:creator>Rajeev45</dc:creator>
    <dc:date>2023-12-07T19:03:34Z</dc:date>
    <item>
      <title>notebooks naming convention</title>
      <link>https://community.databricks.com/t5/data-engineering/notebooks-naming-convention/m-p/54713#M30158</link>
      <description>&lt;P&gt;I have read info about objects names but are there any best practices regarding notebooks naming convention?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2023 08:25:31 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/notebooks-naming-convention/m-p/54713#M30158</guid>
      <dc:creator>ElaPG</dc:creator>
      <dc:date>2023-12-06T08:25:31Z</dc:date>
    </item>
    <item>
      <title>Re: notebooks naming convention</title>
      <link>https://community.databricks.com/t5/data-engineering/notebooks-naming-convention/m-p/54882#M30186</link>
      <description>&lt;P&gt;It is recommended to name notebooks descriptively so that it is easy to understand their purpose and content. A good practice is to follow a consistent naming convention to help keep notebooks organized. These are some of general practices&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Use naming conventions that describe the notebook's function and contents. This can include the project name, dataset used, task name or category.&lt;/LI&gt;
&lt;LI&gt;Use dashes (-) or underscores (_) instead of spaces when separating words in the notebook name.&lt;/LI&gt;
&lt;LI&gt;Begin each notebook name with a prefix representing the notebook type or project name to easily identify related notebooks.&lt;/LI&gt;
&lt;LI&gt;Keep notebook names concise and limit them to 30 characters or less to ensure the name is fully visible in the Databricks workspace.&lt;/LI&gt;
&lt;LI&gt;Avoid special characters or symbols in notebook names.&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Thu, 07 Dec 2023 19:03:34 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/notebooks-naming-convention/m-p/54882#M30186</guid>
      <dc:creator>Rajeev45</dc:creator>
      <dc:date>2023-12-07T19:03:34Z</dc:date>
    </item>
  </channel>
</rss>

