IPTC NewsCodes Standards - Metadata

Howdy,
Here is the IPTC - NewsCodes - List from the iptc.org site which lists the words used in cataloguing.
Search: View Strings Standards
love & peace,
victor
G5, 2.5 GHz   Mac OS X (10.4.4)  

Hello, kgelner
Quote: "A cool resource. Thanks much!"
I'm glad you liked it
Interesting site IPTC -- I didn't realize there are nerdier people than us.
love & peace,
victor
G5, 2.5 GHz   Mac OS X (10.4.4)  

Similar Messages

  • IPTC/XMP standard for metadata

    Does anybody know if iPhoto will ever become compatible with the IPTC/XMP standard for metadata?

    No
    And if they did they would not say
    this is a user to user discussion forum and speculation on future Apple products is expressly forbidden by the TOS that you read and agreed to when you signed up to use these forums
    LN

  • IPTC Info in Metadata Boxes?

    When you add a new metadata box to page, is it possible to have that metadata box populate itself with the City/Country IPTC info?
    I can't seem to find a way to change (add/remove) the metadata fields in the drop down menu.
    I'm trying to make a contact sheet that includes the City and Country where each photo was shot.
    Thank you,
    Kenny

    The metadata is recorded by the camera. Aperture simply reads what data the camera recorded. I'd suggest you update your camera firmware, if an update is available. My experience with this is that the camera body manufacturer's lenses are often much more reliably identified.
    Regardless, not all lens information is available for all cameras; it's currently a hit-and-miss technology.
    I'd say don't worry about it much.

  • [ANN] GeoIPTC 1.0 : geocode your images using metadata standards (IPTC and XMP)

    Hello,
    GeoIPTC is an innovative tool to add geographical identification to your images (geocoding) according to IPTC and XMP metadata embedded in images.
    GeoIPTC reads all IPTC and IPTC Core metadata embedded in an image, isolates localisation data (City, Location, Province/State, Country Code and Country Name), then sends a request to a Geocoding Web Service and finally gets latitude/longitude coordinates.
    To say it briefly: GeoIPTC gets geographical information from the postman address embedded in image.
    Main features
    * Gets full sets of image standard metadata
    * Automatically gets longitude/latitude from widely used Geocoding Web Services like Google Maps, Yahoo! Maps or GeoNames.
    * Locate automatically images on Maps Services like Google Maps, Yahoo! Maps and MapQuest
    * Generate automatically KML or KMZ placemarks and locate single (one image) or multiple (many images) placemarks on Google Earth with full IPTC/IPTC Core metadata
    * Set automatically single or multiple images with appropriate Exif GPS coordinates
    More information and download:
    http://www.geoiptc.com/EN/Index.html
    With best regards
    Patrick Peccatte
    www.softexperience.com

    Note the last paragraph in the original post which explains how Flickr handles resolution changes without breaking the rectangles. Perhaps a more straightforward approach would be to store both the rectangle coordinates for each rectangle AND the image's width and height at the time the rectangles were created. Then if the image is scaled, the rectangles can be scaled accordingly. For example, if a rectangle is at x=100,y=200,w=50,h=70, the "original dimensions" are 1000x2000, and the image's current dimensions are 500x1000, then an application could assume the image has been scaled down by (500/1000=) 0.50, and so the x,y,w,h of each rectangle could also be multiplied by 0.50 (x=50,y=100,w=25,h=35). I'd recommend storing floating-point values so that multiple scalings don't make the rectangles "creep".
    Of course, it is possible that really the image was cropped rather than scaled, but fairly unlikely you would happen to crop it the same percent in both directions. Even if an image is cropped, someone could manually repair the rectangles by sliding and scaling them until the fit back on the faces (unless most of the faces were cropped off).
    A rectangle-aware application could scale and translate the rectangles during a crop or scaling operation, but other applications could still survive scaling if they at least preserve the XMP tags as-is.

  • Question Regarding IPTC Metadata

    I've migrated my iPhoto library into Aperture for the expanded geotagging and metadata support, and it was exhausting. (I had Keyword Manager for iPhoto, and Aperture didn't preserve my hierarchy of keywords, though it imported everything else beautifully.) Anyway, I'd like to leave myself open to the possibility of switching to a different program if necessary, so I'm wondering what information would carry over. My questions are as follows:
    1) In the "Write IPTC Metadata to Masters" option, what exactly gets written - I assume everything under the IPTC core, right? (In particular, I've modified the Country/State/City/Location fields, keywords, comments, creator, and source, and it would be a pain to redo all these for 45,000 pictures.)
    2) I presume the aforementioned option only alters the metadata and preserves the original image intact; is this correct? Would there be any repercussions to writing these changes to the masters instead of just keeping them within Aperture's database? It seems a lot of users here insist their originals remain completely untouched.
    3) Is there an IPTC standard for hierarchal keywords, or will I have to recreate the keyword structure in any photo management software I use? (I've experimented with a trial version of Lightroom 3, and I don't even see a way to manage keywords in it...)
    4) Can face tags be written to the metadata? I assume Aperture has its own proprietary format for tagging faces on the photo, but would there at least be an IPTC standard field in which you could list the people tagged in the photo?
    In short, I switched to Aperture because iPhoto's tagging options were inadequate for properly organizing my 45,000 photo library. As I did some research on how to effectively make the transition, I found there was a lot more to this "digital asset management" concept that I realized, and so I'm hoping to get some input from some more experienced users. I'm a real stickler for precision and logic in my organization, and it looks like the IPTC core standard has all the fields I need. Thanks in advance!

    Just another update ... I did some experimenting and found that the "Write IPTC Metadata to Masters" command does at least write the fields I mentioned in the original post. (Those were the only ones I changed on the test photo.)
    Does anyone know offhand if a manually changed date will get written to the master, or will the file still have its original date? (I could test this too, but if someone knows, then I don't have to.)
    Also, most importantly, does the option actually resave the entire master with the updated info, or does it somehow just write the metadata? I ask this because I've read that jpegs lose some data to compression every time they're saved, and I'm wondering if writing those tags will cost the photo some quality.

  • Display the filed instructions (that´s under IPTC Core metadata).

    Hi all
    I´m new on programing scripts in Photoshop..and tried everything but was not able to change the script below. Let´s explain this script is found at Adobe Photoshop default folder and works to show the Camera Model used to the current image.
    Now..the challenge...I want to change the scripts so when you run the it shows a field called Instructions (that´s located in the IPTC Core XMP metadata Tab. (In Photoshop > open an Image > go to File menu > File Info option and see the IPTC Core Tab > Instruction field).
    Can anyone please help me to change this lines. It could look very simple for you but it´s actually very difficult to me; This base-script is what I have and works fine to display the camera model:
    try {
         var xmpString = activeDocument.xmpMetadata.rawData.toString();
         var tiffModelLength = ('<tiff:Model>').length;
         var tiffModel = xmpString.search( '<tiff:Model>' );
         var tiffModelEnd = xmpString.search( '</tiff:Model>' );
         var tiffModelStr = xmpString.substr( tiffModel + tiffModelLength, tiffModelEnd - tiffModel - tiffModelLength );
         if ( tiffModelStr.length > 0 ) {
              alert( tiffModelStr + localize ( '$$$' ) );
         // check the exif
         var exifModelStr = '';
         var exifData = activeDocument.info.exif;
         for ( var i = 0; i < exifData.length; i++ ) {
              if ( exifData[i][0] == 'Model' ) {
    } // try end
    catch( e ) {
    // always wrap your script with try/catch blocks so you don't stop production
    // remove comments below to see error for debugging
    // alert( e );
    Thank you a lot for any help.
    Gustavo.

    Here is one of X's functions that should give you the information..
    #target photoshop
    var xmp = activeDocument.xmpMetadata.rawData;
    var Instructions = parseMetadata(xmp,"photoshop:Instructions");
    alert(Instructions);
    function parseMetadata(xmp, tag) {
      var re = new RegExp('<' + tag + '>(.+)</' + tag + '>');
      var m = xmp.match(re);
      if (!m) {
        re = new RegExp("<[^:]+:" + tag + ">(.+)</[^:]+:" + tag + '>');
        m = this.xmp.match(re);
      return (m ? m[1] : '');

  • Importing files with embedded IPTC metadata - Workaround?

    I was hoping the the "metadata improvments" that Apple delivered with Aperture v.1.1 would include the ability to import legacy files with IPTC and XMP metadata embedded by Photoshop, iView, Photo Mechanic, and other similar programs.
    Unless I am missing something that ability is still not a part of the Aperture program.
    I really like Aperture and think Apple has got many things right in the new program. I would like to make it my primary tool for digital image management. That would require the ability to read into the Aperture Library the metadadta written by other programs.
    Does anyone have a workaround for importing files that lets other programs IPTC tags be imported or connected with the files.
    Thomas
    G5 dual 2.7Ghz   Mac OS X (10.4.6)   http://www.thomaswhitephoto.com

    Gilles-
    I think your problem is likely that you have the option to stack the copy with the original turned on. First, right-click on one of these photos and go to the stacking menu. If Unstack is not grayed out then you have a stack -- select Unstack to reveal all copies.
    To change the automatic stacking of edited copies from Photoshop, when you next choose to edit a file, in the bottom left corner of the dialog is the check box for unstacking. Clear it, and that choice should "stick" until you change it again.
    Hope this helps!
    Tony

  • How to Customize the Rows in Viewer Metadata?

    I've been mucking around creating some new, custom views for my metadata, in particular how it displays under images in the Viewer. I notice that in some of Apple's pre-set views ("Viewer - Expanded" for example), there's a top row which displays selected bits of information in a larger font size than the standard rows immediately below. In the "Name & Caption" pre-set, the image's Name is shown in this larger top row, while the Caption is displayed below in the smaller font size. Also, turning the "Show Labels" option on or off only seems to affect the lower rows, not the upper one.
    In any case, my question is: how can I specify which bits of metadata get displayed in that top row (and therefore in the larger font), and which get displayed in the lower rows?
    For instance, one custom view I'd like to create is one in which the File Name and the Caption get displayed in the larger top row, while other information such as Date, Master Pixel Size, and some other fields get displayed below in the smaller font size.
    I've figured out how to tell Aperture which specific bits of metadata I want it to display, but Aperture seems to have its own specific ideas about which bits get displayed in which row (and therefore at which size). Is there no way I can affect this? And does that top row have anything to do with the "Summary" button at the bottom of the Metadata inspector pane (a connection which so far I've been unsuccessful in trying to establish)?
    Any suggestions appreciated.
    Thanks,
    John Bertram
    Toronto

    Aperture looks for very specific EXIF, IPTC, and "Other" metadata fields in a particular set. If they are there then Aperture will make them large and put them in the top row. The fields are slightly different for the viewer and the browser last time I did an inventory (yes I am that ridiculously OCD on some things). If it is not one of those fields they are put in a smaller font on the second row in the same order they are defined in the metadata view.
    If you would like to inventory them yourself just open up the metadata inspector go to the set that is being displayed and one by one check and uncheck each field and each category, they update real time.
    RB
    When I get around to it I will update this to reflect what fields do what but that will probably change if we ever see a real update again.
    [Aperture Metadata Display|http://photo.rwboyer.com/2008/08/aperture-and-metadata-display>
    Message was edited by: rwboyer

  • Exporting Metadata

    I've created custom metadata views and presets for cataloging my images. Is it possible to export this metadata into an Excel spreadsheet as a CSV or TSV file? File/Export/Metadata exports standard metadata, but not my custom fields and entries. Or, is it possible to export XMP sidecar files and somehow import those into Excel? All that data is there somewhere within Aperture - please help me get it out and into a spreadsheet! Thanks.

    You have to use some Applescript, but it's a relatively simple script.
    tell application "Aperture"
    set tSelection to the selection -- this gets all the Versions currently selected
    set tValues to ""
    repeat with i from 1 to number of items in tSelection -- now loop through selection
    set tImg to item i of tSelection
    set tValues to tValues & "Version Name: " & name of tImg -- add the name
    try
    set tValues to tValues & "Aperture: " & value of EXIF tag "ApertureValue" of tImg -- add the aperture
    set tValues to tValues & tab -- replace with "," for comma-delimted values
    end try
    try
    set tValues to tValues & "Shutter: " & value of EXIF tag "ShutterSpeed" of tImg
    end try
    set tValues to tValues & return -- make a new line for each image
    end repeat
    end tell
    Copy and paste into Script Editor (in Applications/AppleScript) and hit the Run button, in the bottom pane you'll get the results. Note that you'll have to change 'EXIF tag' to 'custom tag' for your custom tags, and to 'IPTC tag' for IPTC data.
    The 'try/end try' bits are in there so that the script doesn't fail if it comes up against an empty tag.
    Ian

  • Automatically populate metadata field with file name?

    Hi, I'm not sure if this is possible...
    I'm working with many large batches of .jpg files, and am running them through Bridge in order to add metadata according to my client's guidelines.
    For every single file, my client requires that the "Description" field in the IPTC Core section of the metadata is filled with the full filename, as it would appear in the Finder, including the .jpg extension.
    Currently I'm copying every file's name and pasting it into the Description field. Does anyone know of a good way to automate this task? Since each file name is different, a standard metadata template isn't meeting my needs.
    If anyone knows of a good way, I'd be very glad to know! Thank you.
    Chad
    Adobe Bridge CC 6.0.1.6  /  Mac OS X 10.9.1

    Awesome, That works really well.
    I found this on the forum based on your answer.
    Puts the file name in the field and takes off the .pdf extention.
    var
    fileName = event.target.documentFileName;
    //removing the file extensionvar vDot = fileName.length-4;
    //apply the value to the TxtFieldthis.rawValue= fileName.substring(0,vDot);

  • Using Title/Caption In Metadata...

    While I love the develop module in LR I would have to say I am finding the library module most difficult to figure out. Presently I am trying to decide the best way to identify images upon import. For instance, I do a great deal of boat photography and would like to label images with the name of the boat upon import. In the metadata panel there is both a Title and Caption entry line and I would guess that the Title line is the best spot to insert the boat name. At the same time it's not at all clear to me what sort of information is meant by the term Caption. Which of the two spots would be best for entering the boat name or other identifying text. Also, if I had a series of shots of the same boat is there a way for me to enter the name once and have it applied to all the selected images.
    In the Mom/Pop iPhoto all one had to do is enter the boat name in the comments panel. Is there a simple straight forward equivelent in LR3?
    Thanks!

    The short answer: I recommend putting the boat name in Caption, not Title.
    A longer answer: Industry standards define the use of Title and Caption reasonably precisely, but many tools, communities, and workflows interpret them differently. If you anticipate sharing your photos with others, you might scope out which tools will be used to access the metadata of the photos and how they handle the Title and Caption fields.  Take some sample photos, set their Title and Caption in LR, do Save Metadata To File, and then view the file in the other tools.
    The IPTC industry standards define Title, Caption/Description, and Headline as:
    Title: A shorthand reference for the digital image. Title provides a short human readable name which can be a text and/or numeric reference. It is not the same as Headline. Enter a short verbal and human readable name for the image, this may be the file name. Many use the Title field to store the filename of the image, though the field may be used in many ways. Formal identifiers are provided by the Digital Image Id, or the Registry Entry property of the IPTC Extension.
    Caption (Description): A textual description, including captions, of the image. Enter a "caption" describing the who, what, and why of what is happening in this image, this might include names of people, and/or their role in the action that is taking place within the image.
    Headline: A brief synopsis of the caption. Headline is not the same as Title. Enter a brief publishable synopsis or summary of the contents of the image
    Those standards were originally defined years ago for professional press photographers and later expanded to encompass many different uses.   But for better or worse, there exist many tools, communities, and workflows that use those fields in ways different than prescribed by the standards. 
    For example, when you upload a photo to Flickr, it will populate its Title field from the photo's Title if it exists, otherwise it uses the filename.   But many (perhaps most) Flickr users use its Title field as a short caption (e.g. like a Headline), and Flickr's design encourages that. 
    As another example, Windows Live Photo Gallery will show as its "Caption" the metadata Title if it exists, otherwise the metadata Caption/Description. When you change its "Caption" field, it will write it into both the metadata Title and metadata Caption/Description fields.
    So depending on the intended audience and tool set of your photos, you may choose to adjust your use of Title and Caption to better fit in with their way of doing things.

  • IPTC Date from the file properties (EXIF) at import?

    Is it possible to fill IPTC Date Created Field from the raw-file properties  at import to LR4?
    It would be nice – and time saving.

    Thank You  Geoff & Ian
    My mistake. I had a checkmark in the empty date-field in my standard metadata-preset. I now understand, that the date-field shall be left blank with no checkmark in the preset to get the date correct in IPTC. Thank You again.

  • Metadata Methodology in SRM 7.0

    Hello,
    I'm a new developer to SAP and even newer to SRM. I have a requirement to modify a dynpro to default some values and hide some other fields in the SC line item dynpro specifically /SAPSRM/WDC_DODC_SC_I_LIM.
    We've determined that Metadata Methodology best suits our need for this enhancement. I'm not familiar with the technique and would like to know if the SRM guru's out there have any suggestions on where to look. I'm assuming the changes I'll be making are from the SE80 perspective.
    Any information provided will be very helpful and result in p-o-i-n-t-s that's not enough perhaps a bottle of Scotch will do.
    Many Thanks!
    Justin Kraus
    justkr AT vsp DOT com
    916-851-4402

    Hi,
    - Adding Custom fields in Item is handled by Standard metadata -
    1,  Add custom filed to structure INCL_EEW_PD_ITEM_CSF_SC and INCL_EEW_PD_ITEM_CSF
    2,  Metadata can be maintained in views in SM30 for custom fields in Item details, Account Assignment, and Header fields in SC,    
         PO, INV etc. eg: /SAPSRM/V_MDF_IC for adding custom fields in SC item details.
    3,  Field control can be done by adding u2018Dynamic customer control classu2019.
    -Hiding the fields-
    1. Open the relevant Shopping Cart in Portal
    2. Right click on the Field and find out the Technical Details of the Component
    3. Click on Technical Help to see the Technical details of the component and get the field id .We can make use of this field information to make the Meta data changes in the maintenance View.
    4, Go to Transaction SM30 and enter View /SAPSRM/V_MDF_IC
    5, Fill the Field name  and Business Object BUS2121 (For shopping Cart) ,make the field invisible on the screen.
    Now SAVE the entry. (Ensure to keep Field Visible, Enabled & Required properties as unchecked as per your requirment)
    Hope it will be useful
    Regards,
    Neelima

  • Missing Selection in Lightroom 3.2, Metadata

    In the local Lightroom 3.2 Documentation it indicates that the options for the Library, Metadata, Options include …
    Home / Using Photoshop Lightroom 3 / Organizing photos in the catalog / Viewing and editing metadata
    View photo metadata
    In the Library module, the Metadata panel displays the filename, file path, rating, text label, and EXIF and IPTC metadata of selected photos. Use the pop-up menu to choose a set of metadata fields. Lightroom has premade sets that display different combinations of metadata.
    With one or more photos selected in the Grid view, or with a single photo selected in the Filmstrip in Loupe, Compare, or Survey view, choose any of the following from the pop-up menu at the top of the Metadata panel:
    Default
    Shows the filename, copy name, folder, rating, text label, and a subset of IPTC and EXIF metadata.
    All
    Shows the filename, copy name, file path, rating, text label, and all EXIF and IPTC metadata.
    All Plug-In Metadata
    Displays custom metadata created by third-party plug-ins. If you don’t have any plug-ins installed, filename, copy name, and folder are displayed.
    EXIF
    Shows the filename, file path, dimensions, and EXIF camera metadata such as Exposure, Focal Length, ISO Speed Rating, and Flash. If your camera records GPS metadata, the information appears as EXIF metadata.
    EXIF and IPTC
    Shows the filename, size, type, location, metadata status, as well as all EXIF and basic IPTC metadata.
    IPTC
    Shows the filename and basic IPTC metadata: Contact, Content, Image, Status, and Copyright metadata.
    IPTC Extension
    Shows the filename and IPTC metadata for model and artwork releases and other types of licensing rights.
    Large Caption
    Shows a large caption edit box and the copyright box.
    Location
    Shows the filename, copy name, folder, title, caption, and location fields.
    Minimal
    Shows the filename, rating, plus Caption and Copyright metadata.
    Quick Describe
    Shows the filename, copy name, file path, rating, and the following EXIF and IPTC metadata: Dimensions, Date Time, Camera, Title, Caption, Copyright, Creator, and Location.
    In the Metadata panel, if an IPTC metadata field displays an arrow, clicking the arrow is a quick way to find and view all photos containing the specific metadata.
    If multiple photos with different metadata settings are selected, the metadata fields display <mixed>. To show the metadata for the photo that’s targeted (active) within the selection, choose Metadata > Show Metadata For Target Photo Only. If more than one photo is selected in the Filmstrip in Loupe, Compare, or Survey view, the Metadata panel displays metadata only for the active photo.
    The 3.2 version of lightroom does not include the ALL choice. Is this correct?
    Thanks

    The All option does appear to be missing in 3.2 (not sure if it was in 3.0 or not).  In any case, I usually develop my own templates manually.  You can also try out the plug-in at: http://regex.info/blog/lightroom-goodies/metadata-presets which should generate the desired template (including an "all" template) if you so desire.  I am not related to this developer but you might take a look at his site for other plug-ins that might benefit your workflow.
    Jeff

  • Select Button beside custom metadata field on Check In Form

    Hi
    In Oracle Content Server 10gR3, is there a way to add a "Select" button to User Alias Applet for a new Meta data field on New Check In Form? I tried creating a component but I don't see a select button being shown up. The button does shows up if it's a standard metadata fields but not for the custom one. Here is the component code. Any idea what I am doing wrong and how to fix it.
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>
    CustomMetaData htmlIncludeOrString
    </title>
    </head>
    <body>
    <@dynamichtml std_meta_fields@>
    <textarea name="xClbraAliasList" rows=3 cols=40 wrap=virtual></textarea>
    <input type="button" value="Select..."
    onClick="popupSelectAlias(document.Checkin);">
    <script language="JavaScript">          
         var aliasForm;
         function popupSelectAlias(frm)
              var selUser = document.selectAliasApplet;
              aliasForm = frm;
              selUser.createFrame();
         function setAliasString(val)
              if (val.length == 0)
                   return;
              var str = aliasForm.xClbraAliasList.value;
              str.trim;
              if (str.length > 0)
                   str += ",";
              str += val;
              aliasForm.xClbraAliasList.value=str;
         </script>
         <applet name="selectUserApplet"
        code=com.intranetsol.utilities.SelectUserApplet.class
          codebase="/idc/common/"
         archive=suapplet.zip
        id=selectUser
        width=0
        height=0
         MAYSCRIPT>
              <param name=CGI-URL value="/idc/idcplg">
              <param name=JsDisplaySeparator value=",">
              <param name=IsPaged value="1">
              <param name=IsUserList value="1">
              <param name=JsFunction value="setUserString">
    </applet>
    <applet name="selectAliasApplet"
        code=com.intranetsol.utilities.SelectUserApplet.class
          codebase="/idc/common/"
         archive=suapplet.zip
        id=selectAlias
        width=0
        height=0
         MAYSCRIPT>
              <param name=CGI-URL value="/idc/idcplg">
              <param name=JsDisplaySeparator value=",">
              <param name=IsPaged value="1">
              <param name=IsAliasList value="1">
              <param name=JsFunction value="setAliasString">
    </applet>
    <@end@>
    </body></html>
    Then I tried using the same code as above but instead used the built-in dDocType to show a "Select" button. This works but the button obviously shows besides dDocType but when I try for custom metadata as shown above it doesn't. Here is the sample code for dDocType:<html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>
    CustomMetaData3 htmlIncludeOrString
    </title>
    </head>
    <body>
    <@dynamichtml std_doc_page_definitions@>
    <$include super.std_doc_page_definitions$>
    <$include custom_modify_comments_definitions$>
    <@end@>
    <@dynamichtml custom_modify_comments_definitions@>
    <$if isCheckin$>
    <$xComments:isHidden = 1$>
    <$xComments = "some preset and hidden comments"$>
    <$elseif isUpdate$>
    <$xComments:isInfoOnly = 1$>
    <$endif$>
    <@end@>
    <@dynamichtml compute_std_field_includes@>
    <$include super.compute_std_field_includes$>
    <$if fieldName like "dDocType"$>
    <$if isCheckin or isUpdate$>
    <$fieldEntryInclude = "custom_doc_type_popup_field_entry"$>
    <$endif$>
    <$endif$>
    <@end@>
    <@dynamichtml custom_doc_type_popup_field_entry@>
    <input type="text" name="dDocType" value="<$fieldValue$>">
    <input type="button" value="Select..."
    onClick="popupSelectAlias(document.Checkin);">
    <script language="JavaScript">          
         var aliasForm;
         function popupSelectAlias(frm)
              var selUser = document.selectAliasApplet;
              aliasForm = frm;
              selUser.createFrame();     
         function setAliasString(val)
              if (val.length == 0)
                   return;
              var str = aliasForm.xClbraAliasList.value;
              str.trim;
              if (str.length > 0)
                   str += ",";
              str += val;
              aliasForm.xClbraAliasList.value=str;
         </script>
    <applet name="selectAliasApplet"
    code=com.intranetsol.utilities.SelectUserApplet.class
         codebase="/idc/common/"
         archive=suapplet.zip
    id=selectAlias
    width=0
    height=0
         MAYSCRIPT>
              <param name=CGI-URL value="/idc/idcplg">
              <param name=JsDisplaySeparator value=",">
              <param name=IsPaged value="1">
              <param name=IsAliasList value="1">
              <param name=JsFunction value="setAliasString">
    </applet>
    <@end@>
    </body>
    </html>
    Can someone please let me know what is in my above code that I am missing that is preventing the button not being shown in-front of the custom metadata field.
    Any help would be greatly appreciated.
    Thanks
    Edited by: guest0012 on Aug 29, 2009 4:24 PM

    Interesting!
    You'll need a component. You already mentioned you had a custom metadata field. You will also need to add a counter to the counters table for your component. During a check in you will need to fetch the next value from the counters table, increment the counter and store the new number back in the table. The year portion of the id is easy, get the current year and grab the last two characters. Then, put this all togther to get the data for your metadata field.
    The big question now is where in the check in process will you do all this? You will need something called filters probably. Maybe addFiles, maybe validateStandard, there are several that this could work with.
    Check out the how-to-components:
    http://www.oracle.com/technology/products/content-management/ucm/samples/index.html
    -Jason
    http://www.corecontentonly.com

Maybe you are looking for

  • Time machine won't back up external hard drive

    Hello, Due to my internal memory becoming full, I have connected an external hard drive to store my iPhoto Library. There is no problem with this however, I cannot seem to get Time Machine to back up the external drive. It is on the "excluded" list,

  • UTL_FILE & User Input: Case Sensitive File Names

    Hi. I'm trying to reduce problems due to the whether the user uses upper or lower case or combo of them in entering file names. Scenario is: Existing file to be read: Orig_File.Txt (file name changes daily) Output to be saved into file: RESULTS_FILE.

  • Error: ORA-01436: CONNECT BY loop in user data.... with EnableVersioning

    Hi everyone, i'm having some troubles when i execute DBMS_WM.EnableVersioning() procedure for all of the tables from my database. This is the sql line.... EXEC DBMS_WM.EnableVersioning('SAN.SAN_AMPLIAC_ANULAC, SAN.SAN_ANALISISCALIDAD, SAN.SAN_ANALISI

  • Encryption problem

    We have Endpoint and ifolder on Dell Laptops models D8300 and E6500. The folder encryption works fine on the E6500. When I try to install on a D830 and use the encryption feature when I try to rename a file or save a file I get the following error "

  • M-audio profire 610 any issues with snow leopard?

    anyone using profire 610 with snow leopard?...any issues?..