Missing caption metadata in Export Version

I have a new Canon SX260. When I export version from Aperture 3.3.2, caption info isn't included in the exported file. Location and EXIF are included. Exported versions from my older Canon S2IS and from my iPhone do have caption info.  I can export the metadata into a text file OK. Export preset has "include Metadata" checked. I would expect that Aperture creates a new JPEG with space for all the metadata even if the original file didn't have the space.  Any suggestions to getting the caption included in the exported version?

In a separate thread, this solution was provided.  Now all the captions that I exported show up int he caption field when I re-import the photos.
Re: Exports Don't Include IPTC/Copyright Info
Nov 8, 2012 6:39 AM (in response to jas)
I had jpg (not raw) images in Aperture from both a Nikon D5100 and a Nikon AW100. I added captions to the images and then exported them as jpegs. The D5100 jpgs show the caption under Preview, the AW100 jpg do not.
I found a work-around using the free program exiftool (google it) and Terminal.
In terminal I changed to the folder which contained my AW100 images and then entered this command to re-write all the IPTC data.
exiftool -iptc:all= -tagsfromfile @ -all:all -unsafe  ./

Similar Messages

  • Control metadata at exported versions

    how to export versions with iptc annonations but without exif camera data.
    it’s only possible to choose between export with or without metadata, but not to control which metadata is included in the exported version.
    sometimes i prefer if clients don’t see my camera exif infos.
    hope there’s a solution in aperture. sure i could contoll it afterwards with other software, but it should be possible in aperture.

    Same problem here. In one project 4 out of 33 pictures were completely off the mark. The common factor seems to be that the corrupted images had been cropped, and Aperture messed up the area to crop at export time. Exporting them individually afterwards worked fine. Exporting two other projects with non-cropped images worked fine.
    As this is the kind of processing I intended to use Aperture for, it is very annoying to say the least. I was about to buy the non-trial version tomorrow, but I now hesitate a lot - especially as I have not got any answer to my question in http://discussions.apple.com/thread.jspa?threadID=1402056&tstart=0 , which potentially could have achieved similar things using AppleScript.
    Did anyone log a bug report for this yet?

  • Missing file number suffix metadata when exporting

    Hello All,
    I export files from Lightroom 2 (LR2) using custom filenames that include file number, i.e. "Original number suffix", metadata. This metadata is not being picked up by the export module and will therefore not be included in the exported filename. This happens with files that have been edited in Photoshop (CS3), but not with the original DNG files.
    So if I have a master file named "Davison-20080809-1234-Master.psd", I in Lightroom 1.x (LR1) I set up a custom filename scheme in the export dialogue box that will export the master as "Davison-20080809-1234-BW-Web.jpg", or similar. This has worked with no problems to date.
    In LR2, when I look at the Example field under File Naming in the Export dialogue, I see only "Davison-20080809-BW-Web.jpg"--the original number suffix is missing along with one of the hyphens around it. When I create a custom file naming scheme with only the "Original filename suffix" metadata in it, it shows "_.jpg" in the Example field.
    It looks like maybe two things are happening.
    In LR1, if a piece of metadata was missing, it would still export a filename with all the hyphens around the missing data, so I would get "Davison-20080809--BW-Web.jpg" if the number suffix were missing. Someone probably tweaked that in the new version of Lightroom so that the unsightly double hyphenation would not appear. So this doesn't look like it's related to the problem.
    The second thing that appears to be happening is that Lightroom 2 is either not exporting (in file metadata) or not tracking (in the LR catalogue) the number suffixes. I've looked for the number suffix in Photoshop's metadata and it's not stored in the metadata at all. When I copy a Photoshop file with a suffix that does export correctly in LR2, rename the file "Test-20080809.psd" and import it into LR2, Lightroom parses the date (YYYYMMDD) as the number suffix and "20080809" is what I get when I export that file. This indicates that LR1 and LR2 store the number suffix in the catalogue and for some reason LR2 is not preserving the number suffix in the catalogue metadata when a file is edited in Photoshop.
    So has anyone else run into this problem? Or is someone interested in reproducing it? It looks like a bug to me.

    I'm also running into this same problem. For what it's worth, when I import my RAW files (as DNGs), I rename them using a naming scheme which looks like the following:
    (2008-08-13) -019- (7108).dng
    This scheme is created with the following elements (separated by line-breaks):
    custom date formula
    import number
    original file suffix
    In Lightroom 1, I had no problem. Now, I'm wondering if the parenthesis after the end of the file suffix is what's causing Lightroom 2 to think that there is no suffix?

  • Have been trying to export versions to a friend in the UK as JPEG. He receives them as bmp and no Metadata. Tried all the JPEG settings in  Image Export with no success.

    Have been trying to export "versions to a friend in the UK as JPEG. He reseives them as bmp with no Metedata. Have tried all the JPEG settings in Image export with no success.
    Nelson

    Ernie-
    Thanks for responding...but still have a oroblem. Here's what I'm doing:
    In Aperture I choose a "version" that has been Adjusted (croped, etc.).
    - Go to "File"...'Export"..."Version"
    - In next window for "Export preset" I choose "JPEG-Fit within 1024x1024"
    - Click on "Export version"
    The exported version then showes up in "Finder" under "Pictures"
    - Next I open "Mail" (version 5.2)
    - Adderss email to friends in England.
    - Click on attachment (paper clip)
    - Choose my "version" from "pictures"
    - Back in Mail, click on "Format"..."Make Plain Text"
    - Send
    My friends receive it as "bmp", not JPEG, with no Metadata.
    If I do the same procedure but under "File" choose "Export Master", they receive it as JPEG and also the Metadata.....BUT, of course, no Adjustments, such as croping, that were made to the "Version".
    What am I doing wrong? Is there any way to save the "Version" as a "Master" and then send it as a "Master"?
    Thanks,
    Nelson

  • Exporting version with metadata

    Hi there,
    this is probably an easy question. If I have a file (RAW or JPG), make some changes on it using aperture, including changes in the metadata such as adding tags and possibly GPS data, then how do I export the edited version so that the metadata of the export reflects the changes I have made within aperture?
    Currently I command click on the photo and ask to "export version". I select the "JPG - original size" option, which, upon inspection, has the box "include metadata" ticked. But the exported file only has the metadata that came from the camera. Keywords are always gone and GPS data is often (?) gone.
    Can anybody help me with this?
    Thanks a lot,
    Gil

    Apologies. Just found an earlier thread which deals with this bug in aperture:
    http://discussions.apple.com/thread.jspa?threadID=1674375&tstart=0
    Gil

  • Poor image quality on exported version

    I am trying to export versions of my photos to a folder on my external drive. Every time I do this the resulting jpg is washed out and has poor resolution + a ton of noise. The resulting image is substantially lighter than the images in my aperture window, yet the histogram does not indicate that the images should be that light or washed out.
    The images are all starting as RAW images. The export settings are for image quality 12, 300 dpi, sRGB, original jpg. I have onscreen proofing turned on and set to sRGB. My print lab said that the image quality could be 10, but when they looked so horrible I bumped them up.
    I had Aperture for a long time before upgrading to Aperture 2 in March. From March to August I did not have any problems, so this is a more recent problem. I have not yet upgraded to Snow Leopard. Please help!!! Thanks!!!

    Hi
    a. make a DiskImage first and test this with Apple DVD-player.
    (File menu and down "Make a DiskImage")
    b. I only use streamingDV - no .m4v or like (may be it works - I don't know)
    else
    *Not knowing the origin to Your problem - General approach when in trouble is as follows.*
    • Free space on internal (start-up) hard disk if it is less than 10Gb should rather have 25Gb
    • Hard disk is untidy. Repair Permissions, Repair Hard disk (Apple Disc Util tool)
    • Delete iDVD pref file - *or rather start a new user/account* - log into this and re-try
    iDVD pref file resides. Mac Hard Disk (start-up HD)/Users/"Your account"/Library/Preferences and is named.
    com.apple.iDVD.plist
    While iDVD is NOT RUNNING - move this file out to desk-top.
    Now restart iDVD.
    • Program miss-match. iDVD 5.0.2, Mac OS X.4.11 AND QuickTime 7.5.5 - is OK - DON’T work under Leopard
    • Program miss-match. iDVD 6.0.4, Mac OS X.4.11 AND QuickTime 7.5.5 - is OK (might work under Leopard)
    • Program miss-match. iDVD’08 v. 7.0.1, Mac OS X.4.11 AND QuickTime 7.5.5 - is OK (might work under Leopard)
    • iDVD (08) v7 Locate theme folder. Move out iDVD1, iDVD 2 and eventually iDVD4 folders to desktop - re-try
    • Try a Cleaning CD/DVD that cleans the laser lens on the DVD burner/player
    iDVD 6.0.4 and iDVD 7.0.1 are compatible with Mac OS X 10.5 Leopard
    Last resort. from Craig. Solved the problem!! Finally!!
    I deleted every iDVD application and folder from my boot drive,
    emptied the trash and then installed iDVD 08 using the customize option
    and I am up and running.
    If You do a re-install be sure to get rid of all iDVD old parts AND then EMPTY the Trash-basket !
    Yours Bengt W

  • Problems with captions in the exported file

    I export my sequence as a quicktime file and the captions should be embedded in the export file. But the exported quicktime file doesn't show the captions. Who can help?

    Exactly what version of Premiere are you running?
    What type of captions? CEA-608? CEA-708? Teletext?
    When the sequence is loaded in the Timeline, can you see the captions in the Program Monitor?
    When you say "captions should be embedded in the export file," I assume that means that on the Captions tab in the Export Settings dialog you set Export Options to "Embed in Output File." Please confirm.
    How are you checking for captions in the exported clips? What player? Have you enabled caption display in it?

  • Exporting versions won't work

    Must be something simple that I am missing but when I try to export a version, I do not get the next pop up screen. Simply nothing happens. I am able to export master files with no problem. Do I need to toggle a box in preferences somewhere or what am i doing wrong??

    The export options I documented for my own use are as follow:
    1. Select Closed Stacks
    Export Masters: masters only
    Export Versions: top image in stack, whether master or promoted version
    2. Select All Items In Open Stack
    Export Masters: masters only
    Export Versions: masters and versions
    3. Select Only Versions in Open Stack
    Export Masters: masters only
    Export Versions: selected versions only
    See if one of those helps with your exporting of versions.

  • Export Versions not in viewer

    When I export and save a new version of a vile how come I can't see it in the viewer? Do i have to reimport it or am I missing a setting?

    One good workflow with Aperture is to export Versions when needed, _and get rid of them_.  The Aperture Library is your repository of your Images.  If you need another shareable file of an Image, export it anew.
    This shouldn't be taken as inviolable.  I regularly create framed Image "post-cards" that I for emailing.  I create these by exporting using the BorderFX plug-in, and I put them all in a Finder folder called "Images for emailing".  (I have assigned a Finder "Folder Action" to auto-create a new message from each file that goes into this folder.)  I do leave these there.  They are relatively small files, and I regularly re-use them once or twice.  When I want to see what's in that Finder folder, I simply view it in Finder using the "Show as Icons" view.   (Note that if I didn't want the border {and watermark}, there are simpler ways to email Images.)

  • Cannot Export Versions with Aperture 3.3

    After upgrading to Aperture 3.3, I lost the ability to Export Versions of my files. Exporting Originals works just fine, but I need to I export jpegs for my work. What I end up getting now is a jpg with a totally black image. The metadata is intact and the size and jpeg format are correct, but the image is just black. I have already tried Repairing Permissions and Repairing the Database in Aperture with no change. I have not yet tried "Rebuild Database" but I do not think that is the problem because I am able to Export images from my Aperture Library files using iPhoto without a problem. Please help.

    I am exporting with a preset that I have set up. Here are the settings:
    Image Format: JPEG
    Image Quality: 10
    Size To: Fit Within (Pixels) Width 1024 Height 683
    DPI: 132
    (No Gamma Adjust)
    Color Profile: Use Source Profile
    (Black Pint Compensation NOT CHECKED)
    (Show Watermark NOT CHECKED)
    Okay, the good news is that I tried other settings and it worked. Tiff works just fine and exporting the preset jpeg setting (full size, half size) works just fine. I then deleted the export setting mentioned above and created a new one, but it does not work.
    So, I am almost there. I appreciate your suggestions so far as some of them worked. Any more ideas?

  • Cannot export versions

    Using latest version (3.5.1) of Aperture on Mavericks, all latest updates installed on MBP Mid 2012, export versions stopped working completly after succesfuly exporting cca 1500 images.
    Originals I'm trying to export are RAWs (Canon EOS60D .CR2, latest firmware on the camera), referenced images on local drive.
    Have tried different locations for export, fixing permissions on Aperture Library, reboot the machine, nothing helped. Have tried multiple and single image export. Wouldn't suspect low memory, 16GB installed.
    I'm trying to export full size JPGs with into custom folder name with version filename. Have tried on several aperture libraries, none works. I'm stuck
    Searching console for "Aperture" shows following message:
    26/11/13 22:44:10,656 Aperture[1144]: view service marshal for <NSRemoteView: 0x7f80c16eb0e0> failed to forget accessibility connection due to Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application." (The connection was invalidated from this process.) UserInfo=0x60800066a300 {NSDebugDescription=The connection was invalidated from this process.}
    timestamp: 22:44:10.656 Tuesday 26 November 2013
    process/thread/queue: Aperture (1144) / 0x1125e4000 / com.apple.NSXPCConnection.user.endpoint
    code: line 2940 of /SourceCache/ViewBridge/ViewBridge-46/NSRemoteView.m in __57-[NSRemoteView viewServiceMarshalProxy:withErrorHandler:]_block_invoke
    domain: communications-failure
    Thanks in advance for any idea on how to make export verions work again.

    You seem to have already tried a lot of the right things.
    You didn't mention 'Repair Database' so I would try that option next (as always, ensure you have a good backup). 'Repair Database' is accessed from the same screen as 'Repair Permissions.
    If that option doesn't help then, my next step would be to test it with a new user account.
    First creat the new account from system preferences.
    Then log out of your current user account and log in with the new one.
    Run Aperture from that account (you'll get a new empty library so will have to import a few photos).
    What this lets you do is see if the issue is system-wide (for all users, even though you may be the only user) or thw issue is localised to your account.
    If it still doesn't work with that new account, it's probably system wide. If it does work, the problem is localised to your user account, and there are additional troubleshooting steps you can follow, like removing presets and preferences. See HT3805 for trouble shooting basics and how to preform these.
    The fact that it stopped working after such a large export is possibly interesting. Exported versions is a peice of metadata that Aperture tracks, so it's easy to imagine how a small glitch may have caused a number of problems. However, repair database should sort any minor database problems out.
    Have you rebooted your machine since that export? Perhaps a temporary chache needs clearing.
    Andy

  • Aperture not exporting metadata when exporting masters

    It says here (http://docs.info.apple.com/article.html?artnum=302943) that "by Design" Apple doesn't allow you to embed the metadata into an exported master file. Any idea why this is 'by design'? It doesn't make sense.
    Their 'work around' is to double your work by exporting masters (with no metadata) and then exporting versions (say, as JPEGs with metadata) and keep both files together.
    I am trying to archive copies of Masters along with their metadata and want to avoid duplicating work that is grossly inefficient.

    Well, DNG export could really be the option for
    people who require raw + added metadata in one file.
    There's another thing that interested me _soooo_
    much in your reply% it's about connection between raw
    files and editorial. I don't shoot for magazines yet
    (though I will be soon enough ))) ) but I'm surprised
    clients require raw. Or it is your preferrable way of
    giving your work out?
    As a PE, I require RAW files, as 9.9 times out of 10 my color house is going to be better than the photographer at preparing the image for print. This is the same for most of the higher quality publications out there.

  • Keep video metadata after exporting MOV files

    Hello !
    I use LR5 to manage RAW/JPG/MOV files from events where I have taken pictures from. Most of the MOV files do either come from my Canon Camera or from my iPhone.
    I regular export the files in a reduced file back to my iPad or iPhone for "public" viewing. Unfortunately LR5 is loosing all metadata from my videos, especially creating date/time and GPS tags.
    Is there any way to include metadata in exported (and compressed) video files ? It works in photo's very well.
    If not, do you know any other program which can compress original video files from my iPhone and keep the metadata ?
    Thanks

    Cragen,
    A very Good Day!
    Lightroom does not read metadata from the video files till the version 5.3.
    However, the functionality may came as a feature in the coming version of  Lightroom!
    If the same is not visible in Lightroom make sure the files are copied to the system and then check the same in Lightroom
    Source: http://helpx.adobe.com/lightroom/kb/metadata-doesnt-import-video-files.html
    Let me know how it works.
    Cheers!
    Mandhir

  • Can I choose what metadata is exported?

    I'd like to export photos with some metadata (copyright, date, etc...) but not with others (camera model, lens model, etc...) Is there some way to control what metadata is exported with a file?

    You do not have much control over that.
    You cannot prevent the export of the EXIFmetadata tags. They will be exported with originals or edited versions, since they are stored in the original image file.
    When you are exporting original files, you can disable the export of IPTC metadata, for the edited versions these data will be included.
    Also, in the Preferences > Advanced panel is an option, to enable/disable the export of location data with the images.
    One way to prevent the export of certain IPTC data would be to simply duplicate all versions to exported, collect the duplicates in an album, and flag them,so you can easily recognize them again. Then batch change all duplicates of the image versions and erase the metadata tags that you do not want to export. Export the edited duplicates and delete them afterwards again.
    This will only worrk for the IPTC tags; to prevent the export of EXIF tags you would need to clear the EXIF tagswith exiftool or a similar tool. Aperture will not allow to change them.
    Regards
    Léonie

  • Oracle 10g R2 - Metadata Issue With Version Controlled Resources

    We are trying to utilize the Oracle 10g R2 feature that allows user-defined metadata to be attached to XML DB resources. However, we are encountering errors when we try to append/attach metadata to a version-controlled resource (VCR). The following steps were followed:
    1. Register a new schema to be used for metadata (XMLSCHEMA.registerSchema).
    2. Add a new resource to to the XML DB and make it version controlled (DBMS_XDB.createResource and DBMS_XDB_VERSION.makeVersioned).
    3. Checkout the newly created version-controlled resource (DBMS_XDB_VERSION.checkout)
    4. Add metadata to the version-controlled resource (DBMS_XDB.appendResourceMetadata)
    However, after step 4, the errors shown below are encountered:
    ========================================================
    begin
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [qmxStrCopy: INLOB 2], [], [], [],
    ORA-06512: at "XDB.DBMS_XDB", line 890
    ORA-06512: at line 2
    ========================================================
    The steps followed for adding metadata to a resource were taken from Chapter 26 of the "Oracle XML DB Developer's Guide 10G Release 2" (http://download-east.oracle.com/docs/cd/B19306_01/appdev.102/b14259/xdb_repos_meta.htm#sthref2302).
    Is is possible to append and maintain metadata to an XML DB version controlled resource (VCR)? If so, what are the correct steps to do this? Note that if this is tried with a resource that is not version controlled, then no errors are encountered.
    Thanks,
    Steve

    It appears that this issue has been solved in the next release of the database
    QL> spool testcase.log
    SQL> --
    SQL> connect &1/&2
    Connected.
    SQL> --
    SQL> var schemaURL varchar2(256)
    SQL> var schemaPath varchar2(256)
    SQL> var resourcePath varchar2(256)
    SQL> --
    SQL> begin
      2    :schemaURL := 'metadata.xsd';
      3    :schemaPath := '/public/metadata.xsd';
      4    :resourcePath := '/public/metadataTest.txt';
      5  end;
      6  /
    PL/SQL procedure successfully completed.
    SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
      2  /
    Call completed.
    SQL> declare
      2    res boolean;
      3    xmlSchema xmlType := xmlType(
      4  '<?xml version="1.0" encoding="UTF-8"?>
      5  <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
      6          <xs:element name="root" type="rootType" xdb:defaultTable="METADATA_TABLE"/>
      7          <xs:complexType name="rootType" xdb:SQLType="METADATA_ROOT_T">
      8                  <xs:sequence>
      9                          <xs:element name="child" type="childType"/>
    10                  </xs:sequence>
    11          </xs:complexType>
    12          <xs:complexType name="childType" xdb:SQLType="METADATA_CHILD_T">
    13                                  <xs:sequence>
    14                                          <xs:element name="Child1" type="xs:string"/>
    15                                          <xs:element name="Child2" type="xs:string"/>
    16                                  </xs:sequence>
    17          </xs:complexType>
    18  </xs:schema>
    19  ');
    20  begin
    21    if (dbms_xdb.existsResource(:schemaPath)) then
    22      dbms_xdb.deleteResource(:schemaPath);
    23    end if;
    24    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
    25  end;
    26  /
    PL/SQL procedure successfully completed.
    SQL> begin
      2    dbms_xmlschema.registerSchema
      3    (
      4      :schemaURL,
      5      xdbURIType(:schemaPath).getClob(),
      6      TRUE,TRUE,FALSE,TRUE,
      7      enableHierarchy=>DBMS_XMLSCHEMA.ENABLE_HIERARCHY_RESMETADATA
      8    );
      9  end;
    10  /
    PL/SQL procedure successfully completed.
    SQL> declare
      2    res boolean;
      3  begin
      4    if dbms_xdb.existsResource(:resourcePath) then
      5      dbms_xdb.deleteResource(:resourcePath,4);
      6    end if;
      7    res := dbms_xdb.createResource(:resourcePath,'Mary Had a Little Lamb');
      8  end;
      9  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> select xdbUriType(:resourcePath).getClob()
      2  from dual
      3  /
    XDBURITYPE(:RESOURCEPATH).GETCLOB()
    Mary Had a Little Lamb
    SQL> declare
      2    resid raw(16);
      3  begin
      4    resid := dbms_xdb_version.makeVersioned(:resourcePath);
      5  end;
      6  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> begin
      2    dbms_xdb_version.checkout(:resourcePath);
      3  end;
      4  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> set long 10000 pages 0 lines 150
    SQL> --
    SQL> select r.res.getClobVal()
      2    from resource_view r
      3   where equals_path(res,:resourcePath) = 1
      4  /
    <Resource xmlns="http://xmlns.oracle.com/xdb/XDBResource.xsd" Hidden="false" Inv
    alid="false" VersionID="1" ActivityID="0" Container="false" CustomRslv="false" V
    ersionHistory="false" StickyRef="true">
      <CreationDate>2006-06-10T05:01:25.355009</CreationDate>
      <ModificationDate>2006-06-10T05:01:25.355009</ModificationDate>
      <DisplayName>metadataTest.txt</DisplayName>
      <Language>en-US</Language>
      <CharacterSet>UTF-8</CharacterSet>
      <ContentType>text/plain</ContentType>
      <RefCount>1</RefCount>
      <ACL>
        <acl description="Public:All privileges to PUBLIC" xmlns="http://xmlns.oracl
    e.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sch
    emaLocation="http://xmlns.oracle.com/xdb/acl.xsd                           http:
    //xmlns.oracle.com/xdb/acl.xsd">
          <ace>
            <grant>true</grant>
            <principal>PUBLIC</principal>
            <privilege>
              <all/>
            </privilege>
          </ace>
        </acl>
      </ACL>
      <Owner>SCOTT</Owner>
      <Creator>SCOTT</Creator>
      <LastModifier>SCOTT</LastModifier>
      <SchemaElement>http://xmlns.oracle.com/xdb/XDBSchema.xsd#binary</SchemaElement
    >
      <Contents>
        <text>Mary Had a Little Lamb</text>
      </Contents>
      <VCRUID>15DE79F263F7CC00E040578C2A0656F8</VCRUID>
    </Resource>
    SQL> begin
      2    dbms_xdb.appendResourceMetadata(:resourcePath,xmltype(
      3  '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      4         xsi:noNamespaceSchemaLocation="metadata.xsd">
      5      <child>
      6        <Child1>AAA</Child1>
      7        <Child2>BBB</Child2>
      8      </child>
      9  </root>'));
    10  end;
    11  /
    PL/SQL procedure successfully completed.
    SQL> commit
      2  /
    Commit complete.
    SQL> select r.res.getClobVal()
      2    from resource_view r
      3   where equals_path(res,:resourcePath) = 1
      4  /
    <Resource xmlns="http://xmlns.oracle.com/xdb/XDBResource.xsd" Hidden="false" Inv
    alid="false" VersionID="0" ActivityID="0" Container="false" CustomRslv="false" V
    ersionHistory="false" StickyRef="true">
      <CreationDate>2006-06-10T05:01:25.355009</CreationDate>
      <ModificationDate>2006-06-10T05:01:25.558913</ModificationDate>
      <DisplayName>metadataTest.txt</DisplayName>
      <Language>en-US</Language>
      <CharacterSet>UTF-8</CharacterSet>
      <ContentType>text/plain</ContentType>
      <RefCount>1</RefCount>
      <ACL>
        <acl description="Public:All privileges to PUBLIC" xmlns="http://xmlns.oracl
    e.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sch
    emaLocation="http://xmlns.oracle.com/xdb/acl.xsd                           http:
    //xmlns.oracle.com/xdb/acl.xsd">
          <ace>
            <grant>true</grant>
            <principal>PUBLIC</principal>
            <privilege>
              <all/>
            </privilege>
          </ace>
        </acl>
      </ACL>
      <Owner>SCOTT</Owner>
      <Creator>SCOTT</Creator>
      <LastModifier>SCOTT</LastModifier>
      <SchemaElement>http://xmlns.oracle.com/xdb/XDBSchema.xsd#text</SchemaElement>
      <Contents>
        <text>Mary Had a Little Lamb</text>
      </Contents>
      <VCRUID>15DE79F263F7CC00E040578C2A0656F8</VCRUID>
      <Parents>15DE79F263F8CC00E040578C2A0656F8</Parents>
      <root xmlns="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNam
    espaceSchemaLocation="metadata.xsd">
        <child>
          <Child1>AAA</Child1>
          <Child2>BBB</Child2>
        </child>
      </root>
    </Resource>
    SQL> quit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.0.0 - Alpha
    With the Partitioning and Data Mining options
    I've filed bug 5313655 for the 10.2.x behavoir. If this is important to you you might want to consider signing up for the forthcoming beta program for the next release of the database

Maybe you are looking for

  • Open Office documents from NSS exported as AFP impossible

    I have my Mac Lion 10.7.4 users accessing user spaces (NW 6.5.8 NSS exported as AFP) It is imposssible to open Office documents (doc?, ppt? etc) Anybody has an idea why that is happening? Seb

  • How to prevent user from inputting in a Date field?

    Hi, everyone I have another small problems, for a Date field, user can choose from a date window or input from keyboard, is there any way to forbid user to input? I want to make the date field behave like a Drop-down list. User can just choose from l

  • Atom feed error message

    I have a Mac Book Pro which I have just received and installed ilife 09 and 10.5.6. I have two accounts on this computer, one for myself and one for my wife. We both have .mac accounts. When I subscribe to my mobile me gallery iphoto starts up and cr

  • Macbook keeps connecting to neighbor's network

    When starting up, or even waking from "sleep," why does my computer always seem to prefer trying to log into my neighbor's network rather than my own? His (or hers) is not password protected while mine is. Is that it? Whenever I realize it has happen

  • Setting return height in text?

    How do you modify the hard returns between text in Illustrator?  For example, I want to adjust the amount of space a hard returns creates between two paragraphs.  Thanks!