Lightroom TIFF metadata issue

Very shortly after Lightroom 2 was released I used it to convert all the photos in our archive from JPEG to TIFF.
These were all the digital camera photos we had shot before we started shooting as Camera Raw. We use Lightroom
for creating files but not for cataloging. For cataloging we use Cumulus as we have to provide access to people
on both coasts. What I have recently discovered is that when I add keywords in Cumulus and write those changes
back to an asset the keywords disappear from the file's metadata. If I take a sample file and resave it as a TIFF in
Photoshop then write to it from Cumulus the keywords are all there in the metadata.
My question now is, does anyone on this forum know what is different about the metadata structure between a PS TIFF
and a LR TIFF. I'm hoping to get some insight into this so the Cumulus engineers in Germany can help me with a workaround.
I'm trying to avoid having to convert 100-150,000 files.
Thanks,
Jeffrey

Okay, using exiftool I took snapshots of the same photo's metadata in 4 different states.
1- I took a tiff created in Photoshop and wrote keywords to it from Cumulus.
2- I then imported that photo into Lightroom and exported a tiff copy.
3- I reimported The PS tiff into Cumulus and added a keyword so we could
see specifically where Cumulus writes.
4- I brought the LR-tiff back into LR, added a keyword, saved to the file and
then imported that into Cumulus. I added a keyword in Cumulus, saved to
the file and, pow, all the IPTC data is gone.
So, there are only a few thousand that we have written keywords to from Lightroom.
I will stop that practice and only write from Cumulus but, I still wonder if I should convert
all of those tiffs to PS tiffs. hmm...

Similar Messages

Lightroom 6.1 TIFF metadata issue

I work in Adobe Lightroom to process photos and move them to MediaBin (4.6) to catalog and metatag; this is what my company uses for its photo library. Last week Adobe creative cloud prompted me to upgrade Lightroom; I was using 5.7, and the newest version is 6.1. In doing so, the captions and copyright information that I write in Lightroom are no longer showing up when they come in to MediaBin.
At first I thought the metadata was getting stripped following being exported from Lightroom (exported as TIFFs), but when looking at the files in photoshop, I can see all of the metadata is present. I then began a series of tests to try and figure this out.
I first moved a previously exported TIFF file from the previous version of Lightroom into MediaBin, and I could see the data that was embedded. MediaBin was working as it should.
Next, I took a file exported as a TIFF from the new Lightroom and moved it into MediaBin. I could not see the metadata, as expected. Then I downloaded it from MediaBin- as I would do to fulfill a photo request- and opened it in Photoshop. I was surprised- all the metadata was there! For some reason, MediaBin just couldn’t see it.
Finally, on a lark, I exported a file from the new Lightroom, but this time made it into a JPEG. When I moved this into MediaBin, I could see the metadata! I tried this with other file formats- DNG, PSD- and only the TIFF files show up minus their metadata.
What could cause this to happen, and only in TIFF form? I am under the impression that Metadata is just simple text information attached to a file, but I am confused that only in TIFF form do we have an issue.
Thanks!

It appears that this is caused by the same problem described here: Lightroom CC: JPEG format tripping up other programs. JPEGs and TIFFs use the same layout of metadata, and I confirmed that your TIFF has the same atypical layout as LR-produced JPEGs.
The issue is not that LR has a "bug" -- the TIFFs and JPEGs it produces strictly conform to industry standards. Rather, it's that there are many programs out there, evidently including HP MediaBin, that are buggy and don't conform to the standards and get tripped up by the atypical way that LR writes its metadata. Of course, Adobe can't change all such non-conforming programs, so LR users would very much prefer that LR go back to using a more typical layout of metadata.
Please add your vote and opinion (with details) to the bug report linked above. The more people complain, especially professional and commercial users, the more likely Adobe will prioritize a fix.

Metadata issues in A3 - This is a real concern

Metadata issues in A3. This is a real concern if your images go to third parties from A3.
http://www.controlledvocabulary.com/imagedatabases/aperture3.html

Thanks, dzedward,
I posted a reply with quite some effort in it, but it is
dissapeared after pressing the reply button. what I as explaining
was that I use an attached sound and so streaming is not an issue.
Please look at the few lines of code I use in my demo (please use
the link above for the fla with the WAV):
audioClock=new Sound(createEmptyMovieClip("sound1",1));
audioClock.attachSound("theSync");
audioClock.setVolume(90);
stop();
//When playing a swf (in most cases) the audio clock is on
every 46.4399093 ms.
//A onSoundComplete function only starts ON a clock puls!
That explains "gaps"
//when people complain working with audio loops in Flash.
//The audio sample used in this test has a 200 ms duration.
It can't be shorter.
//So it is started 25 ms from the end. When the sample is at
the end, the flash player
//pauses for 46.4399093 minus 25 ms, and starts the audio
sample from the same point
//again ( that is at the next clock puls). That's fine for
hearing audio clock and
//this test:
audioClock.start(0.175,1);
audioClock.onSoundComplete = function() {
audioClock.start(0.175,1);

Cannot write exif and tiff metadata in image file

Hi,
I have a public XMP text file containing exif and tiff metadata: http://ns.adobe.com/exif/1.0/ and http://ns.adobe.com/tiff/1.0/.
I want to write these XMP data in an image file and it doesn't work. I don't get any exceptions, just the metadata are missing in the image file.
C#
using (var xmpFiles = new XmpFiles())
      if (!xmpFiles.OpenFile("test.jpg", handler.FileFormat, OpenFlags.OpenForUpdate))
          xmpFiles.OpenFile("test.jpg", FileFormat.Unknown, OpenFlags.OpenUsePacketScanning | OpenFlags.OpenForUpdate);
     using (var xmpCore = new XmpCore())
          xmpCore.ParseFromBuffer(xmpPublic.ToString(), ParseFlags.None);
          if (xmpFiles.CanPutXmp(xmpCore))
               xmpFiles.PutXmp(xmpCore);
     xmpFiles.CloseFile(CloseFlags.None);
Public XMP:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description xmlns:_ns_2="http://ns.adobe.com/tiff/1.0/" rdf:about="">
    <_ns_2:ImageLength>4252</_ns_2:ImageLength>
</rdf:Description>
<rdf:Description xmlns:_ns_3="http://ns.adobe.com/exif/1.0/" rdf:about="">
    <_ns_3:ApertureValue>8/1</_ns_3:ApertureValue>
</rdf:Description>
</rdf:RDF>
Result XMP in image file:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""/>
</rdf:RDF>
Does anyone can help with that problem?
Thanks,
Alexandra

I found the answer by myself.
According to the last guidelines from metadata working group, exif and tiff data should not be saved as XMP data in jpeg images anylonger because jpeg natively supports exif data.
"The most recent (as of mid-2010) XMP specification describes the usage of Exif/TIFF properties within XMP itself. Both Exif ( http://ns.adobe.com/exif/1.0/) and TIFF ( http://ns.adobe.com/tiff/1.0/) namespaces have been defined so that corresponding Exif properties can be stored. This is particularly useful if Exif properties need to be stored but the file format does not support native Exif (e.g. PNG). [...]However, this document changes this earlier XMP guidance and recommends that Exif and Tiff device properties only be mapped into XMP in the case the file format does not support Exif natively."
See http://www.metadataworkinggroup.org/specs

4.2.1 Does Not Fix" Crash-on-screen saver" bug or metadata issues

ATV2 crashes as soon as it goes to screen saver. 4.2.1 does not fix this. WTC?
You have to set screen saver to "Never" to prevent crashing.
No one checks these things?
Message was edited by: Mike Kwiatkowski

Mike Kwiatkowski wrote:
ATV2 crashes as soon as it goes to screen saver. 4.2.1 does not fix this. WTC?
Metadata issues still hosed.
Not seen the screensaver issue.
Personally I think this update was a patch to fix the DVI flickering issues that rendered the device unusable for many people - other annoyances can be fixed later but we better keep reminding them:
http://www.apple.com/feedback/appletv.html

Metadata Issue iBooks

We recently submitted an Algebra 1 iBook created with iBooks author. Received the message that there was a metadata issue. Was wondering if anyone knew:
1. What is the metadata they are referring to
2. How do you edit it
3. Once fixed, do you have to completely resubmit and start over with the submission process, or can you edit what has already been submitted.
Much thanks

Meta data is the details you entered when you acted to submit your book using iTunes Producer.
Check for red flags for that book in iTunes Producer....could be any number of things - we can't tell without more info
Just edit the stuff for that book using iTP for whatever needs fixing and try again.

Metadata Issue?

I submitted my book Friday morning. Checking yestderday, I see this.
"Metadata Issue. There is an issue with the metadata. Contact us after you have verified and redelivered the metadata."
Trouble is, I can't see anything wrong with the metadata. The blanks are all filled in. Has anyone else seen this? I did a search here and it seems to indicate that Apple won't be able to tell me what the problem is. Any hints or pointers would be greatly appreciated.

It would be easy to verify for iTunes Producer whether the title in the metadata matches the title in the book. Sadly, it doesn't do that.
"Metadata Issue. There is an issue with the metadata. Contact us after you have verified and redelivered the metadata."
Singularly useful error message. The author gets to play the guessing game. Why not just say "The title in the metadata doesn't match the title of the book"?
I have the same problem with many of my submitted ebooks.
All I can suggest is to diligently go through each field of metadata, checking that it meets the requirements set up in the publisher guide and that the metadata is consistent with the book you submitted.
Michi.

EXIF: and TIFF: metadata is missing from XMP block in Lightroom 4

I've recently purchased Lightroom 4 and on the whole I'm very happy with it, but I have run into a problem. I have a few scripts which grab information from the XML-based XMP metadata block that's embedded in the DNG and JPG files that I use. I've found that images processed with Lightroom 4 no longer export the exif: and tiff: data.
To illustrate, a photo I exported with a previous version of Lightroom has the following data in the XMP block
   tiff:Make="Canon"
   tiff:Model="Canon EOS 40D"
   tiff:ImageWidth="850"
   tiff:ImageLength="567"
   tiff:XResolution="240/1"
   tiff:YResolution="240/1"
   tiff:ResolutionUnit="2"
   exif:ExifVersion="0221"
   exif:ExposureTime="1/800"
   exif:ShutterSpeedValue="9643856/1000000"
   exif:FNumber="71/10"
   exif:ApertureValue="5655638/1000000"
   exif:ExposureProgram="3"
   exif:DateTimeOriginal="2010-08-22T10:52:07.58+01:00"
   exif:DateTimeDigitized="2010-08-22T10:52:07.58+01:00"
   exif:ExposureBiasValue="0/1"
   exif:MaxApertureValue="4625/1000"
   exif:SubjectDistance="428/100"
   exif:MeteringMode="5"
   exif:FocalLength="80/1"
   exif:CustomRendered="0"
   exif:ExposureMode="0"
   exif:WhiteBalance="0"
   exif:SceneCaptureType="0"
   exif:FocalPlaneXResolution="3888000/876"
   exif:FocalPlaneYResolution="2592000/583"
   exif:FocalPlaneResolutionUnit="2"
   exif:PixelXDimension="850"
   exif:PixelYDimension="567"
There is, of course, a lot more information in the XMP block, but in a file exported using Lightroom 4 there is nothing in the XMP block with the exif: or tiff: namespaces so none of this information is available to any script which queries the XMP metadata. I'm pretty sure that the metadata is still there, embedded in the original EXIF data, as I can view it using the metadata panel in the Library module, but that's not accessible to my scripts as it's not in the XMP block. I've made doubly sure that the metadata has been saved and also double-checked all my settings and even tried to export the files multiple times with every different setting that I can think of (even though my current settings worked fine in previous versions) but the files never get the exif: or tiff: data.
I have called Adobe, but the best help they could give me so far was to post here and hope someone can help!

I just compared two JPEGs exported with LR 3.6 and LR 4.1RC. The tags you mentioned are exported neither by 4.1 nor by 3.6. These tags are only present in the normal Exif metadata, but not in XMP. Which version of LR 3.x did you use before? Perhaps Adobe changed something already in the later versions of LR 3.x. If this is the case, you have to use a script or tool that is able to read the Exif metadata directly.
In the XMP metadata in the file exported by LR 3.6, I see only crs (camera raw), aux (e.g. serial no.) and some other XMP namespaces, but no exif or tiff.
P.S. I viewed the metadata of the exported files with exiftool. File format was JPEG (with "quality" setting, not with "limit file size", because apparently there are still some XMP differences between these two modes).

Bizarre Lightroom image quality issue

I have a weird image quality issue with Lightroom, when opening RAW files (haven't tried it with any other file format, admittedly).
Here's an example of how the image appears in Lightroom. As an experiment, I exported the image as a TIFF and opened it in Gimp to see if it was just down to a display issue, but the exported TIFF showed the same quality issues as Lightroom. Aside from exporting as a TIFF (and then saving as a Jpeg), this image is SOOC:
<a href="http://www.flickr.com/photos/swisstony10/4912360565/" title="IMG_4134 by swisstony10, on Flickr"><img src="http://farm5.static.flickr.com/4093/4912360565_5891c0160f.jpg" width="333" height="500" alt="IMG_4134" /></a>
If I open the same image in Canon's own DPP software, this image quality issue does not occur, so I know that it's not an issue with the memory card, the camera, or my laptop's monitor. The SOOC image from DPP (exported as a Jpeg) looks like this:
<a href="http://www.flickr.com/photos/swisstony10/4912362053/" title="IMG_4134b by swisstony10, on Flickr"><img src="http://farm5.static.flickr.com/4116/4912362053_1ca92078c9.jpg" width="333" height="500" alt="IMG_4134b" /></a>
Has anybody else experienced this, and if so, is there a fix? (there had better be - I'm not going to be overly chuffed if my expensive Adobe software is being outperformed by the free stuff.. )
Russ.

This is proving to be an extremely helpful forum!
Thanks for the advice on embedding my calibrated colour space - I don't very often send files anywhere other than my own home network (where all the monitors are calibrated), and when I do upload any to Flickr, it's never caused a problem in the past (and if I get anything printed by a lab, I use their ICC profile). I'll definitely keep that all in mind though..
Here's the original RAW file of the image I used as the example https://www.yousendit.com/download/aHlUa3ZONmNFd2Z2Wmc9PQ - I hope that helps someone to shed some light on what's going wrong. From what you've said though, it does look as if this is just an extreme example of something that Lightroom isn't very good at doing.
As I said in my original post, it'll be a bit disappointing if that's the case though, because a fair amount of the pictures I take tend to be of bands playing in what are, let's face it, diabolical conditions for photography. (At the festival I was attending at the weekend for example, all of the photographers - even the seasoned pros - were moaning about how awful the lighting was in the Big Top, and how much it sucked to try and get a decent picture there, as opposed to the main stage where everybody wasn't completely backlit by either red or purple lights. I appreciate that Lightroom is a much more powerful tool than Canon's DPP - the noise reduction controls on their own completely rock - but I must admit I'm a bit surprised that it can't handle highlights terribly well...

Lightroom 3 exporting issue: exported JPGs come out with much more noise than original edited files

Hi all,
My first post here so nice to meet everyone. I've been having some issues with exporting in Lightroom recently. It appeared to happen quite out of the blue. Sometimes when I export my edited .cr2 files as jpgs (in srgb), at a good quality (no less than 85), some of resulting jpgs seem to have exposure higher and/or a horribly large increase in the amount of visable noise. It seems many of the photos which this occurs in have pretty high settings for fill light, but even still, the noise is not visable in lightroom while editing the metadata linked .cr2.
I thought it might be the problem that I'm viewing the final exported jpgs in preview, but I also tried adding them back into the catalog and they look just as off. I just upgraded to 3.3, but it seems to be having the same issue. If anyone can please help, it would be greatly appreciated!
Thanks

No sharpening at all during my export, Ian. Sometimes I sharpen for screen at a standard strength, but I turned it off when I started seeing the extra artifacts but the results of the exports remains basically the same with or without sharpening.
However when I import it seems my photos already have some sharpening on them in the develop module. The settings there are sharpening = 25, radius = 1, Detail = 25, masking = 0. I honestly rarely mess with the sharpening, so I guess I skipped over those settings during the countless hours I have worked with LR! But I assume those are normal post import numbers, correct? I never apply development settings during import, that's why I say that. Thanks for keeping up the conversation and brainstorming Ian! Anyone else also free to chime in.

Metadata issues / problems...

Using LR 4.1, on Windows 7 Professional...
I am updating lots of photos and their metadata, all from within Lightroom. Most every time, it tells me there was an error writing metadata and I have a majority of my photos with:
- Metadata: Has been changed
1.) Why is this happening?
2.) Is there an easy way to force the write again (currently I have to select a few hundred at a time and hit "Save metadata to file". But that's extremely memory intensive...
Thanks,
John

Geoff,
I see the same message... Not to hijack the thread but add to the discussion for kk -- I have been working to move my catalog and images to a new computer so had to Update Folder location to make it see the drive. (more on this below in case it helps us figure out the permissions issue...) The badge with the exclamation point cascades through any folder I look at.
As part of figuring out why I was having trouble seeing the drive and folder in LR4.1 I looked at the permissions for the drive and Lightroom folder specifically. This top-level folder, which holds pretty much all my images, was set for "Everybody" to read and write. The whole drive is set to "Share" in Win7 Pro 64-bit.
Someone else brought up the idea that although the OS sees the drive, Lightroom might have a permission problem that keeps it from "seeing" or writing to the files. An ACL problem? I seemed to have made LR see the images but not connect the metadata consistently.
I always held my 60,000 images on a HD assigned "E:" so as part of the move to the new machine I copied EVERYTHING (under the control of the OS) from the old "E:" to a new hard drive. I then disconnected the old "E:" HD; I started LR for the first time I made sure that this new HD was assigned "E:", although that was a re-assignment. That's why I as hunting the permissions.
Forum user "Jasonized" brought up this Permissions issue with reference to ACLs so perhaps I will post this issue there, too.
Jonathan7007

Bridge labels cause metadata issue

It seems when I apply a color label in Bridge to a PSD file (let's say the yellow label, or even a star rating), then open that PSD file... edit it... then save it. I then look at it's metadata in Bridge and notice that the Copyright status went from "unknown" to "public domain." Does anybody know why this is happening?
Even more wacky is when I remove that label and reset the copyright status back to "unknown" in Bridge CS5. I then re-open the PSD file
, make a simple edit, and the save it. The copyright status in Bridge's meta panel goes from "unknown" to "public domain" once again.
I tried this on a friend's computer running CS4, and it does the same thing as well... so it does not seem to be an isolated issue to just my machine.
Thanks

Hi Melissa,
Thanks for your response. I am also noticing that when I create a new PSD CS5 file (let's call it "test.psd"), and then "place" a file that has a label or rating into test.psd, and then save test.psd... Test.psd's copyright status goes from "unknown" to "public domain."
I notice that this situation also happens a lot when I "edit in Photoshop" from Lightroom (when the image in LR has a label or star rating). I always have to check the saved file's meta to see what got messed up, which is really inefficient and cumbersome.
I agree with changing it in File -> File Info, but if I forget to do that every time I open and save this file, it goes back to "public domain." That's a really embarrassing thing for such a robust (expensive) piece of software to not be able to do correctly.
Thank you for responding!

Deduplication in backups and Lightroom Tiff edits

Oh wise ones…I come to you with this to see if you have any insight
Have a lightroom client that is using backblaze as a secondary cloud backup for her lightroom files and images.
Recedntly had a crash and they sent her her drive with all the images - YEA
She has noticed that not ALL of the TIFF files are included
I trouble shooted everything with her and there appears to be no reason why they were not backed up. She is using Lightroom and Photoshop. Raw files go to Photoshop come back as a Tiff so she has XXXX1.RAW and XXXX1.Tiff is she goes out to another program that files comes back as XXXX1-edit.tiff and or XXXX1-edit-edit.tiff.
All saved in the same folder all the time
I did find this on back blaze website:
Our software contains a process called "deduplication" where files are digitally fingerprinted (checksummed) before they are sent to the server. When a file's fingerprint (SHA-1 checksum) matches an already backed up file, but it's renamed or moved (including drive to drive), it's simply updated at the servers, rather than re-transmitted.
You may see these files queued for back up, but once any given file is at the front of the queue, it will be checksummed, compared against the existing backup, and "deduplicate" resulting in it being updated on the server rather than re-uploading
Could this mean that double triple processed images from Lightroom are not getting saved. This could be a HUGE issue
Thoughts?

Hello Jonathon,
Thank you for the reply. It appears that the edits made in lightroom are being passed to photoshop the way LR 2x would act when selecting "Edit with Lightroom adjustments". I just do not get any options. Photoshop is opened and the image is passed to Photoshop as a DNG.
I have checked all the Lightroom preferences and cannot see anything that is configurable that could cause this behavior. I checked my LR 3 in Vista and LR 3 in Windows 7 and they act identically.
The original problem of not keeping the adjustments corrected itself when I removed the beta version of Photoshop CS5.
Jim

Metadata issue in PPro - UserClipName populates in Metadata and won't go away

I have P2 footage that is behaving oddly in PP - PPro CS6. I am on a PC, using Windows 7 Professional.
Footage was shot and archived onto our PC last summer - as is our typical process - and a PP project was started. It was left dormant till now - 6 months later. I am the new editor tasked with finishing this edit.
I began by organizing assets in the project and then reviewing all files to identify what I have to work with - this step includes logging info into the metadata (as I typically do). I noticed that the UserClipName was appearing in the SHOT metadata item - I wanted to use SHOT for the Shot number, so I replaced the UserClipName that was in that field with the Shot Number, and I made other additions to the Metadata in the appropriate fields. I saved the project often during this process. I closed the project. I then tried to open another project in PP and nothing opened. I tried to open just the program, and nothing opened. I then logged out of my user account, and then re-logged in. I tried to open PP and it opened fine.
I opened other PP projects to see if I could see the UserClipName in the SHOT item (or anywhere) in the Metadata window - and I did not see it. I also did some test changes to the metadata to see if I could replicate the same issue with the program not opening - changed metadata, save, close - and no problems with opening PP. I created a new project in PP for the above footage in question, imported it, and there was the UserClipNames in the SHOT metadata field. I did not change any metadata - just saved and closed, and was able to reopen PP. I then tried to add data to the Metadata, save and close - I was not able to reopen PP.
I have imported this footage in various ways - thru the media browser; click and drag from finder window; double click from within the Projects panel then browse to the files; using cntrl-I - and each of these methods was with a clean (new) project. No love.
I also tried to convert this footage directly in Encoder as well as through Prelude (which just takes it to Encoder) into three different formats - P2; Quicktime; H.264 - then created new projects in PP. No love.
What I know is that I can work in the project fine (as far as I can tell so far) as long as I do not touch any metadata. That is a bummer for me - but, oh well. But the fact that this issue exists concerns me -I have no assurances that I will I be able to complete this edit successfully. Fortunately it is only a short PSA, ... and for extra help, I will make my offerings to the Edit-Gods to help get me through to the end without any further issues.
I would love to hear if anyone out here has any suggestions on what might be going on - and ideally a solution. I am okay with appeasing the Edit-Gods - but I would prefer to have more solid solution.
Sali

Hi Sali,
I began by organizing assets in the project and then reviewing all files to identify what I have to work with - this step includes logging info into the metadata (as I typically do). I noticed that the UserClipName was appearing in the SHOT metadata item - I wanted to use SHOT for the Shot number, so I replaced the UserClipName that was in that field with the Shot Number, and I made other additions to the Metadata in the appropriate fields. I saved the project often during this process. I closed the project. I then tried to open another project in PP and nothing opened. I tried to open just the program, and nothing opened. I then logged out of my user account, and then re-logged in. I tried to open PP and it opened fine.
Thanks for your post.
Let me see if I understand you. You say that the text string, "UserClipName" was in the "Shot" metadata field. By replacing that text string with the a shot number in the Shot metadata you began to have unexpected behavior, such as, not being able to reopen a project. Logging out of your user account, then logging back in allowed you to then open the project. Is that correct? That's pretty odd, for sure.
I opened other PP projects to see if I could see the UserClipName in the SHOT item (or anywhere) in the Metadata window - and I did not see it. I also did some test changes to the metadata to see if I could replicate the same issue with the program not opening - changed metadata, save, close - and no problems with opening PP.
Sounds like you have hit a bug with P2 footage and Premiere Pro CS6. There is a closed bug in our database, but the state may been triggered with subsequent changes to your system, or the like. The bug also may not have been completely fixed with your particular kind of P2 media.
As I understand it, the issue has to do with how XMP metadata is interpreted by Premiere Pro. I do not believe there is a workaround for this issue other than not changing that particular metadata field. Perhaps you can use a different field, like Comment or Description, for shot number.
What I know is that I can work in the project fine (as far as I can tell so far) as long as I do not touch any metadata. That is a bummer for me - but, oh well. But the fact that this issue exists concerns me -I have no assurances that I will I be able to complete this edit successfully.
I really hope you can get through this project. Let us know if you hit any more issues along the way.
Thanks,
Kevin

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

Lightroom TIFF metadata issue

Similar Messages

Maybe you are looking for