--- title: "Playbooks: Certifying Enriched Assets" url: "https://atlan.com/demos/certifying-enriched-assets-playbooks/" description: "Automate data trust with Atlan's playbooks, certifying enriched assets weekly and ensuring users always understand the data's reliability." format: "Video" video: "https://videos.ctfassets.net/nwa1c00rtgxb/4CQKPCDoGnzAqvnhIhvR1K/ba7c692581207f8b19b543dd975f8ca5/Certifying_Enriched_Assets.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: Certifying Enriched Assets Transcript of the video at https://atlan.com/demos/certifying-enriched-assets-playbooks/ Certifying enriched assets [00:00] If you certify your assets and Atland based on enrichment standards. Such as having at least a description owner and tag on an asset, this can be automated through playbooks in two different ways. The first is directly updating the certification through the use of filters on metadata attributes. The second is adding a score to assets through the metadata completeness score custom package in certifying those with a score above the threshold you set. Let's take a look at both these ways. For this, we're looking to certify any asset that has a description, ownership and term linked to it, or has a score over 70 for the metadata completeness score. We've already set up our scoring parameters on the custom package. So our assets have a score associated with them. We click on the governance icon on the left-hand navigation to be taking the governance section and then click on playbooks to open the playbooks page. Clicking on the create new brings the playbook creation pop-up. Since we are adding certification to assets [01:00] based upon enrichment, We name it. Certification updates for enrichment dash weekly. As we want this update to run on a weekly basis, keeping our certification up to date. Clicking create opens the playbooks creation page. For a rule, we enter verifying assets for our first filter. We want to ensure that we do not attempt to update any already verified assets for the attribute we select certification for the operator we select is not and select verified as the value. Next we create a new filter group. As we have two different conditions that we want the selection to match on for the first filter, we add an attribute of our custom metadata field score. We select greater than for the operator in enter the value of 70 so that we select those assets with a high enough score to certify. Since our other selection criteria for update are actually a set of a few filters. We [02:00] create another filter group so that we can require all of the conditions to be met. For the first filter, we add an attribute of description from the properties dropdown for the operator we select is not empty. We add another filter in this time, select owner as the attribute. And again, select is not empty. Finally, we add a filter for the attribute of link terms and den select is not empty. We have now created our selection, grouping finding assets with a description, at least one link term, and at least one owner for this filter grouping, we leave the matching criteria as match all since an asset needs to match all of these items. However for the parent filter group, we update the matching criteria to match any, as we want to select either those with a score above 70 or those that have all of the other criteria. We now have set our filters to properly find the right assets along with keeping those that are already updated [03:00] with a verified certification from selection. Keeping our processing time down Our matching assets update and we click on the view all to verify everything looks perfect for our rule, we select certificate as the action for the operator. We leave this as update and for the value we select verified, our playbook is done and ready to be scheduled. Now, if we wanted to take this a step further, we could add additional rules to find instances where a score has gone down from 70 or no longer contains the required enrichment, but it's still verified. We can set this to automatically update the certification to draft or no certification in those situations. The great thing with playbooks is that you can build multiple complex rules to cover all the actions you want. Clicking on next takes us to the scheduling page. Here we update the recurrence to weekly and select Sunday in 13. As we know that our workflows for connectors run until around eight and no other playbooks are running at this [04:00] time. We click complete and our playbook is now set to run weekly. With this playbook, we are keeping our instance updated with verified assets signaling to their users that they can trust in fully understand the data assets before they use them.