Hi,
How do we copy/package the Metadata Profiles, and Processing Profiles from test to be deployed in Production?
Solved! Go to Solution.
Views
Replies
Total Likes
All the customization get stored at /apps/dam & for you use case it is at [1]. Make use of a package with filter /apps/dam to move between envirnoments. I don;t think you need this in publish technically since editing always done in author.
[1]
/apps/dam/ingestion/profiles/metadata/
/apps/dam/content/schemaeditors/forms/
Views
Replies
Total Likes
All the customization get stored at /apps/dam & for you use case it is at [1]. Make use of a package with filter /apps/dam to move between envirnoments. I don;t think you need this in publish technically since editing always done in author.
[1]
/apps/dam/ingestion/profiles/metadata/
/apps/dam/content/schemaeditors/forms/
Views
Replies
Total Likes
The doc topic does not talk about replicating this. However - it says you apply it to an asset:
"Any asset that you subsequently upload to the folder has the default metadata that you configured in the Metadata Profile."
Try attaching the metadata to an asset then replicate the asset. Is the Metadata appear with the asset on pub? If not - then try manually creating the Metadata profile on pub.
Views
Replies
Total Likes
Sham HC wrote...
All the customization get stored at /apps/dam & for you use case it is at [1]. Make use of a package with filter /apps/dam to move between envirnoments. I don;t think you need this in publish technically since editing always done in author.
[1]
/apps/dam/ingestion/profiles/metadata/
/apps/dam/content/schemaeditors/forms/
Thanks Sham! This helps!
Views
Replies
Total Likes
Here is the AEM documentation on MetaData Profiles:
Views
Replies
Total Likes
Views
Likes
Replies