When I re-looked at the overlay of custom metadata shcema editor, got to
know that we have to
overlay'/libs/dam/gui/components/admin/metadataeditor/formresourcefinder.jsp'for
controlling the schema editor to display for bulk editing.Thanks !!
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...
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 kunal, ravip62119204was this issue resolved for you? Is there any
root cause apart from upgrading to latest service pack? We are running
with AEM 6.0 SP2 and our servers started facing this issue. We reverted
server instances to 1 month back previous state and seemingly new images
work. But intermittent, few of old images fail. Still dono the root
cause.
In case you need fix on 6.1 please log support ticket as for this issue
there has been a Hotfix made available so you can review accordingly.
Also this will be addressed in 6.3 as Mark suggested. Thanks for your
feedback.Thanks,Gaurav
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,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
Hi Adding to what mark has suggested you:There's a GUI for modifying the
Asset Metadata forms. To get there, select Tools > Assets > Metadata
Schemas from the left rail.Documentation can be found at
http://docs.adobe.com/docs/en/aem/6-1/administer/content/assets/metadata-schemas.htmlReference
article :-
http://stackoverflow.com/questions/31383230/how-to-show-edit-custom-properties-on-the-properties-page-in-aem~kautuk
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,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
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,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,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...
Hi,It looks like this information is not publicly available for security
reasons. As for a locked account, please have a supported user contact
customer care with the locked user's email address.Cheers,Jantzen
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...
I agree with Kautuk - this is the default behaviour of AEM Assets and
isn't strictly related to Dynamic Media add-onPlease check best practice
for sizing
here:https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/best-practices-for-assets/assets-sizing-guide.html
Hi,Let's suppose you are using a custom workflow which pulls a metadata
value for each file, say some sort of GUID or productID- at the end of
the day you are still relying on your end users to set and maintain that
metadata, e.g. using the tools built into Photoshop or else Adobe
Bridge. So there is a still a chance it won't be done correctly?If the
user is randomly changing the image name, it's better to educate the
user or to understand why this is happening. If they rename the file,
maybe it...
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
To deliver an asset with a viewer preset, you must replicate/publish the
viewer preset. (All viewer presets must be activated and replicated to
obtain the URL or embed code for an asset.) See Publishing Viewer
Presets for more information about the error log posted, something was
wrong with the steps taken because something is null - you can check in
jcr or else in
config:libs.dam.components.scene7.dynamicmedia.dynamicmedia$jsp Unable
to save imageserverurl and videoserverurl
java.lang.NullPoint...
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
the Image server supports a req=exists parameter, so you could use that
just in browser, or with curl / wget, for
examplehttps://marketing.adobe.com/resources/help/en_US/s7/is_ir_api/is_api/http_ref/r_exists.html
Thanks for the reply Mark. Sorry for the tardy reply, but I thought I'd
put some notes down here in case someone else runs into the same
thing.It turns out that the AEM image component was the culprit. When
using a resourceSuperType of 'wcm/foundation/components/image', AEM
creates a bunch of renditions of your images - this is where the file
naming went awry. If I don't use the image resourceSuperType on my
component then the renditions don't get created and my file name remains
the same as the...
