Perfect Brian, exactly. Rishi, check out the push_pull_framework.properties file. It mentions which met fields push pull adds to the info.tmp files and then like Brian said, you use cas-crawler to augment and extend and add more.
Cheers, Chris On Nov 10, 2012, at 7:08 AM, Brian Foster wrote: > > Hey Rishi, > > You will need to use both cas-pushpull and cas-crawler to accomplish this... > > cas-pushpull: Used to for downloading files from remote sites to you local > systems... the .tmp files contain cas-pushpull's known metadata and you can > configure which of the known metadata gets written out or if a .tmp file gets > created at all... however you can add custom metadata fields to it. > > cas-crawler: Allows for metadata extraction (custom metadata) from files on > your local system... and then allows you to ingest them into the filemgr > (optionally can be turned off) > > HTH > -brian > > On Nov 08, 2012, at 06:11 PM, "Verma, Rishi (388J)" > <[email protected]> wrote: > >> Hi All - >> >> I'm wondering if anyone has experience with, or knows the details of how to >> use custom MetExtractors on products that are remotely downloaded via >> PushPull. >> >> By default, PushPull performs some basic met-extraction and creates a ".tmp" >> file associated with downloaded products, but I'm wondering whether this met >> generation step is customizable. >> >> I've looked through the configuration files (e.g. [1], [2]) as well as the >> code for PushPull, but I can't seem to locate configuration parameters to >> support the invocation of custom met extractors on downloaded data. >> >> If any of you have experience with this, or can point me on where to look, >> I'd really appreciate it. >> >> Thanks! >> Rishi >> >> -- >> [1] >> http://svn.apache.org/repos/asf/oodt/trunk/pushpull/src/main/resources/push_pull_framework.properties >> >> [2] >> http://svn.apache.org/repos/asf/oodt/trunk/pushpull/src/main/resources/examples/
