When file(s) are uploaded the metadata does not come along with it

Razuna v2 Legacy Self-Hosted
1

I have a bunch of photos that I added keyword metadata to in Lightroom and/or photoshop that are embedded into the jpg file. When I upload the file(s) to the self-hosted Razuna v1.6.5 the metadata does not get imported with the file and show all metadata as blank.

I can add the metadata after the fact and it works. Exiftool is installed, is the latest version, and has the correct path to it.

Any ideas why Razua is not importing the embedded metadate in the file(s)?

2

It’s also not reading the dimensions and color space. I’m guessing it’s something that’s not configured right on our end…

3

Also want to add that we downloaded the prebuilt vmware image and when we started it up we got the message about exiftool being missing so we changed the path to where it’s currently located /usr/bin

4

I recommend updating all tools in the vmware image. Installation is here http://wiki.razuna.com/display/ecp/Install+Razuna+on+Linux and for ffmpeg you can rebuild it at http://wiki.razuna.com/display/ecp/FFmpeg+Installation+for+Ubuntu (scroll all the way to the bottom to see how to upgrade)

5

Was using Razuna 1.6.5. Did a new clean fresh install of Razuna 1.7 with the pre build elastic server VM version and still having the same issues. Metadata not read with JPG’s. Other images formats and PDF’s metadata does get read though… Original assets dimensions for JPG’s are 0x0. Tried multiple formats and variations of JPG images.

• Updated all tools
• No error logs
• Razuna 1.7 running on Ubuntu 10.04.4

← Path is correct to Exiftool and all other tools →

← Exiftool is running version 9.75 →

Saw other people were having the same issues as I am, but didn’t see any real answers to them. Did all the test that they did as well.

https://forums.razuna.org/topic/original-asset-dimensions-empty
https://forums.razuna.org/topic/original-asset-dimensions-wrong

6

Well, Don’t know what I did, but now everything seems to work…

7

Most likely caching. You need to flush the application cache when you apply a new upgrade. From time to time, if you see things not working properly, it is also advised to flush the cache.

Glad it works now.