Hi,
I have a requirement to display the filename and the extension on the metadata schema.
I was using these:
The problem is those values are not consistent for all assets.
For File Name, I noticed this property is filled only when we set the dc:title in the Metadata, after that it fills this field. The problem is, it is not filled for all assets. For some formats it is not filled, for example, for PNG it works for a .doc it doesn't.
The same happens for dam:FileFormat, for some file formats it is filled for other it is not.
Is this working as it was designed for?
In case it is not always filled, there would be a way to use the node name in the metadata schema as the asset node name is the file name?
Or any other alternative?
Any inputs are welcome.
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
Sounds like you may want to customize the workflow process for adding/updating DAM assets. You could have a custom workflow step added to the OOTB workflow process that extracts the extension and stores the data on the node, you'd then be able to add this to your metadata schema.
Views
Replies
Total Likes
Sounds like you may want to customize the workflow process for adding/updating DAM assets. You could have a custom workflow step added to the OOTB workflow process that extracts the extension and stores the data on the node, you'd then be able to add this to your metadata schema.
Views
Replies
Total Likes
hi @leeasling,
That's what I was thinking to do.
Thanks for the tip, I'll create a custom step to set the cq:name and dam:FileFormat.
Thanks
Views
Replies
Total Likes
Hi,
"
---
Jitendra
franciscoribeir wrote...
hi @leeasling,
That's what I was thinking to do.
Thanks for the tip, I'll create a custom step to set the
cq : name and dam: FileFormat .
Thanks
Views
Replies
Total Likes
Hi @Jitendra,
I'm going to fill dam:Fileformat with the file extension, that I can get from the filename.
Do you think this could cause problem?
Thanks.
Views
Replies
Total Likes
Well,
If there is no such attribute, then you are going to create it. And my point is that we should use dc:Format if we can rather than creating it. Just putting my thought. Can't really say if that could cause some problem.
--
Jitendra
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies