Custom metadata tags?

I know that by tweaking the flex config files you can have
custom metadata tags and you can extract them with reflection (
describeType() )
But can this happen in flash?
Can they be substituted by a clever use of interface or
inheritance?

File a bug with a simple test case if there already isn't one. No
guarantees it will get fixed? Why can't you put the metadata on the class?

Similar Messages

DescribeType omits custom metadata tags on constructors

I want to put a custom metadata tag on a constructor, but I cannot get the metadata in describeType. Metadata tags placed on any other public location (class, field, or method) can be seen in describeType XML.
Is this something that will be fixed, or is there some way I do not know about to get metadata off constructors?
Also, is the metadata on constructors emitted into the ABC?
Thanks!

File a bug with a simple test case if there already isn't one. No
guarantees it will get fixed? Why can't you put the metadata on the class?

Flash CS5.5[Publish Settings]: How to include custom Metadata tags in swf?

In Flash CS5, the 'Publish Settings' for the fla had an 'Export SWC' checkbox that took care of that.
The option is missing. Why was it removed and how can that be done in 5.5?

Thanks sinious, but, it doesn't work.
Let me elaborate on what I want to do:
I'm trying to create a swf in Flash CS5.5, that's using a flex library (swc) that relies on Metadata tags (anotations).
I need to use the metadata tags in my as3 code (in the fla), and They need to be compiled into the swf (by Flash CS5.5 compiler...).
Although, when I load that swf, the metadata tags aren't compiled into it (I'm using describeType to check if tags are available in the swf).
In flex, I would use the '-kepp-as3-metadata+=' compiler setting to do that, in Flash CS4 & CS5 I used the 'Export SWC' in the publish settings, but that's removed (WHY???).
Checking XMP Metadata didn't change that, the tags are still not included in the compiled swf.
Anyone?

Help with searching custom metadata tags

I have written a Photoshop JavaScript for my employer which allows my users to enter custom information into metadata fields. My intention was to use Bridge to create a searchable asset management system for these files. However, I am running into several problems in allowing my users to search for images with the criteria that they are looking for.
My first thought was to create my own search dialog which then looks for files whose metadata matches the search criteria. I was able to do this and return an array of thumbnail objects, but to my surprise there does not appear to be a way to create a new window which shows these thumbnails? (without creating a new folder object and copying the files there which would tie up too many resources.)
My next thought was to create a custom namespace/panel for my metadata. This also works up to a point. I cannot seem to get my custom metadata fields to show up in Bridge's search or filter areas. I see the SDK example for creating search conditions for a custom node, but how can I modify search conditions for "normal" nodes (folders)?
I'm sure that many of you have run into these issues, there are several posts in this forum and others from people with similar questions. I'm not seeing much in the way of answers, however. Any information would be much appreciated.

I am no expert, in fact a total beginer with Bridge scripting.
I have also found that it a problem displaying the required thumbnails. To get around this problem I have used the label rating, changing all the thumnails I don't wont to reject.
IE:
var items = app.document.visibleThumbnails;
for (var i = 0; i < items.length; i++){
var md = items[i].synchronousMetadata;
md.namespace = "http://ns.adobe.com/photoshop/1.0/";
if (md.Keywords != "") items[i].rating=-1;
This will only show thumnails that do not have keywords so long as the view "Show Reject Files" is not ticked.
I suppose if you used the rating you could copy them into a field that you could restore from.
As for the sorting I haven't done much with that except this sort of code should work on custom metadata.
new SortCriterion("MyDateSort", "date", "http://ns.adobe.com/xap/1.0/", "CreateDate");
var mySortObj = {};
mySortObj.name = "MyDateSort";
mySortObj.reverse = false;
var mySortsArray = [];
mySortsArray.push(mySortObj);
app.document.sorts = mySortsArray;

Custom Metadata

Hi guys,
I have noticed custom class metadata is now preserved in Flash Builder 4 and I was wondering which tech update introduced that - Flash Player 10 or the Flex 4 SDK?
Thanks.
PS: Flash Builder 4 is fantastic. Great work Adoblings.

Sorry to bother you again, a question has just popped into my head related to custom metadata:
Is it possible to modify the Flex SDK (a personal modification) in order to handle custom metadata tags? In other words, if I wanted to use the following metadata tags to embed files would it be possible for me to modify the SDK to get this working?
    // embeds the file as a BitmapData class
    [CustomTag( file="/assets/image.png" )]
    // embeds the file as a Sound class
    [CustomTag( file="/assets/sound.mp3" )]
    // embeds the file as a Sound class, uses LAME for the MP3 encoding
    [CustomTag( file="/assets/sound.wav", encodingOptions="..." )]
If this is possible where should I start researching?
FYI: This would be for projects that did not use MXML or Flex components etc.

How to export custom metadata fields

How do I export custom metadata fields (or even the DATE) to a text or spreadsheet? Why does Aperture have dozens of metadata choices, but only allows a few to be exported?

You can try Automator which must be installed already in your computer. Create a new workflow, on the left pane select Aperture to see a list of actions, select "get selected items" and "extract metadata", and drag both to the right most pane. there you'll choose the Tag names to extract from the images already selected inside aperture and choose an output method, tabbed text should work fine for a spreadsheet. Hope it works.

Need to export custom metadata fields to a national data base, can I ???

In Aperture3 are custom tags embedded in exported Versions or Masters. I have a task to embed matadata on 2000 items and need to pass on the information to someone who doesn’t have Aperture

I am not sure whether you really can embed custom metadata in the jpeg file itself. However you can quite easily export all metadata associated with a file in Aperture using AppleScript. The script below shows you how it works in principle with the different data categories in aperture: IPTC, custom fields etc. To adapt the script to your needs, replace eg "Photo Category" with the name of your own custom field. By copy/paste you can add more fields...
tell application "Aperture"
set tSelection to the selection
-- this is the header, not really necessary
set tValues to "Version Name" & tab
set tValues to tValues & "File Name" & tab
set tValues to tValues & "Keywords" & tab
set tValues to tValues & "Category" & tab
set tValues to tValues & return
--here starts the real stuff
repeat with i from 1 to number of items in tSelection
set tImg to item i of tSelection
--add Version name
try
set t to name of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add FileName
set t to the value of other tag "FileName" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add IPTC tag
set t to the value of IPTC tag "Keywords" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add a custom field
set t to the value of custom tag "Photo Category" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
--next line/image
set tValues to tValues & return
end repeat
set f to choose file name with prompt "Choose file name..."
set my_log to tValues
set mylogfile to open for access f with write permission
set eof of mylogfile to 0
write my_log to mylogfile starting at eof
close access mylogfile
end tell

Custom Metadata url

I have some custom metadata as type url and the button works perfectly in the metadata panel to open the page.
I was wondering is there a way to show text for the url in the field instead of the url itself. Like you do in a html like with the text between the starting and ending tags.
What I am getting at is I would like to display a action in the metadata and when you click the button in the field it goes to the webpage to proform the action.ex: http://mypage.com/admin.php is in the field but I want to display Admin and still go to that address when it is clicked in the metadata field.
If it won't work not, please make it a feature request.

Hi Richard,
the property syntax since NW04 SPS9 or higher and EP6 SP2 Patch 5 or higher is the following:
&SelectedCustomProps=<namespace>:<propid>(value=<value>/operator=<OP>),...
as example: &SelectedCustomProps=default:description(value=banana/operator=EQ),default:description(value=apple/operator=EQ)
Properties queries with multiple properties are linked with a logical AND. Occurence of the same property multiple times are linked with a logical OR.
Regards,
Thilo

How to render custom JSP tags

We have our own custom JSP tag libraries (some of them extend the Struts tags, but many do not) and want those to render correctly in the design view.
Is that supported by NitroX Struts, or will it only work with built-in Struts tags?
If it is supported, how does one get NitroX to run the custom tags?

It is possible to customize many aspects of the rendering of a custom tag. This is done using a combination of an M7 specific metadata, and standard css rules.
For example, you can change the label, icon and border of a custom tag by doing the following steps:
1) Create a folder named "nitrox" where your tld file is located. For example if you have "/WEB-INF/app.tld" then create a
folder "/WEB-INF/nitrox/".
2) In the nitrox folder created above, create a file named "app.tlei" (for Tag Library Extra Information). The file name used here should match the name of the tld file. In this case "app".
3) Paste the following content in the app.tlei file:
<taglib-extrainfo>
<css-uri>app.css</css-uri> 
<tag name="myTag">
<display-name>My Tag</display-name> 
<rendering-label>{tag-name} ({name})</rendering-label> 
<small-icon>images/myTag.gif</small-icon> 
</tag>
</taglib-extrainfo>
All customization tags are optional.
4) Create the css file referenced from the tlei file above (in this example app.css in the same directory containing the tlei file).
5) Paste the following content in the app.css file:
myTag {border: 1 solid red; display: "inline"}
This will render the tag as inline (i.e as one graphical object) even if the tag has nested content.
In addition, you can use any standard css style property.
You can customize other tags in the same fashion.
If a custom tag inherits from a Struts tag, then the tag can inherit the full built-in tag customization as shown in the following example:
Suppose you have a tag named "myText" that extends the Struts html:text form field tag. To inherit the NitroX html:text customization you follow the steps:
1) insert the following in the tlei file described above:
<tag name="myText">
<inherit taglib-uid="http://jakarta.apache.org/struts/tags-html" tag-name="text" />
</tag>
2) Insert the following css rule in the css file referenced from the tlei file:
myText {m7-inherit: "input-text"; display: inline}
This will inherit the built-in css style for form text fields.
Likewise, you can inherit the other Struts tags css styles by using the following rules:
myPassword {m7-inherit: "input-password"; display: inline}
myCancel {m7-inherit: "input-submit"; display: inline}
myCheckbox {m7-inherit: "input-checkbox"; display: inline}
myRadio {m7-inherit: "input-radio"; display: inline}
mySelect {m7-inherit: "select"; display: inline}
myTextarea {m7-inherit: "textarea"; display: inline}
3) The inherited tag library file (in this example the struts-html.tld), must also be present under the WEB-INF directory.
M7 Support

Will somebody please post an Aperture-written xmp file *with* custom metadata in it - thanks.

It is my understanding that Adobe's migration tool will NOT support transferal of custom metadata from Aperture to Lightroom.
I have recently enhanced my Custom Metadata plugin to read custom metadata from Expression Media xmp, and it seems like a no-brainer to have a "preset" which can read/import/transfer custom metadata from Aperture xmp too - I just need a sample to work with - thanks.
If you don't want to post here, please send directly to me.
robcole.com - Contact Me
Rob

To attempt a wrap-up for this thread:
Aperture does NOT provide a means to save custom metadata in XMP - the initial premise of this thread was incorrect: a thank you to John Beardsworth for setting me straight. Specific question asked has been answered.
The purpose for the thread however was to learn how to get information out of Aperture so it can be gotten into Lightroom (final destination: custom metadata fields).
Here is one way to get custom metadata in Aperture to custom metadata in Lightroom, recommended if you have enough free IPTC fields to house the custom data temporarily:
* Create an applescript file with the following contents, modified to support your custom metadata fields; note: it must also be modified to specify the IPTC fields to be used:
tell application “Aperture”
    set imageSel to the selection
    repeat with i from 1 to count of imageSel
        tell library 1
            tell item i of imageSel
                set customFieldValue to value of custom tag "myCustomFieldName"
                set value of IPTC tag "myFreeIptcFieldName" to customFieldValue
            end tell
        end tell
    end repeat
end tell
Note: you must adapt script depending on your custom fields, and which IPTC fields you have free.
* Select photos in Aperture.
* Execute the script.
* Once photos are in Lightroom, with IPTC fields populated.., then in Lr's plugin manager, with 'Custom Metadata' plugin selected, click 'Transfer Metadata' button, then "follow the yellow-brick road" (you will be prompted with instructions..). Metadata will be transferred from IPTC fields to custom metadata in Lightroom.
If you do NOT have sufficient IPTC fields to use, or would rather not use IPTC fields for this, then you'd have to modify the script to populate a row in a CSV file for each photo, then use the 'Import from CSV' function in Custom Metadata plugin. I can help if it comes to this..
PS - There may be other ways as well, but maybe this is enough..
Rob

Flash "Collection Item" metadata tag?

Hi!
While creating Flash components I am using metadata tags Inspectable and Collection. This two allow me to do everything I need, in most cases. But in Flash IDE using Component Definition panel you can define much more:
For me "Collection Item" support is much preferrable than [Inspectable(type="Object"...)], because white editing Collection I can specify enumerations and Booleans -- with Objects only text fields allowed. How can I specify it in my code? Is there any documentation about additional metadata tags supported in Flash IDE?

Where do you see the metadata tag injectors? That is not a documented Flex Metadata tag that I have heard of.
A lot of frameworks create their own and you should be able to use that in both Flex and Flash Pro [assuming an AS3 framework].
If you google on Custom AS3 Metadata in Flash Pro quite a few links come up. Here is one: http://patrickmowrer.com/2010/03/03/compiling-custom-as3-metadata-flash-professional

Export custom metadata

Does anyone know a way of exporting custom metadata in Aperture? The standard export only seems to apply to ITPC data.

RedKite provided this script for exporting to a tab-delimited text file in an archived forum. Copy the script to the Apple script editor. Change "category" in the upper section and "photo category" in the lower section to the name of your custom field. Run it. To add more custom fields, copy and paste the custom field section in the lower part. Add a corresponding line to the upper part. The upper part is the column name on the spreadsheet.
This script is old, It works for the version name, file name, and custom fields. It does not work for Keywords (written into the script) or other IPTC fields written the same way. Does anyone know a script that does both IPTC and custom fields in Aperture 3 in 2013?
tell application "Aperture"
set tSelection to the selection
-- this is the header, not really necessary
set tValues to "Version Name" & tab
set tValues to tValues & "File Name" & tab
set tValues to tValues & "Keywords" & tab
set tValues to tValues & "Category" & tab
set tValues to tValues & return
--here starts the real stuff
repeat with i from 1 to number of items in tSelection
set tImg to item i of tSelection
--add Version name
try
set t to name of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add FileName
set t to the value of other tag "FileName" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add IPTC tag
set t to the value of IPTC tag "Keywords" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
try
--add a custom field
set t to the value of custom tag "Photo Category" of tImg
on error
set t to ""
end try
set tValues to tValues & t & tab
--next line/image
set tValues to tValues & return
end repeat
set f to choose file name with prompt "Choose file name..."
set my_log to tValues
set mylogfile to open for access f with write permission
set eof of mylogfile to 0
write my_log to mylogfile starting at eof
close access mylogfile
end tell

Custom metadata in Spotlight?

If you open Spotlight using Ctrl+F, you get an interface for advanced queries. Under "Kind", you can select "Other..." and Spotlight opens a list of "search attributes". It's a long list but of course not complete.
Question: is there a way to add custom metadata attributes that can be read by Spotlight? I am willing to get my hands dirty with plists and such, or perhaps there is some freeware add-on that can facilitate this?
Here's the usage scenario:
1. I can create a new search attribute for OS X files -- let's call it "foo".
2. I can attach the value "bar" to the metadata attribute "foo", e.g. for the file "myFile.txt".
3. I can write an AppleScript that takes a file name as a parameter and returns the value of the "foo" attribute. I.e., I give it "myFile.txt" and I get "bar" as the result.
4. I can use spotlight to search for "bar" and get all files with this metadata.
5. (Optional) I can use spotlight to search for "foo:bar" and get "myFile.txt".
I have looked at a bunch of things on the Net (OpenMeta, SpotMeta, etc.) but I haven't found anything yet that will do this.
Any suggestions?
TIA

Why not just use your hypothetical attribute "foo" (so long as it is unique label) as tag your files in the Spotlight Comments. Then Spotlight will find all files with this "attribute". But best use another nonce word like "foophotosofmydog" that will be completely unambiguous.
I am searching for alternative to Spotlight since, under some peculiar circumstances, the tags become "transparent", i.e. you cannot view them by command-I, but they are still searchable. Consequently, the Comments are scary to me just now.
HoudaSpot appears to be an alternative, since it allows tagging of files using OpenMeta that can be searched b Spotlight, but at I cannot see any native way to create real meta tags in OS X.
-j

Searching custom metadata

Hello all,
I have logged a bunch of footage using Adobe Prelude CC and have tagged my clips with custom metadata on ingest. I can search for and filter my clips as expected within Prelude but, upon sending the clips to Premiere I loose that ability. I can see that the custom metadata has indeed transferred over to Premiere via the metadata window but I cannot search and filter as expected.
My two thoughts are I have either logged the clips metadata incorrectly (I used the new CC custom metadata feature on ingest) or I am searching via Premiere incorrectly (through the search bar in the top left of a given bin window).
I am very new to Premiere having jumped ship after a long love affair with FCP 7, so you will have to excuse me if this is a simple case of user error.

Unfortunately, that is just not a work flow that I use or am familiar with. I don't think I can help much with this specific problem, but maybe with a work around.
My own view is that Prelude has very limited usefulness for a single editor. Using only native media, without transcoding, I don't think there's anything Prelude can do that PP can't do itself, so I just don't see the purpose of a single user spreading the work out between two different programs. Where Prelude makes sense is when you have an assistant editor, who can make selects and rough cuts in Prelude for the editor who does the real work in Premiere Pro. With two people working, then it makes sense to spread the load out to two programs.
The point I'm working towards is why not just add your keywords right in Premiere Pro?

How can I convert the metadata tags on my mp4s to xml files so that they can be read in Windows Media Center?

I have a library with almost 3000 movies and TV shows that I have fully tagged. However, I have decided to start using Windows Media Center and it does its metadata tagging through XML files. I wanted to know if anyone could tell me if there was a way to extract the metadata from those mp4s and convert them to a format that WMC could read? Thanks!!!!

iTunes can make XML playlists so it might be all you need, I made a simple one file playlist and exported it from iTunes. The result is shown below. In principle I could delete the playlist and the entry from the library, as long as I don't delete the file, then later reimport the XML playlist file. I haven't tested this particular scenario, but I assume that iTunes will read all the properties as listed unless it can read some kind of tag from the file itself in which case the current value of the tag would take precedence.
What I don't know is what media center would make of this file, or what its files look like, however assuming they have a similar structure that can be decoded then it should be possible to read data from the iTunes library and write out a text file that will make sense to media centre.
Video Test.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Major Version</key><integer>1</integer>
<key>Minor Version</key><integer>1</integer>
<key>Date</key><date>2013-09-26T23:30:26Z</date>
<key>Application Version</key><string>11.1</string>
<key>Features</key><integer>5</integer>
<key>Show Content Ratings</key><true/>
<key>Music Folder</key><string>file://localhost/E:/iTunes/iTunes%20Media/</string>
<key>Library Persistent ID</key><string>CCF046191585EA85</string>
<key>Tracks</key>
<dict>
<key>155170</key>
<dict>
<key>Track ID</key><integer>155170</integer>
<key>Name</key><string>Abbott & Costello: "Two Tens For A Five" & "Who's On First"</string>
<key>Artist</key><string>Abbott & Costello</string>
<key>Album Artist</key><string>Abbott & Costello</string>
<key>Album</key><string>Abbott & Costello: "Two Tens For A Five" & "Who's On First"</string>
<key>Genre</key><string>Comedy Clip</string>
<key>Kind</key><string>MPEG-4 video file</string>
<key>Size</key><integer>110483524</integer>
<key>Total Time</key><integer>532096</integer>
<key>Year</key><integer>1950</integer>
<key>Date Modified</key><date>2013-06-19T17:35:18Z</date>
<key>Date Added</key><date>2012-12-01T17:30:57Z</date>
<key>Bit Rate</key><integer>156</integer>
<key>Comments</key><string>www.dvdvideosoft.com</string>
<key>Artwork Count</key><integer>1</integer>
<key>Persistent ID</key><string>5AF2C490D1E065CD</string>
<key>Track Type</key><string>File</string>
<key>Has Video</key><true/>
<key>HD</key><false/>
<key>Video Width</key><integer>1136</integer>
<key>Video Height</key><integer>640</integer>
<key>Location</key><string>file://localhost/E:/iTunes/iTunes%20Media/Home%20Vide os/Abbott%20&%20Costello_%20_Two%20Tens%20for%20a%20Five_%20&%20_Who's%2 0on%20First_.mp4</string>
<key>File Folder Count</key><integer>3</integer>
<key>Library Folder Count</key><integer>1</integer>
</dict>
</dict>
<key>Playlists</key>
<array>
<dict>
<key>Name</key><string>Video Test</string>
<key>Playlist ID</key><integer>1930541</integer>
<key>Playlist Persistent ID</key><string>30BF2769C94F7F29</string>
<key>All Items</key><true/>
<key>Playlist Items</key>
<array>
<dict>
<key>Track ID</key><integer>155170</integer>
</dict>
</array>
</dict>
</array>
</dict>
</plist>
Such files are easier to interpret if opened with Notepad++.
tt2

Custom metadata tags?

Similar Messages

Maybe you are looking for