Adding custom tags in TagUI | Community
Skip to main content
stiegjo22
Level 4
February 10, 2025
Solved

Adding custom tags in TagUI

  • February 10, 2025
  • 1 reply
  • 419 views
I created a custom metadata schema under metadata schema forms with new metadata properties and applied it to a DAM directory where I'm working. However I get an error "Unable to edit properties. Insufficient permissions." if the asset doesn't already have the custo metadata properties. (it works for files that have been previously custom metadata properties) How do I set it up to create the metadata node for files without the custom tags when using the TagUI?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by AmitVishwakarma

1. Ensure Permissions: Make sure the user executing the TagUI script has permissions to edit metadata in the DAM, including creating new properties. Check user roles (e.g., DAM Admin or Author).

 

2. Verify Metadata Schema: Confirm the custom metadata schema is applied to the asset types (e.g., images, documents) in the DAM. It must be associated correctly.

3. Create Metadata Node for New Assets: Ensure your script handles assets that don't have the metadata properties. You may need to use AEM's REST API to create the metadata nodes for new assets before modifying them. Example:

POST /bin/querybuilder.json { "path": "/content/dam/your-folder", "type": "dam:Asset", "p.limit": "-1" }

4. TagUI Execution: Ensure the TagUI script is run with the correct user credentials and permissions. Simulate metadata field updates with set and click commands as needed.

1 reply

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity AdvisorAccepted solution
Community Advisor
February 10, 2025

1. Ensure Permissions: Make sure the user executing the TagUI script has permissions to edit metadata in the DAM, including creating new properties. Check user roles (e.g., DAM Admin or Author).

 

2. Verify Metadata Schema: Confirm the custom metadata schema is applied to the asset types (e.g., images, documents) in the DAM. It must be associated correctly.

3. Create Metadata Node for New Assets: Ensure your script handles assets that don't have the metadata properties. You may need to use AEM's REST API to create the metadata nodes for new assets before modifying them. Example:

POST /bin/querybuilder.json { "path": "/content/dam/your-folder", "type": "dam:Asset", "p.limit": "-1" }

4. TagUI Execution: Ensure the TagUI script is run with the correct user credentials and permissions. Simulate metadata field updates with set and click commands as needed.