Updating EXIF metadata

My new imports into Aperture 2 show some metadata which was not present in in 1.5. Specifically, the new version identifies lenses specifically and records camera serial numbers.
I would like to get my imported library to show these metadata items too. The info must be in the raw file, but doesn't show in the Aperture 2 metadata. I assume this means that the metadata is parsed at import and then not touched again.
Does anyone know a way of forcing Aperture to update the metadata from raw files to take advantage of software improvements?

I am disappointed to see that a bunch of EXIF metadata is still not imported correctly from my EOS 1D Mk 3 - ie metering mode, exposure mode and white balance are still only represented by numbers and not their actual selection title.
Is this my error are there any other EOS1D Mk3 users out there experiencing the same issue?
Dingah

Similar Messages

Lens Exif metadata worked for KM but no more for Sony cams

Playing with the metadata panel in Aperture 2.1, I was surprised to see the information for the lens manufacturer/model for some shots I did with my old Konica-Minolta 5D DSLR.
Sony took over the Konica-Minolta DSLR system about 2 years ago and as many others I have since moved to a Sony A100 body and recently to an A700 body.
Using the very same lenses, that give me detailed lens Exif metadata with the old Konica-Minolta 5D, the metadata field is empty with Sony A100 and A700 files.
A bit annoying, that the 4 years old Konica-Minolta 5D is supported in Aperture, while the follow up models from Sony are not.
Hope this will be fixed in the next update.
Peter

Steve,
you are probably right, that Sony is encoding the lens data in a somewhat non standard way.
But as far as I know, in the EXIF of the Konica-Minolta files, this was done as well in a non standard way, by storing a binary lens code (at least I don't find any plaintext lens data in the image file, when I peek into it with a low level file-editor like Hexedit). As the lens information is displayed in clear text for the Konica-Minolta files within Aperture, Apple must have already integrated a lens database holding data for Konica-Minolta and Sony lenses. Interestingly even new Sony lenses like the Carl-Zeiss 16-80 lens show up, when used on an old Konica-Minolta DSLR.
For me it looks like Sony might store the same lens-code now in a different proprietary EXIF field but Aperture is still looking into the old Konica-Minolta EXIF field, which is non existent or empty.
So yes, Sony probably broke it, but there was enough time for Apple to fix it, especially as they have updated the lens database all the time. It is weired to add all recent Sony lenses to Aperture's lens database, but make the data only available, if you use the lenses on a 5 years old Konica-Minolta body.
So I repeat my request for Apple to fix this in Aperture soon.
Peter

What is effect of "Update EXIF From Master"?

I can't find an explanation of this menu item. A search within the manual returns nothing (?!).
A list view of my library in the browser shows that some photos do not have a lens information entry while others do. However, if I select a photo that has no entry and then click the "Update EXIF From Master" entry in the Metadata menu the lens information appears. Nothing else appears to be changed.
However, not knowing what this option exactly does I am not sure if anything else is changed.
This begs the question as to why some photos have that information while others do not (but can be made to appear).

Aperture's metadata handling in the 1.x days skipped or missed some things (e.g. lens info). So images imported in the 1.x days may not have all the details. For these images, if you've upgraded to Aperture 2, running this may get you more EXIF info on the photo.
For images that have been imported in the last 6 months, its not going to do anything at all.
The one exception is if you somehow add GPS info to the RAW files themselves (with a tagging application) after they've already been imported. I think Ian Wood has a couple applications that will do this. Anyway, if you run this command after adding GPS info to a RAW file, I think Aperture will pick it up (I haven't managed yet to successfully add GPS info to a shot tho').

Why is there missing EXIF metadata after merging aperture libraries?

I had an old library and a new library. All metadata and files were fine in the respective libraries.
After importing one into the other, I am missing all EXIF metadata like Camera, Lens, ISO, Aperture, Focal Length.
Anyone experience this problem or have any ideas?

FIXED!
I waited this long for a simple fix:
Select all the photos, control-click on a photo and select Update from Original.

How to update managed metadata column for all file in document library using powershell

Hi,
How to update managed metadata column for all file in document library using powershell?
Any help on it.
Thanks & REgards
Poomani Sankaran

Hi TanPart,
I have changed the code which you have give in order to get the files from SharePoint 2010 Foundation Document Library.But i am getting below error in powershell.
Property 'ListItemCollectionPosition' cannot be found on this object; make sure it exists and is settable.
Could you tell me which is the issues in it?
See the code below.
$web = Get-SPWeb http://ntmoss2010:9090/Site
$list = $web.Lists["DocLib"]
$query = New-Object Microsoft.SharePoint.SPQuery
$query.ViewAttributes = "Scope='Recursive'";
$query.RowLimit = 2000
$caml = '<Where><Contains><FieldRef Name="Title" /><Value Type="Text">Process Documents/Delivery</Value></Contains></Where>' +
 '<OrderBy Override="TRUE"><FieldRef Name="ID"/></OrderBy>'
$query.Query = $caml
do
 $listItems = $list.GetItems($query)
 $spQuery.ListItemCollectionPosition = $listItems.ListItemCollectionPosition
 foreach($item in $listItems)
 #Cast to SPListItem to avoid ambiguous overload error
 $spItem = [Microsoft.SharePoint.SPListItem]$item;
 Write-Host $spItem.Title
while ($spQuery.ListItemCollectionPosition -ne $null)
Thanks & Regards
Poomani Sankaran

Update Managed Metadata field in SharePoint 2013 Designer Workflow for O365

Hi Guys,
I need to update the managed metadata field in SharePoint Custom List using Workflow but its not working. I have also tried to use the HTTP WebService POST Operation but no luck.
Am doing this for a SharePoint Online (O365) Site.
Has anyone worked on something similar and was able to get it running ?
I saw a post to create a custom Workflow Activity but I don't have a choice to go with the custom code option.
http://patrickboom.wordpress.com/2013/07/23/workflow-activity-set-managed-metadata-column/
I was able to achieve this by creating a SP 2010 based Workflow for O365. Which means that it worked well with SP 2010.
Is there a different way to do it in 2013 ? I tried almost all options apart from creating custom Activity but nothing worked out.
Any help would be great.
Thanks,
Nutan
Nutan Sharma

Hi Nutan,
According to your description, my understanding is that you want to update Managed Metadata field with SharePoint 2013 Designer for SharePoint Online.
As far as I know, there is not an OOB action to achieve your requirement with SharePoint 2013 Designer for SharePoint 2013. Customizing a workflow action is a better option to achieve it. Why didn’t you customize a workflow action as Patrick’s blog?
In addition, please take a look at the article about Nintex workflow, check whether it is useful for you:
http://habaneroconsulting.com/insights/setting-managed-metadata-fields-in-a-nintex-workflow#.UykBSf6KDHo
As this issue is about SharePoint Online, I suggest you create a new thread on SharePoint Online forum:
http://social.technet.microsoft.com/Forums/en-US/home?forum=onlineservicessharepoint . More experts will assist you.
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Index of EXIF-metadata from jpeg files by TREX

Hello,
I have the following scenario:
We have a central fileserver with a lot of marketing pictures. Our marketing people are looking for a solution to search pictures by data stored in the EXIF-metadata of the jpeg-files.
So I like to integrate this fileserver as a repository in KM, set up an index and let TREX do the search (as of note 663630 TREX can search the EXIF-Data of JPEG-Files).
As goodie I want to give the marketing people the possibility to browse through the pictures in an image gallery. This gallery should be consisting of a query-based taxonomy where all the pictures are sorted by special EXIF-data (e.g. name of the photographer).
Until now I have integrated the fileserver (as a FS-Repository) and create an index.
Before index creation I added the mime-type image/jpeg to the TREXValidMimeTypes.ini and restarted TREX.
After indexing the pictures could be found by its name, but the EXIF-data is not indexed.
Now my question:
Why TREX doesnt index the EXIF-metadata?
And how can I use the EXIF-data in an taxonomy?
System:
EP6.0 on WebAS 6.40 SPS16
TREX SPS16 Patch 2
KMC SPS16 Patch 2
Greetings from Berlin, Germany
Jens

Greetings to Berlin,
when triggered by KM, TREX will only index metadata that is known to KM as KM propertis.
I do not know in detail and am not at all sure, but you could try to create custom properties in KM that are called exactly like your EXIF-metadata, set them to "indexable", not fill them with values on KM side and then try again.
You may want to try this for just one of the EXIF-metadata as a test.
Even if that works somehow, the maximum result is:
- Property name existent in KM
- Property thus searchable an classifiable
- BUT property values will not show up in KM, as they will remain known only to TREX
Regards, Karsten

Script to update EXIF data in iPhoto '08

I shoot some photos with a digital Nikon D50, and some with a Leica M3 (35mm film). The pictures from the digital Nikon are encoded with plenty of detail in the EXIF tags, but the digitized images from the Leica and the 35mm film have only a few tags from the scanner.
I wanted a script that would update the desired EXIF tags direct in iPhoto. I looked around on the Internet at other scripts, and wrote a simple script to update a few EXIF tags on selected images in iPhoto.
I hope this script is of use to others.
http://movingtomac.blogspot.com/2008/07/script-to-update-exif-data-in-iphoto-08. html

since we don't have your tables or data, we can not run, test, or improve posted code.
How do I ask a question on the forums?
SQL and PL/SQL FAQ

IPhoto and EXIF Metadata

Is there any way to set iPhoto 6 so that it will preserve all metadata in an image, even if the image is modified in iPhoto? It seems like the EXIF metadata is preserved in my photos upon import into iPhoto, but if I adjust an image using iPhoto all my EXIF metadata (shutter speed, aperture, etc.) is overwritten or lost.
This is very annoying. Why does iPhoto behave this way? It has no business overwriting this metadata that should, by all logical accounts in my mind, remain with the image.

Jim:
How are you checking the metadata? I find that when I edit, like a crop, the modified jpg contains all of the EXIF data that the original has. I've verified that with other applications that read all the metadata.
The only metadata that is not saved for use by other applications are the comments and keywords. Those are kept in the iPhoto database file.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Disconnect WSUS server and Process of Approving Updates via Metadata.

Hi Folks:
I have recently setup 2 WSUS servers. The first one has connectivity to the Internet and of course has access to Microsoft updates. The second WSUS server is part of a disconnected network. Both WSUS servers are supporting client workstations
of various operating system versions. The connected WSUS server is fairly easy, from a management viewpoint. I simply check to see what updates are "Needed" and I approve them for download. However, the disconnected WSUS server
is the one that I need some advice on. I want to have a fairly simply procedure for the disconnected WSUS server, but here is the procedure that I think would work:
Transfer metadata and updates via disc from the connected WSUS server to the disconnected WSUS server (using documented export/import procedure).
Check to see what is "Needed" updates on the disconnected WSUS server, once the WSUS server has had a chance to absorb all the imported metadata and updates. This means that the disconnected WSUS server has determined from it's supported
client workstations, what updates are required.
Generate a list of those "Needed" updates in some form, so that I can now approve those updates on the CONNECTED WSUS server for download.
Once those updates have been downloaded to the connected WSUS server, transfer the updates and metadata again to the disconnected WSUS server. Approve those updates, so that they can now be sent out to the client workstations on the disconnected
network.
If that is my procedure (can someone like Lawrence Garvin), please let me know, if that sounds correct. I'm concerned about the double export/import of the metadata and updates.
Also, I'm wondering if it would be better to have separate connected WSUS server for supporting the disconnected WSUS to keep things straight.
For example:
One connected WSUS servers supporting the set of client workstations, that are on the connect WSUS server's network.
One disconnected WSUS server supporting the set of client workstations that are on the disconnected WSUS server's network.
One more connected WSUS server, that would be used to download and transfer metadata and updates to the disconnect WSUS server. The advantage in keeping this separate, is that you would never confuse approved updates between the connected network
client workstations and the disconnected network client workstations. Especially, if they have different versions of software, that require updating.
Any input would be appreciated.

You will likely also want to configure your WSUS server to "Download express installation files." under the "Update Files and Languages," setting on your options.
I will unequivocally disagree with this statement, for several reasons:
First, there's nothing that needs to be deployed that would use Express Installation Files anyway. Express Installation Files were designed to facilitate the deployment of Very Large Updates (read: SERVICE PACKS) across slow-speed links by significantly
reducing the size of the binary that must be downloaded by the CLIENT. There are NO service packs in the catalog that won't already be installed on any client system.
Second, in exchange for that ability of clients to download less, it significantly increased the size of the binary that must be downloaded by the SERVER from Microsoft. Express Installation Files will cause hundreds of gigabytes of extra binaries to be
downloaded, which will need to be transferred to the disconnected server. None of which will actually ever be used.
Third, most disconnected networks do not include WAN links, so the primary purpose of Express Installation File is contra-indicated by the very scenario being discussed.
Otherwise by default you might get just an installer downloaded onto the WSUS server and clients might still need internet access to download the actual package contents.
It would seem that you do not correctly understand Express Installation Files.
There is an in-depth explanation of Express Installation Files in the WSUS Deployment Guide. For additional information see
https://technet.microsoft.com/en-us/library/dd939908(v=ws.10).aspx#express
I also would not recommend a internet facing WSUS server just to provide updates to the disconnected WSUS server as that will also need to download a full copy of the content to that server when it is likely already downloaded onto your internet
/ production WSUS server anyway.
Seemingly you are also not actually familiar with the documented guidance for how to manage disconnected networks. An Internet-facing (connected) WSUS server is *exactly* how this is done.
You may also find this part of the Deployment Guide to be useful reading:
Configure a Disconnected Network to Receive Updates
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Problem with EXIF metadata reading

Hi everyone
I'm trying to read EXIF metadata information. Here is my code snippet:
uchar* exifData;
Handle exifDataHandle = filterRecord->handleProcs->newProc(100);
propSuite->getPropertyProc('8BIM', propEXIFData, 0, nil, &exifDataHandle);
exifData = (uchar*)(*exifDataHandle);
filterRecord->handleProcs->disposeProc(exifDataHandle);
After this code executed I have exifData size only 4 bytes, but as I now minimum valid EXIF data should be 6 bytes. Maybe I did something wrong?
Thanks for help.
Regards

Dennis Knutson wrote:
The old serpdrv was eliminated with 7.0 unless you manually copied the VIs and driver from an older version.
Well perhaps it was I who converted in labview 5.1. I remember that the old system was quite clumsy written. It was very slow. But with a few trick it could be speeded up. Just by using refnums like in files and a simple C program for baud rate setting. I could use stable 115200 tranfer rates back in labview 3.1
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Updating KM Metadata properties using KM API

Hi All,
We are tring to update the custom Metadata properties using KM API from the Abstract Portal Component.
We have written the below code for updating the metadata.
We have checkbox called "Region" which has multiple option values like "Asia,America,Europe". I was able to update this property with single value. But when i try to update with multiple value it is not working. I tried with comma seperated but it didn't work.
Can somebody through light on this. How to update multiple values?
Code snippet
IUserManagementService service=(IUserManagementService)PortalRuntime.getRuntimeResources().getService(IUserManagementService.KEY);
          com.sapportals.portal.security.usermanagement.IUser user =null;
               user= service.getDefaultFactory().getEP5User(request.getUser());
IResourceContext context = new ResourceContext(user);
RID path = RID.getRID("/documents/src/ex1.doc");
                    IResource res = ResourceFactory.getInstance().getResource(path,context);
                    IPropertyName propName = new PropertyName("http://ars.com/xmlns/cm","Region");
                    IMutablePropertyMap map = new MutablePropertyMap();
                    IProperty property = new Property(propName,"Asia");//How to pass multiple Values?
                    map.put(property);
                    res.setProperty(property);
Helpful answer would be appreciated and Rewarded....
Regards,
Birla.

Hi Birla,
try this:
IResource res = ResourceFactory.getInstance().getResource(path,context);
IPropertyName propName = new PropertyName("http://ars.com/xmlns/cm","Region");
java.util.List values = new List();
values.add("Asia");
values.add("America");
values.add("Muenster, Germany");
IProperty property = new Property(propName, PropertyType.STRING, values);
res.setProperty(property);
Best regards,
Michael

Can I change exif metadata with AIR?

Hi.
I am autor of a simple application that changes exif information in scanned images. I am looking for a way of re-implementing the application in a more cross platform way than it is today and found AIR interresting.
However, I can not find any API for accessing image metadata in the documentation..
Is altering the exif metadata possible with AIR (without having to implement all the "libexif-like" suff myself?)
Thanks
/sverrir

There is nothing built in to AIR - but you may wish to look at
http://code.google.com/p/as3corelib/
which is an opensource AS3 library which includes some image metadata manipulation routines.
You may also wish to make a feature request here
http://ideas.adobe.com/air
so that we will consider this addition in a future addition of the AIR runtime.
Hope that helps.
Chris Thilgen
AIR Engineering

IPhoto geotags not save in EXIF metadata

Why if I geotag a picture using iPhoto, that geotag won't be saved into the EXIF metadata? Exporting for example that picture in, say, Adobe Lightroom, or uploading it to Flickr won't show the location I picked in iPhoto, simply because that information is not stored in the EXIF metadata.
Is it this behaviour what iPhoto is supposed to do? Or is it a bug? Conversely, if I geotag a picture in Lightroom, that geotag will be saved in the EXIF metadata, and correctly read by any other application

iPhoto stores the location data in the edited version and does not write it into the original image file. To create a geocoded image file, export the edited version with the location data included:

Lightroom Import: How to load Exif metadata description

Exif schema contains a description tag, which I would like to populate as part of the process of importing images from camera. Would you please show me how that can be done. I cannot locate rhe correct property in the import dialog.

Are you referring to the EXIF:ImageDescription field or the EXIF:UserComment field? When LR imports an image, those fields get automatically imported into the LR catalog. They appear in the Metadata panel on the right. EXIF:ImageDescription will be displayed as "Caption" under the Default metadata set, and EXIF:UserComment will be displayed as "User Comment" under the EXIF metadata set.

Updating EXIF metadata

Similar Messages

Maybe you are looking for