---
title: "Playbooks: Applying Descriptions"
url: "https://atlan.com/demos/applying-descriptions-playbooks/"
description: "Automate manual data updates with Atlan playbooks, saving tons of time and ensuring consistent, up-to-date descriptions across your data warehouse."
format: "Video"
video: "https://videos.ctfassets.net/nwa1c00rtgxb/0pnWDtpXsodDVPjoFTfly/84abeca449457f7b214e83dcf510b89c/Applying_descriptions.mp4"
content_purpose: ["Product Overview"]
target_persona: ["Data Steward"]
journey_stage: ["S2 - Discovery", "C1 - Onboarding", "C3 - Adoption"]
use_case_context: ["Training"]
product: ["Context For AI - Automation"]
content_type: "video transcript"
transcript_source: "contentful"
---

# Playbooks: Applying Descriptions

Transcript of the video at https://atlan.com/demos/applying-descriptions-playbooks/

<!-- Body: machine transcript stored on the Contentful entry (field contentBody), timestamps kept, product names corrected. Not yet edited by a person. -->

Applying descriptions

[00:00]

For many repeated column names inside a data warehouse represent the exact same data, whether that is the first name, last name or order ID. Since they represent the exact same data, their description is usually the exact same to. Instead of having to update each and every instance of these manually playbooks allows you to automate the process, saving tons of manual work and keeping those descriptions up to date.

Whenever new assets come in. Cookie on the governance icon on the left hand, navigation and clicking on playbooks takes us to the playbooks page. Clicking on the create new button brings the playbooks creation. Pop-up. In this case, we want to add a specific description to all our columns, with the name of order ID.

So we entered description update for order ID dash weekly. For the name we click on create in the playbooks creation page opens. Since we were only updating a single description, we enter the name of the playbook as the name of the rule. For [01:00] filters, we add our first with the attribute type of asset type. Operator of is one of, and we select column. Since we were only looking to update the descriptions in our Stoweflake warehouse.

We add a second filter with the attribute of connector. Is one of as the operator and choose snowflake. Next we add a third filter with the attribute of name from the properties options, select equals as the operator, as we want an exact match and enter in the value of our column name, order ID. Finally, we can limit the update in two ways, depending on our choice we could limit so that we ensure that any column with this name in snowflake, that already has the exact description we are going to update them to is not selected for processing by creating a new filter. Going to the properties option in selecting description as the attribute, and then select not equal for the operator. And enter in the description for the value. Or if you wanted to just make sure that those [02:00] that did not already have a value are updated. We can put the operator of is empty. In this case, we will select is empty. Our asset matches update and by clicking on view, all. We're able to validate that only order ID columns are shown. Everything looks perfect.

We go to the actions in select description as the action type, the only option for the operators update. So that is kept and we enter the description that we want. All of our order ID columns to be updated to. We clicked next to take us to the scheduling page. Here we update the recurrence to weekly and select Sunday. We select 11 as we know that not only do our workflows for connectors and by eight, but we also do not have any other playbooks running at this time. We click complete and our playbook is saved and scheduled. We have now ensured that not only will all our descriptions for order ID be updated on the first run of this playbook, where they have not yet been enriched. But if new instances of the column are created in snowflake and not [03:00] enriched, they will be automatically enriched using this playbook.