Hey Luca, Thanks! Yep, check out:
http://oodt.apache.org/components/maven/metadata/user/basic.html HTH! Cheers, Chris On Mar 30, 2011, at 2:06 PM, Cinquini, Luca (3880) wrote: > Hi Chris, > thanks for your answer - please find the policy files attached. To > answer your questions: > > On Mar 30, 2011, at 2:55 PM, Mattmann, Chris A (388J) wrote: > >> Hi Luca, >> >> Thanks for your questions! Answers inline below: >> >>> I have a question about how to use the metadata extracted by an >>> implementation of "FilemgrMetExtractor" when versioning a file that is >>> ingested by the File Manager. >>> >>> I have configured my File Manager to run a custom metadata extractor >>> ("NetCDFMetExtractor") and a custom versioner ("DRSVersioner"). I am >>> running the filemgr-client tool to ingest a netcdf file, please see the log >>> below. >>> >>> o First question: why is the versioner run twice ? It seems like the first >>> time it is run, it has access to all the metadata that has been previously >>> extracted by the NetCDFMetExtractor, but the second time it doesn't ? >> >> >> What does your NetCDFMetExtractor do? Does it call the DRSVersioner? How are >> you wiring the 2 together? I see from your command line below you are >> attaching these to the GenericFile product type? How did you set that up? >> Can I see an example of your policy files? That will help to diagnose what >> you're seeing. > The extractor and the versioner are not wired together via Java code, rather > through the file product-types.xml, where they are both defined for the > product type "GenericFile". >> >>> >>> o Second question: what is the relation between the metadata extracted by >>> the NetCDFMetExtractor and the argument to the --metadataFile option ? Is >>> there any way to serialize the output of the metadata extractor to a file >>> that is then ingested by the file manager ? >> >> The policy files will help with this. My guess is that you made the >> NetCDFExtractor a *server side* met extractor. You have the ability to do >> *client side* or *server side* extraction. From the FM client side, that's >> the extracted client side metadata, pre-baked in (via the --metadataFile >> param), or generated on the fly from a >> o.a.oodt.cas.metadata.extractors.CmdLineMetExtractor implementation, and >> piped in via the StdIngester, or via the crawler (AutoDetect, or >> MetExtractor). > > I think you probably have nailed the problem... so the metadata extractor > that is defined in "product-types.xml" only affects the server side > functionality ? Is there a good place where I can find how to setup the > CmdLineMetExtractor + StdIngester for the client side ? > > thanks a lot, > Luca > <elements.xml><product-type-element-map.xml><product-types.xml> >> >> Server side met is *derived after* the original client side met is sent >> along during the process of ingestion. >> >> HTH, >> CHris >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: [email protected] >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
