Tested on 6.1 latest CFP and all working as normal for both methods, the
metadata editor is
triggered:mnt/overlay/dam/gui/content/assets/metadataeditor.external.htmlAs
you have a custom editor check that it is overlayed properly, and that
the sling selector works.Customizing the Consoles (Touch-Optimized UI) -
docs.adobe.com
Do you mean templating? Adobe Scene7 * Template Basics This works in a
similar way to a layered photoshop file, in fact you can even upload a
PSD and let S7 manually create the template.You can then control the
layers via url commands e.g. to swap images
Daniel Paiva BR wrote... Hi mvance: I understand what you mean. The
problem is that it states in the dropdown list: "Associated Content".
From my view, it mislead the developer and the user to use it as a real
Associated Content. Should it be called Content for Reference or so,
would make more sense. In this case, how can the user create a fragment
with, for instance, image that gets published? For now, we are
customizing the Metadata area to accept the real Associated Content, but
the users did...
Collections are meant to be used on Author only, for internal
usage/organisation.The exception is if you use the Brand Portal cloud
service add on, you can publish collections there for sharing with
partners/vendors,
I cannot find any information on this issue internally, please open a
support ticket for deeper investigation if it is having an affect on
your system Mark
Hi Anisha,6.3 has not been released yet.The API will be posted to the
new verison of this page upon
releasehttps://docs.adobe.com/docs/en/aem/6-2/develop/ref.htmlMark
Hi Ravi,I tested on my local install with DM enabled and it worked
fine.Please try to capture the failing image request in your browser or
log file, it will give info on the issueMark
Hi Herbert,I believe the doc is in error here, I'll have it fixed up.We
have versions for 6.0 and 6.1. For 6.2 I believe we'll need to build a
new package, please log an issue via the AEM portal for this.Thanks
AdrienM wrote... The issue has been identified as bug by the Adobe
support, it will be fixed in a later version of AEM. If a user does not
have the permission to edit the ACLs of a folder, he cannot rename it
(even if he has the permission to modify/create/delete it).I believe
this will be resolved in 6.3
Hi,in http://localhost/libs/granite/security/content/useradmin.html
click on Permissions and this will open the new screen.Find the user
group (e.g. dam-users), double click to open and then assign the
relevant rights. Once they have this the user should be able to rename
the folder.Mark
As far as I can see, according to the standard, dc:rights is a String
array:https://www.w3.org/2008/WebVideo/Annotations/drafts/ontology10/WD/XMP.htmlhttp://dublincore.org/documents/dcmi-terms/#terms-rightsSo
it seems to me that
/libs/dam/content/schemaeditors/forms/default/items/tabs/items/tab2/items/col1/items/copyright
should also be a String array.I think this would need to be reported to
Customer Support to check into this furtherMark
SPS UI supports 7500kbps as an encoding option.Higher bitrates in an AVS
setup are possible but would need to be submitted via the API and then
tested.You should work with AEM Customer Support for help with the API
call, and also to review any potential throughput onto the systemMark
The 5.4.2 viewers have consolidated and minified the JS requests for the
SDK. Previous releases had multiple JS requests for SDK components, now
there is only one JS request for the SDK. This is the default for the
viewers (no customer interaction required).Here is an example of a
consolidated request from the BasicZoom Viewer on
production:http://s7d1.scene7.com/s7viewers/html5/js/BasicZoomViewer/js/s7sdk/utils/Utils.js?namespace=s7classicThere
is no obfuscation option. Mark
Hi Divya,The videos are encoded in the cloud, and also served from
there.There is no encoding done on local AEM servers.So, you do need to
complete the DM config.Mark
What sort of properties?You can add metadata fields to the
display:https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/metadata-schemas.html
Hi,if it just that PDF then could be some issue in the jcr for it.The
error comes from
here:https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-1.0/javax/jcr/InvalidItemStateException.htmlIf
it is happening for different assets, then there is some issue with
concurrent writes.I think this should be reported to Customer Care via a
ticket if you need helpMark
dc:title is filled according to the mime type of the file, and according
to the standard, xls and xlsx are different mime entries..xls
application/vnd.ms-excel .xlsx
application/vnd.openxmlformats-officedocument.spreadsheetml.sheetThis
will be similar for .doc and .docx, ppt and pptx
etc.https://blogs.msdn.microsoft.com/vsofficedeveloper/2008/05/08/office-2007-file-format-mime-types-for-http-content-streaming-2/Mark
Hi,the functionality of Dynamic Media is changing from release to
release, and with feature packs. If you intend to switch over, you need
to check your use cases - not all S7 features are currently supported in
6.2 - for example, templating based on PSD file. More features will be
added in
6.3.https://docs.adobe.com/docs/en/aem/6-2/release-notes/assets.htmlMark
Hi,Assets works differently from that.You could disable edit of the
fields in the Metadata Schema editor
perhaps?https://docs.adobe.com/docs/en/aem/6-2/author/assets/managing-assets-touch-ui/managing-multiple-assets.htmlMark
HI,not sure I quite follow the description - if you'd want to copy
metadata from one asset to another, then you'd have to have some way to
update the JCR with this info, like a workflow modification or else a
program which modifies jcr directly.I don't believe there is some way to
modify automatically Mark
Hi,You can extend or customise any workflow in
AEMhttps://docs.adobe.com/docs/en/aem/6-2/develop/extending/workflows/customizing-extending.html?wcmmode=disabledDAM
Upload Asset is the generic workflow for Asset uploading.To find out the
specifics of what each steps does, you can test and examine the jcr and
see what has changed.If you want to insert your own workflow step(s),
you may query any of the data from previous steps.Mark
to clarify: did you try the options under
here?https://docs.adobe.com/docs/en/aem/6-2/manage/seo-and-url-management.htmlAnother
way would be to add “sling:vanityPath” property to the property node of
the image, but this is not exposed in the UI, to my knowledge.So you
would need to customise the screen so that the end user could modify
this value.Or if you want to control it a different way, write an app
which updates the jcr directly
Hi,In a normal setup, files are activated and published out in full. The
system just knows a node is changed, and activates it accordingly,
without the context of what has changed.So when using Tar storage, this
is an ideal scenario for a shared datastore, so that author and publish
access the same file, so there is no copying.once you turn on binary
less replication,As you are using Mongo, then the file is shared in
author only, and must be replicated out to the publish servers. This is
fine un...
I moved this as I think we need a Marketing Cloud expert to
comment.Normally the account will auto unlock after a set period. It is
likely that a manual password reset will achieve an unlock also
Hi,I'm not sure I fully understand the need to customise the screen.For
a large number of updates like this, best to write a program to access
the JCR directly, and not use AEM at
all:https://helpx.adobe.com/experience-manager/using/programmatically-accessing-cq-content-using.htmlTo
maintain over time, for new assets, if there is some need, you could use
a custom launcher, for example. But ideally I think, the end users
shoudl maintain the metadata, before teh files enter AEM, and after they
are...
Hi Rob,Yes this seems feasible, but AEM should not create these files.
In fact this ignore ability was added in a very old version (5.3) so if
it is occurring for you on a newer version, this can be reported to the
Customer Care team to investigate and log the issue.Thanks,Mark
Hi Rob,would something like this
work?https://support.apple.com/en-ie/HT1629http://www.christiano.ch/wordpress/2010/11/27/mac-os-x-prevent-ds_store-file-creation-on-network-volumes/I
don't have a mac to test this on.I'm not sure if AEM is able to prevent
it, if you'd require an AEM solution, this should be checked with the
Support teamMark
