Ediscovery Export : Metadata Consistency

Hello Everyone,
I am facing a peculiar challenge in one of our ediscovery project implementation.
Challenge description:
When legal users export the hold documents (Image-1), It’s showing the exported date/time as “Date Modified” not the actual modified
date of the documents (Image -2).
I have verified that none of the document properties hold the actual modified date.
Image -1 :
Image - 2:
Business users need the actual modified date as “Date Modified”, as failing to do so will be considered as "Tampering of Evidence
Please let me know if anyone has encountered this before and any solution/approach implemented.
I have checked the api to override the export functionality but there is little to none information available about this.
Regards,
Akash

The OWB Bridge metadata export will work with 10.1.0.4. So you should be able to deploy your OLAP schema to your target instance.
Hope this helps,
Keith
Oracle Business Intelligence Product Management
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Beans http://www.oracle.com/technology/products/bib/index.html
Discoverer: http://www.oracle.com/technology/products/discoverer/
BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Blog: http://oraclebi.blogspot.com/

Similar Messages

How can I export metadata to a csv file in CS4?

Help please, I used Workflow Automation Scripts on CS3 but it doesn't seem to work on CS4.

OK,
after combing through these posts and trying various 'solutions' I have found that the Barred Rock export metadata script is the only one I have been able to get to work in CS4, kinda. It is a superior script to the original workflow automation script that edo75 refers to, as it does not seem to have the comma issue encountered by jesse and others, where if there are any commas in your metadata it creates a new column and your excel file becomes nonsensical and disorganized. There is a way to avoid this by the way, simply by opening a new file in excel and importing the csv file as text, you then tell excel to read the data the right way by selecting various delimiter combinations. It is not a perfect solution but I have found that by doing this it places most of my metadata in the proper columns, and I end up doing a minimal amount of editing. The barred rock version, which I assume is a modified version of the original script available from adobe as the interface is exactly the same, does not seem to have this issue with commas at all, I am unsure why. If B. Stucky is still reading these posts he may be able to answer, as I think he wrote this script?
Anyhow I was able to get the script to load in CS4 and then I had to tweek the script to recognize my custom metadata schema, which I was able to do. Now however there is an issue with it recognizing the actual metadata in the image files. I suspect it is a mynamespace issue, that is, I do not have the right path for it to locate the actual metadata for export.
here is where I suspect the problem lay, where this "http://NPSAlaskaImageStandard" is incorrect.
new MdNs.MetadataNamespace( "NPS Alaska Image Standard", "http://NPSAlaskaImageStandard", "NPSAlaskaImageStandard" );
I am a total novice with this stuff so this may not be it at all, however this is my best guess, anyone know the answer?

Error while exporting metadata file /iam-features-ldap-sync/LDAPUser.xml

Hi All,
i am trying to export /iam-features-ldap-sync/LDAPUser.xml metadata file with the weblogic properties mentioned below
# Weblogic Server Name on which OIM application is running
wls_servername=oim_server1
# If you are importing or exporting any out of box event handlers, value is oim.
# For rest of the out of box metadata, value is OIMMetadata.
# If you are importing or exporting any custom data, always use application name as OIMMetadata.
application_name=OIMMetadata
# Directory location from which XML file should be imported.
# Lets say I want to import User.xml and it is in the location /scratc/asmaram/temp/oim/file/User.xml,
# I should give from location value as /scratc/asmaram/temp/oim. Make sure no other files exist
# in this folder or in its sub folders. Import utility tries to recursively import all the files under the
# from location folder. This property is only used by weblogicImportMetadata.sh
metadata_from_loc=@metadata_from_loc
# Directory location to which XML file should be exported to
metadata_to_loc=D:/MDS
# For example /file/User.xml to export user entity definition. You can specify multiple xml files as comma separated values.
# This property is only used by weblogicExportMetadata.sh and weblogicDeleteMetadata.sh scripts
metadata_files=/metadata/iam-features-ldap-sync/LDAPUser.xml
# Application version
application_version=11.1.1.3.0
i get the following error
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting export metadata script ....
Please enter your username [weblogic] :weblogic
Please enter your password [welcome1] :
Please enter your server URL [t3://localhost:7001] :t3://hostname:7001
Connecting to t3://hostname:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'OIMDOMAIN'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to domainRuntime tree. This is a read-only tree with DomainMBea
n as the root.
For more help, use help(domainRuntime)
Problem invoking WLST - Traceback (innermost last):
File "C:\Oracle\Middleware\Oracle_IDM1\server\bin\weblogicExportMetadata.py";,
line 22, in ?
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 134, i
n exportMetadata
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 568, i
n executeAppRuntimeMBeanOperation
File "C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py";, line 538, i
n getMDSAppRuntimeMBean
UserWarning: MDS-91002: MDS Application runtime MBean for "OIMMetadata" is not available. "exportMetadata" operation failure.
i have exported these files multiple times, it never gave an errror, but this time i see this error, please help.
Thanks in advance

Glad that worked.
Working with MDS, another way is to use the EM console for exporting/importing data from/to MDS. This I find lot easier rather than working with the OOTB script.
Steps are:
http://ADMINSTRATION_SERVER/em
Navigate to Identity and Access, oim. Right-click and navigate to System MBean Browser.
Under Application Defined MBeans, navigate to oracle.mds.lcm, Server:oim_server1, Application:oim, MDSAppRuntime.
To export the configuration files:
•     Click the Operations tab, and then click exportMetaData.
•     In the toLocation field, enter /tmp or the name of another directory.
•     Select createSubDir as false.
•     In the docs field, enter the complete file location as the Element.
•     Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.
This exports the file specified in the docs field to the directory specified in the toLocation field.
To import the configuration files:
•     Click importMetaData
•     In the fromLocation field, enter /tmp or the name of the directory in which you have the configuration files.
•     Select createSubDir as false.
•     In the docs field, enter the complete file location as the Element. For example, /db/oim-config.xml.
•     Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.
This imports the file specified in the docs field to MDS in the toLocation field.
HTH

Exporting Metadata (caption information) from JPEGS to a comma separated value (CSV) file

Here is my dilemma. I am an archivist at an arts organization and we are in the process of digitizing many of our materials to post them on the web and make them available to internet users. One of the principle components of our collection is a large trove of photographs. We have been in the process of digitizing these images and embedding metadata (in the Caption/Description, Author/Photographer and Copyright fields) via PhotoShops File Info command.
Now I am at a crossroads. We need to extract this metadata and transfer it into a comma separated value form, like an Excel spreadsheet or a FileMakerPro database. I have been told that it is not possible to do this through PhotoShop, that I must run a script through Acrobat or Bridge. I have no clue how to do this. I have been directed to a couple of links.
First I was directed to this (now dead) link: http://www.barredrocksoftware.com/products.html
The BSExportMetadata script allegedly exports the metadata from files selected in Adobe's Bridge into a comma separated value (CSV) file suitable for import into Excel, Access and most database programs. It installs as a Bridge menu item making it simple to use. The the Export Metadata script provides you with an easy to use wizard allowing you to select associated information about a set of images that you can then export. This script requires Creative Suite 2 (CS2). This script sounds like it does exactly what I want to do, but unfortunately, it no longer exists.
Then I found this:
Arnold Dubin, "Script to Export and Import Keywords and Metadata" #13, 8 Aug 2005 7:23 am
I tried this procedure, but nothing seemed to happen. I also tried to copy the script into the JAVASCRIPT action option in Acrobat, but I received a message that the script had an error. It also seems to me that this script does not set up a dumping point, that is, a file into which this information will be exported to.
I am a novice, not a code writer or a programmer/developer. I need a step-by-step explanation of how to implement this filtering of information. We have about 2000 jpeg and tiff files, so I would rather not go through each file and copy and paste this information elsewhere. I need to find out how to create a batch process that will do this procedure for me. Can anyone help?

Hello -
Is anyone aware of a tool that will do the above that is available for mac? Everything I've found so far seems to be PC only.
Any help is appreciated, thanks!

Exporting Metadate for multiple images

Hi, I can't find a way of easily exporting the metadata for a number of images into a csv file. The "Export Metadata" function in Aperture 1.5 only exports the file name and the keywords, with a number of blank columns, and there are no column headings for useful information like shutter speed and aperture!
I've looked at tools like "exiftool" but they are quite difficult to run and seem to only do one image at a time. I also tried using Automator to extract metadata, but couldn't make it work
It would be very useful if I could (a) enter comments in a metadata field and (b) extract technical metadata to a csv file for a number of images
any suggestions welcomed!
Richard

You should be able to do it using AppleScript. It is not straightforward, unfortunately, but the information seems to be there.
http://homepage.mac.com/jlarson7/metadata/index.html

Can I Export Metadata Using CS2?

Hi Everbody,
I'd like to generate a text file for my client with filenames, captions, and credits. Can I do this from CS2 somehow? I can't see how to do it in Bridge or Photoshop at this point. Thanks in advance for your time, folks.
Phil

Phil,
Go to www.creativescripting.net
Look for the barred rock scripts. There's a script in there that exports metadata to a csv file.
Make sure you download all the docs too!
Bob

Export with consistent=y raise snapshot too old error.

Hi,
Oracle version:9204
It raises
EXP-00056: ORACLE error 1555 encountered
ORA-01555: snapshot too old: rollback segment number 2 with name
"_SYSSMU2$" too small
when I do an export with consistent=y option.
And I find below information in alert_orcl.log
Wed Apr 20 07:50:01 2005
SELECT /*NESTED_TABLE_GET_REFS*/ "XXX"."TABLENAME".* FROM
"XXX"."TABLENAME"
ORA-01555 caused by SQL statement below (Query Duration=1140060307
sec, SCN: 0x0000.00442609):
The undo parameters:
undo_retention=10800(default value)
undo_retention is larger than the seconds run export(only 1800
seconds),so I think the default value is enough.
undo_management=auto(default value)
Maybe the rollback tablespace is too small(about 300M)? But I think oracle should increase the size of datafile in this mode.Is that right?
undo_tablespace=undotbs1
undo_suppress_errors=false
I think I must miss something.
Any suggestions will be very appreciated.
Thanks.
wy

UNDO_RETENTION is a request, not a mandate. If your UNDO tablespace is too small, Oracle may have to discard UNDO segments before UNDO_RETENTION is reached.
How much UNDO is your database generating every second?
SELECT stat.undoblks * param.value / 1024 / 1024 / 10 / 60 undo_mb_per_sec
FROM v$undostat stat,
v$parameter param
WHERE param.name = 'db_block_size'Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

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

Metadata Consistency warnings error.....need help

I'm getting this error when i run my reports. I checked in all my files and I'm not seeing any consistency warnings. Can someone tell me why and how i can fix this error?
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: count(HPQC_DEFECT.BG_BUG_ID by [ HPQC_DEFECT.BG_BUG_ID, HPQC_DEFECT.BG_SEVERITY, HPQC_DEFECT.BG_PRIORITY, HPQC_DEFECT.BG_DETECTION_DATE, HPQC_DEFECT.BG_DETECTION_VERSION, HPQC_DEFECT.BG_USER_03, HPQC_DEFECT.BG_USER_05, HPQC_DEFECT.BG_USER_15, HPQC_DEFECT.Closing Date, Project_Dim.DOMAIN, HPQC_DEFECT.Week of Defect Closed Date, hpqc_audit_log_prop_EIT.AU_TIME, hpqc_audit_log_prop_EIT.AP_NEW_VALUE, case when Project_Dim.PROJECT = 'PRODUCT_13_2' then 'Stores' when Project_Dim.PROJECT = 'System_Test_13_2' then 'MOM' when Project_Dim.PROJECT = 'Enterprise_13_2' then 'EIT' else Project_Dim.PROJECT end ] ). Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT "Projec Dim".Domain saw_0, case WHEN "Projec Dim".Project = 'PRODUCT_13_2' then 'Stores' WHEN "Projec Dim".Project = 'System_Test_13_2' then 'MOM' WHEN "Projec Dim".Project = 'Enterprise_13_2' then 'EIT' else "Projec Dim".Project end saw_1, COUNT("Defect Facts"."Defect ID") saw_2, "Defect Facts"."Defect ID" saw_3, "Defect Facts".Severity saw_4, "Defect Facts".Priority saw_5, "Defect Facts"."Reported Release (Base)" saw_6, "Defect Facts"."Closing Date" saw_7, "Defect Facts".Status saw_8, "Defect Facts".Type saw_9, RSUM(COUNT("Defect Facts"."Defect ID")) saw_10, "Defect Facts"."Week of Defect Closed Date" saw_11, "Defect Facts"."Testing Type" saw_12, "Defect Facts"."Detected on Date" saw_13, hpqc_audit_log_prop_EIT.AP_NEW_VALUE saw_14, hpqc_audit_log_prop_EIT.AU_TIME saw_15 FROM Defect WHERE ("Defect Facts"."Closing Date" IS NOT NULL) AND ("Projec Dim".Project IN ('System_Test_13_2', 'PRODUCT_13_2', 'Enterprise_13_2')) AND ("Defect Facts"."Reported Release (Base)" IN ('13.2', '13.2 Euphrates')) AND ("Defect Facts"."Testing Type" IN ('System', 'System Test', 'Integration', 'Regression', 'EIT')) AND ("Defect Facts"."Detected on Date" > timestamp '2010-04-01 00:00:00') AND (Audit_Log_Dim.AU_ENTITY_TYPE = 'BUG') AND (hpqc_audit_log_prop_EIT.AP_NEW_VALUE IN ('Cancelled', 'Closed', 'Completed', 'Resolved')) AND (hpqc_audit_log_prop_EIT.AU_TIME = date '2010-04-01') ORDER BY saw_11, saw_4

I was facing this problem for a long time, this came up
1) when there was no link between the columns shown in the report and the dimension against which it is shown. Sol: You need a physical join at the physical layer and also properly define logical joins at the BMM layer.
2) when you use facts for dimensions as well. Sol: you need to make sure all aliases are mapped(in the dimension) as well when you show the data.
3)when content level has not been set correctly.Content level is very important, you need to make sure that the content levels are set properly, make sure that content levels for all the dimensions used in the request that is throwing an error, are set in the Logical Table Source of the fact and are at the correct levels. If you are not sure of any content level then do not set any content level.
4)when I had a duplicate column under different presentation tables. Remove the duplicate.
Thanks
Manoj
Edited by: user13367543 on Jul 27, 2010 12:30 AM

Unable to navigate requested Expression.Please fix the metadata consistency

Hello ,
I have created one criteria but when I m running the request i m geeting this error, State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: Dim - GL Account.Unit Code. Please fix the metadata consistency warnings. (HY000)
now when i checked the RPD for this and run the consistency check everything went fine.No warning MSG, No Error, No Best Best Practice.
now i checked the join condition in BMM for the dimension i m using in report and fact.
it's like Fact F is directly Joined with Dim A & Dim B.
now when i checked the Physical join it's like Fact F1 is joined with Dim Aand Dim C , Fact F2 is joined with Dim B and Dim C.
so there is no direct fact table join between Dim A and Dim B.
Fact F1 & Fact F2 goes as MTLS in BMM and creating Fact F, now when i got this error i went to Fact F in BMM and checked the LTS and level of granuality for DIM A and Dim B for Fact F1 and Fact F2 respectively. and it is also set as detail level. and in BMM LTS Fact F1 and Fact F2 is also join with inner join with Dim C. and Dim C's level of granuality is also set in Fact F1 and Fact F2 .
the Columns that i m taking criteria are coimng from Fact F, Dim A, Dim B.
can anyone suggest me what to do in this case????
Thanking you..

Hi Veer,
If I get you correctly,
In BMM
Fact F = (physical F1 + F2)
In Physical:
F1 -> Dim A, Dim C ; F2 -> Dim B,Dim C
So, in your BMM, please make sure that
1. Logical source for physical F1 has 'Detail for Dim A, Dim C' and 'Total for Dim B'
2. Logical source for physical F2 has 'Detail for Dim B , Dim C' and 'Total for Dim A'.
I think this should resolve the issue.
Hope this helps.
Thank you,
Dhar

Exporting Metadata

I've created custom metadata views and presets for cataloging my images. Is it possible to export this metadata into an Excel spreadsheet as a CSV or TSV file? File/Export/Metadata exports standard metadata, but not my custom fields and entries. Or, is it possible to export XMP sidecar files and somehow import those into Excel? All that data is there somewhere within Aperture - please help me get it out and into a spreadsheet! Thanks.

You have to use some Applescript, but it's a relatively simple script.
tell application "Aperture"
set tSelection to the selection -- this gets all the Versions currently selected
set tValues to ""
repeat with i from 1 to number of items in tSelection -- now loop through selection
set tImg to item i of tSelection
set tValues to tValues & "Version Name: " & name of tImg -- add the name
try
set tValues to tValues & "Aperture: " & value of EXIF tag "ApertureValue" of tImg -- add the aperture
set tValues to tValues & tab -- replace with "," for comma-delimted values
end try
try
set tValues to tValues & "Shutter: " & value of EXIF tag "ShutterSpeed" of tImg
end try
set tValues to tValues & return -- make a new line for each image
end repeat
end tell
Copy and paste into Script Editor (in Applications/AppleScript) and hit the Run button, in the bottom pane you'll get the results. Note that you'll have to change 'EXIF tag' to 'custom tag' for your custom tags, and to 'IPTC tag' for IPTC data.
The 'try/end try' bits are in there so that the script doesn't fail if it comes up against an empty tag.
Ian

Please fix the metadata consistency warnings error..

Hi Guys,
I am new to OBIEE, When i try to convert a chart view into Pivot table i get th ebelow error.How can i fix this issue?
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 3058399872. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: FILTER(Budget Amount:[DAggr(Fact - Fins - Budget.Budget Amount by [ ] )] USING Dim - GL Account.Group Account Number = 'MKTG PAYROLL'). Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT "Time"."Fiscal Quarter" saw_0, "Time"."Fiscal Period" saw_1, "Facts - Budget"."Total Operating Expenses" saw_2, "Facts - Actuals"."Total Operating Expenses" saw_3, "Facts - Budget"."Total Operating Expenses"-"Facts - Actuals"."Total Operating Expenses" saw_4, "Facts - Budget"."Total Operating Expenses YTD" saw_5, "Facts - Actuals"."Total Operating Expenses YTD" saw_6, "Facts - Budget"."Total Operating Expenses YTD"-"Facts - Actuals"."Total Operating Expenses YTD" saw_7, AGGREGATE(saw_2 BY ), AGGREGATE(saw_3 BY ), AGGREGATE(saw_4 BY ), AGGREGATE(saw_7 BY ), AGGREGATE(saw_2 BY saw_0), AGGREGATE(saw_3 BY saw_0), AGGREGATE(saw_4 BY saw_0), AGGREGATE(saw_7 BY saw_0) FROM "Financials - GL Budget and Expenses" WHERE ((Time."Fiscal Quarter" <= VALUEOF(NQ_SESSION."CURRENT_FSCL_QUARTER")) AND (Time."Fiscal Quarter" > VALUEOF(NQ_SESSION."FSCL_QTR_YEAR_AGO"))) AND (("WFS Segments".SEGMENT_NAME IN ('Aviation', 'Corporate', 'Land', 'Marine')) AND ("WFS Segments".ORG_NUM = VALUEOF(NQ_SESSION."OU_ORG"))) AND ("GL Segment1"."Hierarchy ID" = 'TTTTT') AND (Time.Status = 'Closed') ORDER BY saw_0, saw_1

As of my knowledge, you shouldn't get results set for any of views because of this error..!!
I see you are using 2 facts in the report.
And, dimensions you are using in this reports are confirmed dimensions to these 2 facts?
Are you mentioned proper content levels for each Fact LTSs?
Basic funda is: If fact and dimensions are joined directly, then you should mention the the level of granularity in Fact LTS. If not, you should mention total level of the dimensional hierarchy for the Fact LTS

Problems exporting metadata (using bridge).

Hello.
I'm trying to export metadata from OWB to Discoverer. I've a multidimensional model and now I want to explore it using Discoverer.
When I export metadata, OWB creates a file like:
BEGIN End User Layer Export
EUL_Version 3.1.92.0.7
EUL_Unique_Id 20030315095138
EUL_Characterset_WE8MSWIN1252
Define Object
Type BUSINESS AREA
Name AREA CASO 1
mName AREA CASO 1
mDescription Área de negocios del caso de estudio del almacén de comestibles.
mId
EndDefine Object
Define Object
This file can't read by Discoverer because not is a XML file. How can I export the .eex using XMI especification?
Thanks.

Juan Antonio,
What version of Warehouse Builder are you using?
It seems you have selected the Discoverer 3 bridge which may not generate an XML file (I am not sure about the Discoverer 3 format).
Anyway, you have to define a business area in OWB (or collection if you use OWB904) that contains the object definitions you want to export when you run the bridge.
Mar.

Exporting metadata from Lightroom to Excel

For all those out there wanting to export metadata from Lightroom to CSV, I have found a Fantastic Company www.pkzsoftware.com that sell their product for approx AUS $10.00 "Lightroom Metadata Explorer" it works perfectly and their customer service is just the best you will find anywhere, being a computer novice I had a few problems and they went out of their way to assist me to get exactly the data I needed. Can't speak highly enough of the Company.

John,
Thanks for your reply and the references to the tools. I ran the sqlLite Database Browser to look at the LR database, and to be honest it was pretty much gibberish to me. There's over 50 tables in the database and some quick browsing through them revealed data that would seem to require a knowledge of the database structure to extract. I'm a photographer with very good knowledge of how to use software tools to do my job, but I'm not a programmer and really don't have the time or the desire to become one.
My point is any good database software should have the capability to generate at least a flat file of the information contained within. In LR's case, I (and it seems others based on feature requests) would like to see a capability of exporting a CSV or tab-delimited file of the information contained in the side panels (i.e., keywords, the metadata browser, and the metadata panel for starters) on an image-by-image basis. I could then use the output in any of several other tools to do what I need.
Thanks again for your helpful links. Maybe someone can come up with a "CSV generator" using one of those tools that could be shared among LR users.

Exporting Metadata in V3.4.5 appears NOT to work

What I want to do is export selected metadata, or perhaps a metadata view, for selected images to a CSV file, or to a spreadsheet file for further analysis. No matter what I try I cannot get anything remotely useful. Here is what I get when selecting one image and choosing File -> Export -> Metadata:
Version Name
Title
Urgency
Categories
Suppl. Categories
Keywords
Instructions
Date Created
Contact Creator
Contact Job Title
City
State/Province
Country
Job Identifier
Headline
Provider
Source
Copyright Notice
Caption
Caption Writer
Rating
IPTC Subject Code
Usage Terms
Intellectual Genre
IPTC Scene
Location
ISO Country Code
Contact Address
Contact City
Contact State/Providence
Contact Postal Code
Contact Country
Contact Phone
Contact Email
Contact Website
Label
Latitude
Longitude
Altitude
AltitudeRef
_DSC2529
0
This is not useful. It contains data items I don't want and doesn't contain data items I actually want, such as lens used, shutter speed, focal length.
Has this ever worked? Is it broken in this version of Aperture only?
What am I missing?

Sorry to say, but that is how it has always been.
You can annote printed contact sheets with selected matadata from your predefined views, but if you want textfiles of selected metadata, you will have to write a script or an Automator workflow to extract the data. For example, I posted an automator workflow here, that extracts some metadata fields and writes them to a textfile for printing. If you know how to program a bit, you could adapt this to your needs:
Export EXIF Info to Printer or PDF?

Ediscovery Export : Metadata Consistency

Similar Messages

Maybe you are looking for