Updating MetaData from Original Masters Possible?

Hi,
I spend hours (well, most of a day) importing my 13k+ stock library into Aperture after switching to Mac. I used to use Extensis Portfolio on Windows to catalogue my finished files.
Well, it's my own fault for not checking as i was going through all this (I assumed Aperture would be at least as intelligent as Extensis Portfolio), but Aperture seems to be very, very picky about what it recognises as valid IPTC information.
Now, all my images have been IPTC tagged using various versions of Photoshop over the years, but many of them seem to have lost their Description (Caption in Aperture) field during the import.
I have now fixed the problem files by using Graphic Converter to go through my entire collection and resave all the TIFs - which seems to solve the problem (openeing them in PS CS3 and saving them again, doesn't make the issue go away with older files, although new PS CS3 files work fine when imported).
Is there a way now to make Aperture extract Metadata again, or do I have to literally destroy the entire library and start again from my now corrected original masters?
I have to say - I'm not terribly impressed by Aperture stumbling over such a fundamental thing as importing IPTC data - Extensis Portfolio has no problem extracting IPTC data from just about any version of Photoshop.
Thanks for any help.

I have the same question. I have around 40 images out of a total of 7,000 or so in Aperature for which the IPTC metadata embedded in the original images does not display in Aperature. I don't know the reason for this, but I am looking for a way for Aperature to "extract" this existing metadata.
I'm on Aperature 1.5.6 -- v. 2.0 is on order.
Thanks for any help.

Similar Messages

Metadata from original video

Is it possible to retain the metadata from the original video somehow after going through and using Premier Pro CS5 to blur out pieces of videos? I need to be able to retain the metadata for defense attorneys to be able to see what the "original" was and what exactly was done to the video. Thanks in advance.
Cpl. Cory Sutton #42
OUPD

This article might help:
http://www.maclife.com/article/howtos/changing_creation_date_file

Is it possible to copy or export metadata from Folio Producer?

Hi,
Is it possible to copy or export metadata from one issue in Folio Producer and import/apply it to a different issue in Folio Producer? Or create a master metadata template that every issue build could use? It would save a lot of time and typing not having to re-enter the same information every month when releasing the next issue for departments, bylines, etc.
Thanks!

Bob,
Do you know when exporting metadata from Folio Producer will be available, and will it export directly to another rendition, or would it export to a sidecar.xml file?
The workflow my team prefers is to build our 1024x768 folio first, add metadata via Properties in the Folio Builder as we add articles, share the folio with editors and advertising sales, make edits and updates, then when all content is approved, create the 2048x1536 rendition folio using multiple importing of articles.
Having the ability to export from an existing folio in Folio Producer would save tons of tedious copying/pasting to get a sidecar.xml.
Hopefully when this becomes available you'll have a big announcement. (Please?)
Thanks in advance.
Mark

I recently bought, from the original website of Adobe, Photoshop elements 13. However, when I go with my mouse pointer over the menu, It hangs or he works very slow. Does anyone have an idea how I can fix it? I have already downloaded updates, both from A

I recently bought, from the original website of Adobe, Photoshop elements 13. However, when I go with my mouse pointer over the menu, It hangs or he works very slow. Does anyone have an idea how I can fix it? I have already downloaded updates, both from Adobe and Windows. I have a new pc with window 8.1.

It could be a coincidence, but I rebooted the machine and (knock on wood) PSE13 seems to be working ok.

I want to update software from 5.1.1 to 7.0 update is it possible to my first gereation iPad.advisr

I want to update software from 5 1.1 to to 7.0 to my first generation iPad.Advise and help.
Thanks.
Dhansukhlal Luhar

The original iPad 1 cannot be upgraded past iOS 5.1.1.
Sorry.

Hi My grandparents just bought an iPod Touch for me from Dubai, UAE. I can't see any facetime on the home screen nor in the settings. I've read that it's not possible. But is it possible if I get my OS updated again from India?

Hi My grandparents just bought an iPod Touch for me from Dubai, UAE. I can't see any facetime on the home screen nor in the settings. I've read that it's not possible. But is it possible if I get my OS updated again from India?

There is no way you can activate Facetime on an iPod touch purchased in the UAE. The government there required Apple to lock off Facetime at the hardware level and there's no way to unlock it. Reinstalling iOS, regardless of country, will not help. If you want Facetime, you will need to sell your UAE-version iPod and buy one there in India.
Regards.

Trouble maintaining original "date taken" info and metadata when exporting TIFFs from original CR2 files.

When exporting TIFFs (from original RAW), I noticed my metadata said the "date created" was the day of export. I want to be able to access the date the original image was taken as opposed to the day I exported it. Is there a way to maintain original date of image taken in my info? I couldn't seem to find it after I exported my TIFFs...

I just tested this with LR 5.5 Mac OS 10.9.3 and it works correctly for me.
To troubleshoot your problem:
1. Which version of LR and which platform (Mac, Windows)?
2. Which tool or command are you using to examine Date Created of the exported TIFF?
3. Upload a sample TIFF showing the problem to Dropbox or similar and post the URL here. This will allow us to take a look in detail.

Update Model from database does not update Nullable Property -- Possible bug?

Hi,
I don't know if this is the correct forum.
When updating Model from database seems does not update the entity nullable property.
and it will not update the Default Value from the Backend (MSSQL) also.
I am using VS2008 SP1 3.5EF, XP64Bit Machine.
Thanks
vb.net GUI

maybe related..
today.. i changed the PK size.. from char(10) to char(36)
got many problems.. easy to fix...
but some query stop working:
Table1Record.Table2Reference.Load(); //i'm trying to load table2 from table1..
throw this error: A relationship multiplicity constraint violation occurred: An EntityReference expected at least one related object, but the query returned no related objects from the data store.
i get this error only when PK is greater than char(10)...
with SQL profiler.. i saw that PK was truncated to char(10) :
exec sp_executesql N'SELECT [... some fields...]
FROM [dbo].[Table1] AS [Extent1]
INNER JOIN [dbo].[Table2] AS [Extent2] ON [Extent1].[NoTable2] = [Extent2].[NoTable2]
WHERE [Extent1].[NoTable1] = @EntityKeyValue1',N'@EntityKeyValue1 char(10)',@EntityKeyValue1='a2164b14-e'
(NoTable1 is the PK changed from char(10) to char(36))
i'm working with VS.NET 2008
so, i looked at Model1.Edmx... in notepad
CSDL was not changed when i did the "Update Model from Database" !!!
here is SSDL part:
        <EntityType Name="Table1">
          <Key>
            <PropertyRef Name="NoTable1" />
          </Key>
          <Property Name="NoTable1" Type="char" Nullable="false" MaxLength="36" />
here is CSDL part:
        <EntityType Name="Table1">
          <Key>
            <PropertyRef Name="NoTable1" />
          </Key>
          <Property Name="NoTable1" Type="String" Nullable="false" MaxLength="10" Unicode="false" FixedLength="true" />
Cool.. i found the prob.... but why ? and how to correct this ? manually change Model1.Edmx in notepad ??
why the maxlength property is readonly in Model Browser pane ??
what about VS.NET 2010 ?! same prob ??
is it a bug or by design ?
I hope this can help someone.. I spent a few hours on this prob
Patrick

Error while copy of Update Rules from ODS 0SD_O03 to InfoCube 0SD_C13

Hi all,
I work on a NW04s SPS9 System I would like to simply copy Update Rules (from an ODS to an InfoCube) from the BCT to the 1:1 Z-Copies of these Objects.
To do so, I copied the InfoProviders 0SD_O03 and 0SD_C13 to Z-Versions. In SAP BCT the InfoCube is updated from the ODS. The ODS itself is updated from InfoSource.
After successfully copying the two InfoProviders as next step I tried to copy the Update Rules from the Content version Objects to the Z-Version Objects to link them.
Similar to copying update rules in 3.5 I tried
- right click on "ZSD_C13"
- choose Additional Functions - Create Update Rules"
- choose DataSource: ODS Object "ZSD_O03"
- choose Copy from: InfoCube "0SD_C13"
This result in the error "0SD_C13 is not suitable as a template for copying update rules".
Some hints that might help:
1. The very same error occurs if I try to copy the Update Rules from 0SD_O03 to 0SD_C13.
2. I also tried to copy both Update Rules (to C12 & C13) on a BW 3.5 system where it worked fine: The update rules from both Z-ODSs to both Z-Cubes were copied correctly 1:1 and without any errors.
3. In the NW04s System I was able to copy the Update Rules from the InfoSource 2LIS_11_VAITM to 0SD_O01 (as well as from 2LIS_11_VAHDR to ODS 0SD_O03). So I only cannot copy Update Rules from ODSs to InfoCubes while it is possible to copy Update Rules from InfoSources to ODSs.
4. During copy of 0SD_O03 the system warned: "InfoObject 0FISCVARNT needs to be in key for DataStore object ZSD_O03". No matter whether I move this IO to the keys of the Z-ODS, the Update Rules copy does not work.
- This warning does not show up on BW3.5 when I copy the very same ODS. Can anyone explain this?
- This warning is not displayed during the copy of ODS 0SD_O01, just for 0SD_O03.
5. Obviously during a preceding test I actually must have been able to copy the Update Rules for another copy of 0SD_C13 (as I can see the Update Rules in the SAPGUI). I stopped this first test as I was not able to do the Update Rules copy for 0SD_C12.
Yet as of today I cannot copy Update Rules this for both cubes 0SD_C13 as well as 0SD_C12. So yesterday there was no error on copying the Update Rules to InfoCube ZSD_C13, but today there is. To my knowledge nothing has been changed in the System Setup / Customizing in the mean time.
6. For both cubes ZSD_C13 as well as ZSD_C12 it is possible to copy Update Rules that map from the BCT ODS to the Z-InfoCbes. So I can copy Update Rules from 0SD_O03 to ZSD_C13 and from 0SD_O01 to ZSD_C12. This would point in the direction that the copied ODSes are the source of this behavior?
I am not sure whether this is a special NW04s behavior and how to use it correctly so the Update Rules can be copied.
Please could you help on how to copy these Update Rules in NW04s or share your experience if you had similar?
Thanks a lot,
Werner

Hi Vinod,
Check the update rules for the original cube. Are they active? It appears that they contain a formula...check this too.
Hope this helps...

Update Metadata in Elements 12

Is there a way to have the metadata automatically update to the original file or do we have to manually do it all the time?

You need to convert the music into one of the formats supported by Elements:
Here's an article showing how to convert unprotected music in iTunes to WAV - http://www.aimersoft.com/itunes-drm/itunes-to-wav.html (methods 1 & 2 don't require the product they would like you to buy).
Cheers,
Neale
Insanity is hereditary, you get it from your children

Access custom metadata from another plugin

I was wondering if it would be possible to access the custom metadata from one plugin from another plugin.
I know you use the _PLUGIN object when you read or write the metadata with a plugin.Is there any way to pass the varible to another plugin, maybe stored in a xml or text file in the modules folder? I also see where you can use the "unique identifying string" or plugin.id. Is this id differant for every installation of Lightroom?

Allen, I'm pretty sure the answer is no - you can't access another plug-in's custom fields.
I'm sure I have read this limitation somewhere - even if I can't now see it stated explicitly in the documentation. If anything, the docs imply getPropertyForPlugin can do so by specifying the LrToolkitIdentifier value (which you may be able to pass as a preference). So this doesn't work:
getData = photo:getPropertyForPlugin("uk.co.beardsworth.missing", jbMissing )
It is an important point though that one plug-in should be able to access another's custom fields. Obviously one can think of many ordinary circumstances where it would be handy, but I'm more worried about the longer term DAM viability of custom metadata. Let's say I decided to release a plug-in based around custom fields and users entered metadata which had some value to them - whether that's just input time or business data (eg client or agency account number). Now move on to LR3 and the plug-in no longer works - I've disappeared, driven mad by SDK changes, or you're unwilling to pay my extortionate plug-in upgrade fee.
Now what happens to that valuable metadata? The data is still in the database but you can't read it because the original plug-in's unavailable, and Adobe's built-in "All" Plugin Metadata panel only shows data from enabled plug-ins. It's not in the XMP either. You're stuffed - unless you're resourceful enough to reverse engineer chunks of the plug-in. Assuming that I encrypted my plug-in's code, that means you're going to have to dig around the SQL to figure out my plug-in's ID and its field names. Only then can you create a plug-in to rescue your custom data. And you've got to hope to hell that my plug-in didn't encrypt or obscure the values you entered.
For me what this shows is
1) You're taking a big risk if you store valuable custom metadata - if you can't sort it out yourself, should you do it?
2) You should ensure any plug-in with custom metadata stores its field definitions in unencrypted files
3) The All Plug-in Metadata panel needs to show all plug-in metadata
4) The SDK should allow you to get custom metadata from other plug-ins
4) Custom fields should be mapped to XMP
Short answer - No.
John

Request: Ability to update metadata via spreadsheet view or csv file upload

A fairly simple change to make Muse more efficient and user-friendly.
I'm in the process of building out a medium size site for a client (90+ pages) - my first experience using Muse - and editing metadata is a pain. I've planned the site: page titles, descriptions, page names, etc, but updating metadata isn't the first step in my creation process and now I'm going back through updating information. My have a 2013 Mac Pro and 2013 Macbook Pro and both systems take time to update this information with so much data buffering and being updated.
My request:
The ability to update metadata across a site without the changes being executed until we applied the changes. For example, changing site view to a spreadsheet view with each pages information. Then, I could update a bunch of pages and hit enter, and walk away while it takes 5 minutes to update. This would also eliminate the hassle of requesting page properties from each page separately.
Thanks in advance.

Is your DTP full or delta.
Here is some interesting discussion.
/thread/348238 [original link is broken]

Backup to Vault Fails Before Switching From Copying Masters to Next Step

My backup to a Vault in Aperture 3 has failed.
I have successfully upgraded to Aperture 3 from Aperture 2. Everything works well, except backing up to a Vault. I have attempted to save the entire library to two different drives - one internal and one external, both empty and tested as OK in the Disk Utility. The backups - multiple times - simply stopped at the same place. The usual sequence is copying masters and then versions, but the full backups never went beyond copying masters. I’ve set up additional libraries of individual projects, and those libraries backed up to vaults with no problem. I had no problems with saving to a Vault with the Aperture 2 library.
I’m using a Mac Pro with Snow Leopard (10.6.2), 2x2.66 Dual-Core Intel Xeons, and 10gb of memory. There are four internal drives, and two external drives connected by a firewire connection. The computer and drives are unchanged through the transition to Aperture 3.
Any suggestions?

I Have exact the same problem.
Originally updated a 150 GB Library from 2.1.4 to Ap 3; Backing up to a NAS based Vault stops after doing the masters.
I ended in reinstalling Ap 3, and Creating a new library from scratch. Reimporting the upgraded library worked fine, but Vault freezes like before.
Creating gain a new library and Importing original masters and versions step by step. After every import Vault backup works until now (60% done).
I m curious wether it will work when I m finished.
All my keywording etc. will be gone then !

The 'Update Metadata' icon displays even after saving metadata

After upgrading from v3 to v4.3, I opened my catalog (Lightroom made a copy of the file and converted it for v4.3). I didn't do anything to the images, but noticed several displayed the 'Update Metadata' icon. (I should note the 'update metadata automatically' option in the preferences is turned off to save ROM.)
Since I update the metadata manually, it's possible I forgot to save these several files — but when I try to save them, the icon persistently returns within seconds, or when I scroll away and come back.
I'm running an iMac with OS X 10.6.8 and 165 GB of disc space. The Lightroom files are on an external drive, and the images are DNGs.

rjmooreii wrote:
The Lightroom files are on an external drive, and the images are DNGs.
For DNG the best solution is to run the 'Update DNG Preview and Metadata' command, which can be found under the Metadata menu. This method builds a completely new DNG file before removing the old file.
As to the cause - two known at present:
1. Auto Exposure or Lens corrections, and
2. Applying Spot Heal corrections with opacity less than 100%
The first is complicated by the fact that it's also associated with updating of the thumbnail previews (basically a timing issue) and has been around for a long time, although not everyone sees it. The second is more recent and much easier to reproduce.
Adobe engineering are aware of these bugs, but I supect that the fix is still some way off. The user level fix for both is as mentioned above, but further develop adjustments can result in it returning.

How to allow CS users to update metadata on several items? (UCM 10gR3)

In the UCM 10gR3 portal user interface:
It is convenient for us to allow users to update metadata fields on a group of items in one action. We want to allow users to select any number of files from a CS search result.
After selecting the items, we want to users to be able to set new values for some fields (e.g. Security Group and Document Type) without touching the values of the other metadata fields (such as Author).
This seems to be pretty basic functionality, but we cannot seem to find it in the CS user interface. What is the easiest way to do this in the CS user interface?
Thanks!

Unfortunately freezing the metadata model is not an option in practice. While we may make a model that serves us well for the time being, we are likely to end up in a situation where the outside world invalidates our metadata model.
A hypothetical case
From the UCM Administration Manual:
"Choose only static information as a security group. For example, department names change infrequently, so they can be considered static; projects come and go, so they might not be considered static."
Although department names may change infrequently, they are likely to change sometimes. Sometimes departments are split up or merged.
A real case
In our concrete case, a project will generate a large amount of content distributed over many content items. After the production of this content within the project the responsibility will be transferred to a number of different departments. It is thus impossible to know in advance which metadata model will be suitable and it seems that the archiver is inefficient in solving the problem of delegating the content to different security groups.
Obviously, we are not interested in making heavy customization that we need to maintain. And reassigning the security group of many content items individually is not a feasible solution.
Has anyone had similar needs? What solutions have you used?

Updating MetaData from Original Masters Possible?

Similar Messages

Maybe you are looking for