Hello, POST request does not seem correct here. It should have complete
path to whole asset for example modifying metadata at
/content/dam/wknd/en/activities/hiking/equipment_6.jpg bring out
something like below post request POST
/content/dam/wknd/en/activities/hiking/equipment_6.jpg HTTP/1.1] Can you
retry after cleaning the logs?
Rightly pointed out by @BrianKasingli that it is supposed to be Jcr API
so the concept of ResourceResolver is not applicable as it uses sling
API which is higher abstract level. You need to use the node level
operations using JCR node interface.
Here good authoring experience means faster load by allowing cached
content serve from dispatcher and no need to go to AEM server.
Specifically on author instance only cache static content (js,css ) and
steer clear of caching actual content as stale content can become an
If your question is about finding out a special property on a component,
try querybuilder page to experient with various queries. If you want to
also update some value, try groovyconsole. Might have a bit of learning
curve but you won't repent the te spent in the long run.
If you can make user part of "workflow_users", it will be a quick and
fast way to enable the manage publication functionality. However if not
then below nodes need be given access as per below list(dump from
netrcentric plugin): - workflow-users:- path:
/etc/workflow/scriptspermission: denyprivileges: rep:write- path:
Hi There, I think you are talking about the Asset Http API which is
mostly used for asset manipulation(crud operations) and not for search.
Searching can be done using querybuider API which is exposed @
http://localhost:4502/bin/querybuilder.json and allows parameters to be
passed on to the search engine. Please check
which will help to understand the overall big picture about AEM...
Hi There, Smart tags using Sensei has two options:1. Untrained/Default
smart tags: These are assigned to assets uploaded without any inputs
from the user. How the Sensei trains is completely black-box and user
does not have any control over it. I don't think once you remove any
smart tags, that information ever goes out back to Sensei to correct the
tags. Also this makes a bit of sense as personalizing tags can conflict
with other users' way of tagging the same set of object. So no training
Hi There, OOTB metadata upload/download solution works only for metadata
node's properties of an asset and as related assets are stored therein,
it can't be done with this solution. Either you need to write something
custom which csv kind of input basing it on OOTB solution or come up
with something else. One thing I can think of apart from csv solution is
creating a curl script/groovy script and feeding it with right
properties. You can use SlingPostServlet in those script. Need to
Hi There, It is absolutely possible and any custom metadata schema that
you create has to applied to a folder to allow the assets within that
folder use the metadata schema. It means if you have defined a custom
metadata schema and applied to a folder let's say /content/test then all
the assets within will have that metadata schema available for editing.
If your question is about the location where metadata schema is created
then yes you are right that it gets created at