Metadata Schemas vs Metadata Profiles

[#1]

What is the difference between these two things and how do they tie together? From what I've read in the documentation:

• Metadata Schemas have more form field types and they define what values can be entered by an author for a particular asset?
• Metadata Profiles are the same thing but they're defined automatically when an asset is uploaded?

I'm trying to determine the best way to add extra metadata properties for PDFs in a particular folder in the DAM. So I'm guessing Metadata Schemas would be the way to go?

I may also need to create a metadata-driven workflow that prompts the user to enter the extra/custom PDF metadata that I'd like to add. Is there anymore information or are there any examples of these? There only seems to be this tiny section that says what they are on this page of the documentation.

Thanks in advance! Also, I apologize in advance if this is in the wrong section (AEM Assets vs. Adobe Experience Manager).

[#2]

Ok, Lets put it this way, If you want to add new metadata property (with some default value or custom one ) to the asset, you need to update metadata profile with new metadata properties which will be applied to only new assets uploaded in that folder, if you want to apply that new metadata property to all the previously uploaded assets on that folder, you have to run ” DAM UPDATE ASSET” workflow on all the assets. This will only update new metadata property value in JCR at ./jcr:content/metadata path. Now if you want to access this value of new metadata property which is included in the metadata profile in the properties page of an asset, you have to update metadata schema form.

in short, the schema form is like what properties from the profile you want to show to the author, there could be 10 custom properties and if you want to show only 5 out of those 10 then update schema form with only those 5

hope this helps!