Metadata - Adobe Experience Manager Asset Series

Let’s get started. I’m pleased to introduce our presenters for today. Bridget Roman, Senior Product Marketing Manager, AEM Assets, and Elise Han, Principal Consultant, Content Strategy and Architecture. Bridget, you now have the floor. Great, thank you so much Anu, and welcome everyone. We’re so happy to have you here, whether it’s morning, afternoon, or evening, where you are. I think we’re going to make the most of this next hour together, and we really are excited to see so many people here participating in our Skill Builder series for AEM Assets. You probably are aware of this, but you’re at the second of five webinars, and last week we covered folder structure and search. So hopefully many of you were able to attend that. Sharon Bull and I presented there, and it was a really great deep dive on how to set up your folder structure for success. Obviously today we’ll be diving into metadata, and I was excited to see your responses in the poll. Oops, sorry about that. Looks like there are a lot of folks on the line who really kind of want to take their metadata strategy to a place where it’s more mature. A lot of you answered that your strategy does not exist, or maybe there’s tribal knowledge, which to us basically means, you’re sort of talking over your shoulder. In the old days when you used to sit near people, talking over your shoulder, and giving each other tips on metadata. So Elise is going to dive into a lot of topics today to help take your low or moderate metadata strategy to a place that’s much more mature. So we’ll get into that momentarily. And then I just want to do a plug for the next three sessions. If you are interested in really becoming a more astute DAMM practitioner, you won’t want to miss next week. We’re going to get into Brand Portal. This is, if you’re not familiar with it, Rajeev’s going to take us through this, but it’s our out of the box offering around creating a portal to be able to deliver basically completed assets out to agencies, partners, even internal constituents. But great session around that asset distribution theory. And then after that, on March 2nd, we will have Joe Pearl, who is one of our resident experts on dynamic media. Talk us through what dynamic media is in case you’re not familiar with it. It is an add on to AEM assets, and it’s really a tool that automates the output of your assets for all channels and screens. And then the last in the five of our webinars is all about Adobe AssetLink. This is our native connection to Creative Cloud. And Greg Klebus, who’s the product manager for this capability, he is the resident expert. He’s going to take us through how the dam can actually appear in a window from Photoshop, Illustrator, InDesign, and most recently Adobe XD. So if you haven’t signed up, please do so. Each of these sessions you can sign up individually for. So I wanna just put a plug in to make sure you’re signing up for all of them. Because I think with this portfolio of these five different topics, your skills and abilities around dam enablement will definitely go up. It’s worth noting, we will be sharing a recording of this session and all the sessions as the weeks go on. So if you are registered, which if you’re here today, you obviously are. If you have colleagues who have registered and maybe they’re not able to attend, you’ll all be receiving a recording of this session, a PDF of the deck that we share, and the links to the various resources that we’re providing. So if you look into the resource pod, you’ll see links out to some important things relevant to the topic we’re going to cover today. So with that, speaking of topics, here are kind of the five key things we’re going to dive into today. We’re going to define what metadata is, talk about the different types of metadata. We’ll get into namespaces and AEM, how to customize metadata forms, and then metadata automation. And so I think we’ll get lots of your questions answered just as we go through the content. And if you have additional questions, be sure to put in the Q&A pod. We will address them as we go along or at the end, depending on how things go. So with that, I’m going to hand it over to Elise and let her take the wheel and start driving this presentation. And then we’ll regroup at the end. Well, hello everybody. My name is Elise Han, and hopefully you can hear me and see my screen. Sound good, Elise. Are you all set? Yep, slides are up, ready to go. Okay, perfect. Slides are up and they don’t have the little navigation panel to left, correct? Full screen, good to go. Yes. Okay, lovely. So my name is Elise Han, principal content strategist, and I primarily work in technical content strategy. So what’s happening in the backend as opposed to editorial or brand strategy, it’s all about how systems are actually designed and incorporating your content. So we’re going to focus on metadata today. Metadata is a very loaded word, similar to content or governance. It means all different things to a just array of people. So we’re going to run through some of the foundational concepts within AEM. And I’m also going to touch on several things that are a bit more advanced, that if you have anybody to reach out to, that you work with from Adobe, they’ll run through it with you, or they may be actually related to sessions that are going to happen within this series. We’re going to start with just defining metadata. Metadata is data about data. It’s almost a very boring definition in that it’s so all encompassing, but that’s what it is. If we have a file, if we have a content fragment, if we have any content that is actually coming into our system, we need additional attributes and properties that describe it for findability or for workflows or for other functionality within the system. The big thing to note is that if you don’t actually apply metadata to your files, to your pages, they sometimes just get lost in the ether because nobody can find them. Sure, we have full text search, but typically your metadata strategy is going to be focused on controlled vocabularies, different properties that you can get from various systems. And pretty much if you think about filters, think about how important filters and certain terminology are when you’re trying to locate anything. And that’s your metadata. So it actually becomes just as important as the content itself, because without the content just it’s produced and then it goes off and you’re never actually able to locate it or reuse it again. So it becomes a Kleenex as opposed to something reusable. So the types of metadata, this is very standard and there’s actually different classifications for it. You have descriptive metadata, which is what is it about? How are you actually giving it nomenclature? They may be internal terms or external terms, but it’s something that’s being added for humanistic understanding. There’s administrative metadata, which is very much workflow based or about explorations, where it’s allowed to be used. It’s how you can leverage the content. Technical metadata is the size, the type of file it is, the different attributes that are pulled out about maybe versioning upstream in Photoshop or the color profiles that are embedded. It’s technical. You shouldn’t be overriding it. It’s part of the file. It’s inherent to that content. And the last thing that you have is process metadata, which is really about your own business process. So you can have all different workflow steps, all different types of attributes that are associated to the content and assets in order to actually show where it’s going in a life cycle, who is involved in it, all of those different pieces, aside from just the administrative pieces. So administrative oftentimes is outside of your organization. What are you allowed to do with it? Where are you going to have legal ramifications? And process is much more related to what happens internally as something is going through approval processes and actually being authenticated. These four classifications can absolutely change. There’s a million different blogs that use all different terminology, but these are the ways that you can at least approach your metadata strategy and start thinking about what you can capture. And again, these are not definitive categorizations. They’re a good start. So the next thing that we go into is metadata standards. This is something that is so overlooked when people are developing an organizational and enterprise level strategy. There is a whole world out there that is full of systems that all puts data into their files, like so many different embedded metadata properties. And in order for these systems to talk to each other, they use the same metadata standards. That means that a Microsoft Word file, which I will show you, uses the same standard called Dublin Core, so it’s the second one on this list, to capture its title, its keywords, and things like that. The whole reason that there are metadata standards is because all these systems, like Adobe, is gonna function differently than your standard Office applications. But if we use the same metadata standard, then all of a sudden things that you put in the file upstream, Adobe Experience Manager can actually extract and understand. So when you’re looking at what metadata to use, it’s very important that you look at what standards exist that are gonna accomplish what you’re trying to do. Otherwise, it’s really reinventing the wheel. So we’ll dig into this just a little bit. Here are four big standards that are pretty much adopted all over the place. Dublin Core as well as IPTC, IPTC being the last one. IPTC is very much photo-related, so this is where you’re capturing things like the photographer and the models and different things related to a photo shoot. These are universally adopted standards, and I highly suggest that if you’re figuring out a strategy, look at these and figure out what could you potentially capture in the content life cycle, so further upstream when activities are taking place, that when you upload a file into AEM, AEM just automatically pulls out that metadata. We all know the burden of responsibility for adding metadata upon upload. Binks is such, it is so many different things that you have to add, and it involves so much oversight. So if you can start to scale it all out, that’s gonna be better in the long run. So we’re gonna get into this a little bit and just know every single one of these has a prefix. I only say that because I’m gonna show you it. The next thing that we wanna know about is what are the taxonomies in play and what are the schemas? Just like how metadata or content or governance or all these other things are loaded terms, taxonomy also means different things to different people. Within this context, we’re actually referring to a metadata taxonomy, which is the metadata values, so a controlled vocabulary list or valid values or enumeration, something that is a set number of inputs where people are not free forming entries, and it can actually be a hierarchy. So think about the ways that you would classify fruit or vegetables or the origin of species. So all of those are taxonomies. This is not the same as taxonomies that were referred to and discussed in the first call with Sharon, where it was all about folder taxonomies. So I just wanted to differentiate. When we’re doing taxonomies, it’s progressive disclosure. So when you’re thinking about a metadata hierarchy, whatever the parent is that you’re tagging something with, all the child entries are also gonna be tagged with that parent. So your taxonomies for metadata need to be understood across the organization. They need to have a natural progression in terms of hierarchies, and then they’re usually going to be your opportunities to start capturing things outside of the metadata standards that are used over several industries. So what we just talked about with Dublin Core and IPTC, they’re not gonna use the same hierarchy, and that’s gonna be something that you can start really leveraging in AEM in order to classify your content. So as we’re going through this, the ways that you really wanna think about defining a metadata strategy. What are your taxonomies? What are those controlled vocabularies? It doesn’t have to be a hierarchy. It doesn’t have to be progressive disclosure. If you just have a flat list of terms, like say you have content types or audiences, like a target audience, and you get your organization to agree on those terms. If you get people to agree on how to classify things from a lifecycle perspective, it can be a dropdown, but it can be so impactful for finding content that you can’t really see. So what are your taxonomies? They don’t have to be a hierarchy. They just need to be universally understood and applied. And when you start to do freeform text, it’s basically the difference between having a filter and having a Twitter hashtag. One is just grouping things together based on how people are entering stuff. The other is a systematic entry into the organization. The next thing, step two, is about adding additional namespaces. So when we think about IPTC or Dublin Core, they have their own prefix on how properties are stored. That sounds really foreign. Put those metadata properties upstream into things like Bridge and XD, and you have the opportunity to really collect things further upstream. So number two, I totally realized you need a visualization. Three is about adjusting your metadata forms. When you’re exposing information about an asset, about an image to people, you want it to be meaningful. You don’t want to expose everything under the sun because it turns into noise. And AEM gives you the ability to alter the different schema forms without deleting information behind the scenes. All it is is a UI representation. So we’re gonna dig into that. And then the last piece is how are you automating things based on your folder hierarchy, which was last week. Totally suggest people revisit that session if you weren’t able to attend. But how are you actually automating metadata application? Because when you upload an asset into a particular folder hierarchy, you can automate the metadata that’s applied. So figure out your organizational vocabulary, figure out what you’re collecting, start capturing your own enterprise level metadata under a specific namespace. We’re gonna get to that. And make sure you’re conscientious of the user experience. I think that everybody probably on this call has been exposed to when too much is asked and you don’t really know how to prioritize your input. And so that’s something within AEM where you can absolutely determine what’s displayed to users. So going into control vocabularies and dropdowns versus tags, as I said, control vocabulary, it’s the predefined list. It’s a predefined set of values. It’s not accounting for all of the different variations or internal jargon that may take place. This is something where you’re asking somebody to select something. And so there’s two different types of control vocabularies in AEM. You have tags, which by the way, AEM loves a tag because tags are used not just within assets, they’re used everywhere. You can use them on pages, you can use them in campaign. These are hierarchies and values that can be used to aggregate pieces of content. And the best way to think of them is ways of associating dissimilar pieces of information or dissimilar pieces of content. Maybe they have the same theme. Maybe if you’re in finance, they’re talking about 529 planning. There could be so many different things that you introduce in tags that can be applied across the board within AEM. The thing about tags is that you need them to be inclusive. And what I mean by that is that is progressively disclosing something. If you decided that you have a set of tags that are location-based, and I have North America as the region, and then I have the United States as the country, anything that I tag with the United States is automatically tagged with North America. So if you’re trying to actually do something that’s showing exclusivity, meaning this content should only be displayed in the United States, it should not be displayed in all of North America. That’s not a use case for tags. So when you’re going through these things, make sure that even if it’s in a quick and dirty Excel sheet, figure out what the properties are, and then actually write out a definition of what it’s capturing. And that’s gonna actually let you decide, do you use a dropdown? Do you use a tag? Because there can be conditional formatting, not conditional formatting, sorry guys, cascading rules for dropdowns, meaning you select this value so only these values are available to you. Tags, on the other hand, inclusive. So this is a very important slide. I don’t know if people are gonna take screenshots or maybe mark the minute, but this is something that you should go back to if you’re trying to figure out which type of property to capture things as, because both are exceedingly valuable, both can drive a whole lot of functionality. They can be applied through metadata profiles, they can be leveraged in workflows, but they’re different. It’s not to say one is great, one is not, they just have different levels of functionality. So we spoke very briefly about IPTC and Devlin Core and a bunch of the different industry-wide metadata standards. You have the ability to actually register your own namespace. So when I say namespace, everything in AEM is stored as a quote unquote node. And dot this down, there are so many help X documents about it. But basically if you think about a giant parent-child folder structure, that’s what’s behind the scenes in AEM. And there’s a lot of different metadata properties that are each stored separately against a different property name. So like the title is one property on one node, and then you have keywords on another. And majority of those are actually using industry standards. They’re using Devlin Core, they’re using IPTC, they’re using XMP. But what happens when you have something that’s completely unique to your organization? The great thing about AEM is that you can actually go in and register your own namespace. And by that, basically, I mean an abbreviation. Like if I said Experience League, it’s gonna be my namespace. It could be EL. And then every property would have a prefix of EL. So when you think about that, it’s not a big deal from your user experience on the front end. It’s not a big deal for the people that are adding things in the author environment. It’s a really big deal for your developers, because you’re telling them that this is a metadata property that we handle and we own. And you can actually work with the different metadata standards and metadata industry groups to get your terminology introduced into what is used by all the companies. Like it’s a very, very powerful thing. So I’m gonna show you how to register a namespace. I know this is a whole lot of information. There’s so many things. And even if you take 20% of this and take it and run with it, it’s gonna be amazing in terms of the incremental benefits. So moving into user experience, what’s usable versus what’s noise? So when you think about the user that’s actually managing an asset, like they upload an image, are you exposing every field to them, or are you curating that experience? When you upload a PDF, are you showing them a field for duration? Because that’s not applicable to a PDF. That really is only applicable to a multimedia file. And so these are the things that you can actually tailor in AEM. And getting rid of noise is one of the biggest user adoption considerations, because when people are overwhelmed and they don’t understand the prioritization of what you’re asking them to put in there, they’re not gonna do anything. Like I know personally, I work in metadata, and if you give me too much stuff, I’m exhausted. I wanna know what you need from me. So you can curate the user experience in AEM. You’re also able to customize metadata panels that are used in Bridge and Creative Cloud. And those are things that I highly suggest if you’re entrenched in AEM assets. Reach out to different people within Adobe that you’re working with and ask them about this. Like ask them about customizing panels, because that’s gonna really help your creative teams quickly apply metadata without them having to put it in three different systems. Like they can easily do it in Creative Cloud or Bridge. So what you’re gonna do is you refine the schema based on MIME type. MIME type took me a hot minute to figure out what it actually meant in this context, but really it’s the file format. So you’re able to determine if there are particular properties that you need for application files, like PDFs, documents, Excel files, et cetera, versus multimedia files, versus images. But you can actually get very, very granular with it in case you want specific files or specific properties for something like an audio file versus a video. Say you’re capturing a podcast versus a commercial. You can very easily manipulate all of those properties. And so you’re able to actually edit everything within the metadata schema. This is a sample of what you’re able to do in terms of metadata schema panels. Take down this little bit link because it’s just something to consider. There’s a lot of information out there on how to introduce your own organization’s custom metadata into upstream activities. Last thing before we get through the demo, just so you know that this is, again, a lot of information is automating metadata. And if we’re being completely transparent, we want to automate as much as possible. Just trying to get people to apply it ad hoc, it’s really difficult. And typically the time from when something is produced to when it’s ingested, you’re going to lose a lot of the metadata because it requires almost manual knowledge transfers. So how are we actually able to automate it upon upload? So the first thing that everybody should look at, I know that this isn’t a day one immediate thing, what third party integrations are available? So Adobe, we have Workfront. However, there’s also things pertaining to a Primo or Wrike or any of these other upstream systems that are almost capturing like the creative brief or different pieces of information pertaining to the concepts and campaign strategy and things like that, where you have a whole subset of assets and content that’s produced based on an initiative within your organization. Vast majority of the time, that information is somehow captured in a PowerPoint. And once that PowerPoint has been reviewed, all that information is lost. So where do you have an opportunity to start looking at things, not just from a AM, but from a content life cycle perspective. That way you can look upstream and say, hey, you’re capturing a program and a strategy and a campaign and a target audience and all of these things when you’re producing these banners, let’s figure out how to systematically capture it and then apply it to our assets upon upload. Because otherwise somebody has to tell someone to manually tag it. And there’s just a whole lot of opportunity for optimization. The last piece is when you start thinking about AM extensions, those are where I was saying that there are panels that you can introduce into different clouds within Adobe. And you can have different people that are working within those environments capture information as opposed to it all being collected right upon upload into AM. These are things that are workflow oriented and process oriented. And your other opportunity is applying certain properties to hierarchies so that they get automatically applied when something is uploaded into AM. I’m gonna show you that. The thing about that is it requires a lot of foresight into what those properties are. And there’s a limited number of people that are able to actually create those profiles. So your two biggest opportunities, which of course are never things that you’re able to put out there day one, third party integrations, AM extensions. So we’re gonna get into this metadata profile where you’re collecting information and applying it to a folder. And now we’re gonna get into the demo. Well, we are not in best practices yet, so apologies. All right, assuming everyone here has AM, then you are likely familiar with the navigation panel in author. One thing that I wanna show you is a very forbidden area of AM. It’s something where I’m giving it to you just as context. This is not something that authors generally have access to because it’s very much a development space. So within AM, as we’re thinking about files, I’m gonna go into experience league. I personally love a column view because I just love a hierarchy. So as we’re going in here and we look at profiles and sensei, so I’m gonna show you smart tags and things like that versus just standard. I’m gonna upload an asset into standard using a metadata industry-wide standard for IPTC. So drag and drop, beautiful thing. This looks like nothing. Like this doesn’t look like a very fancy thing. It looks like a banner. There’s so much metadata that’s embedded in this. And what I mean by embedded metadata is it’s information that is carried from system to system with the file. And so when we look at this property, I’m sorry, when we look at this asset and we look at the properties for it, you’ll see I just uploaded it and it has all of these different pieces of information. And of course, these are pretty generic, but this particular asset, and please write this down by the way, because this is IPTC’s asset that they have provided to show you embedded metadata. Adobe is working with them and Creative Commons in order to make sure that we can extract all of these things. But this isn’t something that Adobe produced. This is just something that Adobe can handle. So all of these properties are automatically filled out because they were in the file. And that’s magical. That’s just amazing. And so when we look at the file, and I go into Bridge, I don’t know if everybody has Bridge, but all of these different properties are standard and these are all the things that it was filled out with. And this isn’t something we’ve gone through in previous sessions, but the whole reason that I wanted to point this out is because it’s very important to understand what you can collect from other systems. So this is now gonna open in Photoshop. And when I look at Photoshop, now if everybody can see everything within here, this is all stuff that somebody upstream could fill out and they could give you the file and bam, it shows up in AEM. All of these different properties are upstream and you don’t have to fill them out in AEM. AEM can just ingest the file, populate the properties. And what’s even more meaningful is that Adobe actually introduced metadata panels so you can introduce your own custom tags, your own custom properties. All of those things that can be captured in different applications in Creative Cloud. So it’s shifting that burden of responsibility upstream to different creative processes. And it’s a really, really powerful thing, but it requires that you have certain levels of enterprise strategy, like certain things that you’re wanting to input. So when I said I was gonna show you a part of AEM that most people don’t get to see because it’s very much off limits, it’s over here in something called CRXDE. And if you look over here, this is a huge hierarchy. If I go into AEM, go into Experience League, you’ll see that all of these things are actually hierarchies and nodes. And so when I go into Standard, which is where I uploaded that file, you’ll notice that there’s something called Metadata. That’s where all of your metadata properties are stored. There’s gonna be a whole lot of them. This can become noise. Like this, you don’t necessarily wanna expose a hundred and something properties to someone. Like, do we really need to show this value to your end user? No. So what we’re gonna do is we go in, and by the way, just cause we don’t expose it to the end user doesn’t mean it wasn’t captured. Yeah. Elise, I’m sorry for the interruption. It looks like you have exited Adobe Connect. We’re no longer seeing your screen. Well, that’s ironic since I was saying it was a part of things that you don’t normally see. So let me get back in there. Thank you for letting me know. Thank you. Thank you for your patience. We’ll be right back.

Okay, all good now? Yes, we can see your screen. Thank you. All right, perfect. Okay, so within CRX, you’re able to see all these properties that were extracted from just uploading a file, but they don’t all have to be exposed to an end user. So when you actually go in and you’re managing the asset experience for different individuals, you can go into assets into the metadata schemas, and you can change what all is visible. So for those of you that are actually using AEM, redo this. Not everything that’s on the first tab is relevant. So you can actually change what all gets exposed on a tab by tab basis. So I’m just gonna completely delete a whole tab, and then I’m gonna add in a new tag field at the very top.

And so you’re able to actually change all of these different properties. They’re explicitly there for your use. Like they don’t have to be what you see out of the box. They’re just gonna delete actually all of these, because you don’t need them if they don’t make sense. That does not mean that you’re deleting things behind the scenes, and you’re able to change all of these different properties. You’re able to specify if there’s dropdowns you wanna use, if there’s tags you wanna reuse, all of these different things. So before I even set this tag up, and I’m gonna try to cover a whole lot in five minutes. So let’s run through it. When you look at this, the whole area that nobody should ever play in, you’ll see that there’s a lot of these different properties, and they have a name colon, like Photoshop colon, DAM colon, DC colon. By the way, that stands for Dublin Core. That’s a namespace. And so if I wanted to produce my own namespace to categorize all of my own values together, I can actually go into AEM, and this is something where you’re gonna work with the development team, but this is what you can put in panels and do all these different things. But basically, it’s grouping together your own properties so that they’re not just haphazardly thrown around. Like, you know they’re things that you intentionally were trying to capture. So as I go in, I can look at node type administration, and this is something where you’re gonna wanna work with your development team. But if you notice over here, there’s all of these prefixes with different properties associated to them. And again, that’s using metadata standards. It’s using industry standards versus just new ones. And so if I wanted to create one that was specific to my organization, I can actually create a new one, I’m gonna say that this is experience-like, EXLG. Now all of a sudden, if you notice, there are all these different prefixes, like Photoshop and Dublin Core, and all of these things that you saw on the deck. And then I’ve also created a new one that’s specific for the properties I wanna capture. So this is why it’s very important to know where are you capturing metadata that’s industry-wide, and that’s just a purely understood set of properties versus where you deviating. So within here, if I wanted to produce a new property, and I go ahead and delete all of these tabs, again, all of this is customizable. Just because I’m deleting the tab does not mean I’m deleting the metadata. It solely means I’m changing the UI. Your metadata schema form should really only represent information that you either want people to know, or you want them to fill out. Otherwise, it’s noise. Try to reduce the noise. So I’m gonna come in here, and I’m gonna say that I wanna put in the whole thing for experience-like product. If you notice that right here, I’m putting in JCR content, which is the Java content repository. That’s what this whole big hierarchy is. That’s totally off limits. Metadata with our net new little prefix and a new property name. Realize that what I’m mapping this to is how it says there’s JCR content here. Metadata is the next level down. And what I’m saying is whatever is actually the name of this property, that’s the word underneath the metadata hierarchy. Again, hierarchy meaning your own personal computer where you’re organizing files and different things like that on your PC. It’s stored the same way behind the scenes. So we have JCR content, metadata, and then all of this stuff that’s stored. And what I’m saying is that I want it to store against this property. Let me go ahead and save this. And the great thing about AEM is that you also have the ability to add tags with ease. The tags again, hierarchies. I created a hierarchy that was specific to products. So I have experience cloud, all of these different entries. The interesting thing about tags is you can actually merge them, you can move them. Like say we used to have a tag called Adobe. My Bluetooth just went out. That is not what I was trying to type. Adobe Experience Manager. So now I have Experience Manager and Adobe Experience Manager. If I go in to my assets and I went in here and decided that I just wanted to tag this with the product of both of these, this is how easy it is to manage tags. Tagging it, saving it, lovely. When I look at the information, both of those are there. But let’s say, hey, Adobe just went through a rebranding exercise and we don’t want both tags on there, we want everything to just say Experience Manager. I can actually go in to my tags, select the one that I’m wanting to merge, and say hey, now go in and everything that is tagged with Adobe Experience Manager, I want it to just say Experience, but now I’m gonna go back to this just to show you, and you’ll now see that it’s merged the tag. So we only have one of those two tags. So these are all different things that you can do within AEM to help manage content and to manage the metadata. When you’re even looking at the assets and the metadata schemas, if you decide that you want to apply a different schema to a different hierarchy, so let’s say I wanted to change this and put a new field in explicitly, I can say that, oops, let me go back. I can actually decide which area I want to apply new schemas to, and the great thing about that is that as assets are uploaded, and this is a very, very big deal for metadata strategy, if you notice on this one, it doesn’t have that property that said New Schema, it’s not there. It’s using a different metadata schema, and if you recall, I put the new schema that has a unique property against this area of the hierarchy. So the great thing about that is I can actually take, I can take this and upload it, and if you see, it has the New Tags field. So what that is actually illustrating is if you were part of Sharon’s session last week, your hierarchy can determine which metadata schemas are being used. So if you have one hierarchy that’s all about campaigns and strategy versus another hierarchy that’s explicitly there for stock photography, they may have very, very different metadata, and using your schemas, you can add different processing profiles and different schemas to different part of the hierarchy in order to collect the information that you need. So I know that this was a tremendous amount of information, and I wanna at least give a few minutes for Q&A, but please reach out to me if you have additional questions on the things that we didn’t even get the chance to cover. It’s just such a robust system that it’s very difficult to cover in one hour. Just make sure you’re focusing on the enterprise level properties and taxonomies, and that’s gonna be your biggest win straight out the gate. So I should have stopped sharing in case there’s any questions we wanna run through. Right, thank you, Elise. That was really comprehensive. I know there’s much more to show, but I think for today, that was terrific. We do have a couple of questions.

So first one, can we lock down tags so that users can’t dynamically create new tags, but still inherit the parent attribute? Yes, so that’s the whole point of tags. You actually determine who in your organization is a tag admin, and they are the only group that’s allowed to add tags and manipulate them, so that way everybody else is adhering to that controlled vocabulary policy. Great, here’s another one. How do you require the metadata to be added as the asset is being loaded into the dam? Is there a way to prevent assets from being saved if they are missing metadata? Yes, you actually have a whole other tab on your schema with rules, and one of the rules is, is it required? And if you check that box, then people need to fill it out in order to save. It also means that any of the assets that are using that schema, so let’s say you decide to make something required, and there’s already hierarchies using that schema, it’s gonna flag those assets and say that required metadata is missing, and that doesn’t mean that they’re gonna get pulled off the web or anything like that. It’s just an indicator to make sure that you have metadata integrity. And last question, how is folder metadata used in AEM? Does it feature to assign metadata to a folder? How is that used? So folder metadata and a metadata schema are a little bit different. The metadata schema is about the asset, and the folder metadata is really more about the folder that contains all of the assets. There’s no way to determine properties on a folder that get inherited down using the folder schemas.

If you do customizations, you can actually create those rules, just be careful about governance. But they serve different functionality. One is more about, the folder metadata schema is more about being able to find a certain area of your asset directory structure that contains assets based upon those folder properties, whereas your metadata schema is describing the assets in there and can actually be written back into the assets into embedded things. So definitely reach out to talk about the different strategies for both use cases. Okay, great. And one quick thing, so thank you, Elise, for the great Q&A and the great presentation. Before we all sign off, I just wanted to give a quick update on Adobe Summit. If you haven’t heard yet, it is free, it’s virtual, of course, it’s scheduled for April 27th and 28th. You can sign up at summit.adobe.com. We actually have a link to it in the resources pod. And for experience manager assets and dynamic media, we have some really great sessions.

You can see them listed here, but I want to do special mentions of the content strategy and architecture session. That one is one that Elise will be presenting in. And then is your metadata future ready? Another very pertinent session based on what we talked about today. And Adam Crane from Dell will be the guest speaker. And he’s got an extremely robust metadata strategy at Dell. They’ve been working on it for years and he’s an excellent presenter, so you won’t want to miss his session. We have others as well. You can sign up for some of these where you’ll learn more about Adobe AssetLink and all kinds of interesting things about what’s new in FY21. And I think with that, I know we’re at time. If folks could take one second to just rate us on this presentation today, we’d love your feedback. We’d love to learn what you got out of today. And we definitely hope to see you next week when we talk about brand portal. And I think at least with that, we’re all set for the day. Thanks again for the great presentation. And thank you everybody who carved out time today in their schedule to learn about metadata. Appreciate it very much.