You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oodt.apache.org by JPSS GRAVITE <jp...@gmail.com> on 2012/02/08 21:18:46 UTC
CAS Curator - No metadata detected
Hi,
I am following Curator Basic User Guide to get a basic Curator interface up
and running. When I select a Test.mp3 file, I get "No Metadata detected"
error in the right pane (screenshot attached). I do see mp3extractor in the
drop down list.
I was able to run the python script to generate a valid xml file locally.
But, I am not able to get the results of running python script on the web
interface.
x@/usr/local/extractors/mp3extractor: ls -al
total 47016
drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
-rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
-rw-r--r-- 1 root staff 333 Feb 7 16:55 mp3PythonExtractor.config
-rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
-rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
--------------------------------------------------------
FYI: I noticed this guide had following errors:
> Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (
http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3)
> Under Extractor Setup --
Link to Extractor Basics Guide is broken in 2 places.
Need to Remove ' after \n
f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
Thank you.
Re: CAS Curator - No metadata detected
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Peyush,
On Feb 13, 2012, at 12:23 PM, JPSS GRAVITE wrote:
> Hey Chris,
>
> We are sharing this account. :)
>
> Following the guide, we made staging/products/mp3 and staging/metadata/mp3 folders. So, when we first look at the mp3 file in the staging area of the webapp, .met files are created in both of these folders.
Hmm, your context file below looks good. Can you try from scratch, by performing the following steps:
1. cd /oodt/FileManager/cas-filemgr/bin
2. ./filemgr stop
3. rm -rf ../catalog (assuming that is where your FM catalog is and that you are using Lucene for now)
Where does your FM product type policy store its products? Can you show me what
the value for repositoryPath is by catting
/oodt/FileManager/cas-filemgr/policy/product-types.xml
?
That will be the location of the actual product files. Is that set to /oodt/Curator/staging/products/mp3?
I think something funky is going on with some of the set paths, we'll figure it out and get it to only
ingest the product files, as it should.
Cheers,
Chris
>
> Here is my context file:
>
> <Context path="/my-curator"
> docBase="/Users/pjain/NASA/JPSS/OODT/apache-oodt-0.3-src/curator/target/cas-curator-0.3.war">
> <Parameter name="org.apache.oodt.security.sso.implClass"
> value="org.apache.oodt.security.sso.DummyImpl"/>
> <Parameter name="org.apache.oodt.cas.curator.projectName"
> value="My Project"/>
>
> <Parameter name="org.apache.oodt.cas.curator.stagingAreaPath"
> value="/oodt/Curator/staging/products"/>
>
> <Parameter name="org.apache.oodt.cas.curator.metAreaPath"
> value="/oodt/Curator/staging/metadata"/>
>
> <Parameter name="org.apache.oodt.cas.curator.metExtension"
> value=".met"/>
> <Parameter name="org.apache.oodt.cas.curator.metExtractorConf.uploadPath"
> value="/oodt/Curator/extractors" />
>
> <Parameter name="org.apache.oodt.cas.fm.url"
> value="http://localhost:9000"/>
>
> <Parameter name="org.apache.oodt.cas.curator.dataDefinition.uploadPath"
> value="/oodt/FileManager/cas-filemgr/policy" />
>
> <Parameter name="org.apache.oodt.cas.curator.fmProps"
> value="/oodt/FileManager/cas-filemgr/etc/filemgr.properties"/>
> </Context>
>
> Peyush
>
>
> On Sat, Feb 11, 2012 at 12:43 PM, Mattmann, Chris A (388J) <ch...@jpl.nasa.gov> wrote:
> Hey Peyush,
>
> Hehe, wasn't sure if this account was you (as it was labeled "JPSS Gravite") :)
>
> On Feb 9, 2012, at 11:48 AM, JPSS GRAVITE wrote:
>
> > Hi Chris,
> >
> > Actually, it turns out that the python script was not able to write .met file to the intended directory because of a permission issue. As soon as I fixed the permissions, it started working.
>
> Woot. Awesome.
>
> >
> > I noticed that .met files are created in both products/mp3 and metadata/mp3 folder.
>
> Meaning, that the met files are generated in both the staging area, and in the archive?
> That's odd, and shouldn't be happening. Can you pass along your curator.xml (context.xml)
> conf so I could see the properties that you are using?
>
> > Is there a reason why .met file is created in products/mp3? Because of this, on a web app page refresh, .met files also show up in the staging area.
>
> Yeah it shouldn't be doing this, it might be that the guide here is out of date:
>
> http://oodt.apache.org/components/maven/curator/user/basic.html
>
> How did you do the file ingestion? Can you take me through the sequence
> of events?
>
> I'm sure we'll figure this out.
>
> Cheers,
> Chris
>
> >
> >
> > On Wed, Feb 8, 2012 at 9:52 PM, Mattmann, Chris A (388J) <ch...@jpl.nasa.gov> wrote:
> > Hi there,
> >
> > Thanks for the feedback!
> >
> > Hmm, are you getting any specific errors in your Tomcat logs when you get no metadata
> > detected error? Also, can you verify that you have the following property set:
> >
> > org.apache.oodt.cas.curator.metAreaPath
> >
> > This should be set in your META-INF/context.xml file inside of the unpacked webapp,
> > or inside of a specific context.xml file that you configure in Tomcat. A couple of questions:
> >
> > 1. what value is that path set to?
> > 2. do you see a corresponding met file underneath org.apache.oodt.cas.curator.metAreaPath/mp3?
> > - if the answer to #2 is "no", then that's why you are getting the "No metadata detected error". It's not
> > exactly an error, it's just letting you know that there is no pre-computed metadata file that has been
> > generated, and thus it's not already there. To generate the met file, you click the "refresh" button in
> > the interface, which will run the mp3 extractor
> > - if the answer to #2 is "yes", then that definitely is an issue that we can look at.
> >
> > Let me know the answers to the above. Also thanks for the points to updates in the guide.
> > I'll open up corresponding JIRA issues and take a lead in getting those fixed!
> >
> > Cheers,
> > Chris
> >
> > On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
> >
> > > Hi,
> > >
> > > I am following Curator Basic User Guide to get a basic Curator interface up and running. When I select a Test.mp3 file, I get "No Metadata detected" error in the right pane (screenshot attached). I do see mp3extractor in the drop down list.
> > >
> > > I was able to run the python script to generate a valid xml file locally. But, I am not able to get the results of running python script on the web interface.
> > >
> > > x@/usr/local/extractors/mp3extractor: ls -al
> > > total 47016
> > > drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> > > drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> > > -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> > > -rw-r--r-- 1 root staff 333 Feb 7 16:55 mp3PythonExtractor.config
> > > -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> > > -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
> > >
> > > --------------------------------------------------------
> > > FYI: I noticed this guide had following errors:
> > > > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3)
> > > > Under Extractor Setup --
> > > Link to Extractor Basics Guide is broken in 2 places.
> > >
> > > Need to Remove ' after \n
> > > f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
> > >
> > >
> > > Thank you.
> > >
> > >
> > > <No Metadata Detected.png>
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: chris.a.mattmann@nasa.gov
> > 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: chris.a.mattmann@nasa.gov
> 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: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: CAS Curator - No metadata detected
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Peyush,
On Feb 13, 2012, at 12:23 PM, JPSS GRAVITE wrote:
> Hey Chris,
>
> We are sharing this account. :)
>
> Following the guide, we made staging/products/mp3 and staging/metadata/mp3 folders. So, when we first look at the mp3 file in the staging area of the webapp, .met files are created in both of these folders.
Hmm, your context file below looks good. Can you try from scratch, by performing the following steps:
1. cd /oodt/FileManager/cas-filemgr/bin
2. ./filemgr stop
3. rm -rf ../catalog (assuming that is where your FM catalog is and that you are using Lucene for now)
Where does your FM product type policy store its products? Can you show me what
the value for repositoryPath is by catting
/oodt/FileManager/cas-filemgr/policy/product-types.xml
?
That will be the location of the actual product files. Is that set to /oodt/Curator/staging/products/mp3?
I think something funky is going on with some of the set paths, we'll figure it out and get it to only
ingest the product files, as it should.
Cheers,
Chris
>
> Here is my context file:
>
> <Context path="/my-curator"
> docBase="/Users/pjain/NASA/JPSS/OODT/apache-oodt-0.3-src/curator/target/cas-curator-0.3.war">
> <Parameter name="org.apache.oodt.security.sso.implClass"
> value="org.apache.oodt.security.sso.DummyImpl"/>
> <Parameter name="org.apache.oodt.cas.curator.projectName"
> value="My Project"/>
>
> <Parameter name="org.apache.oodt.cas.curator.stagingAreaPath"
> value="/oodt/Curator/staging/products"/>
>
> <Parameter name="org.apache.oodt.cas.curator.metAreaPath"
> value="/oodt/Curator/staging/metadata"/>
>
> <Parameter name="org.apache.oodt.cas.curator.metExtension"
> value=".met"/>
> <Parameter name="org.apache.oodt.cas.curator.metExtractorConf.uploadPath"
> value="/oodt/Curator/extractors" />
>
> <Parameter name="org.apache.oodt.cas.fm.url"
> value="http://localhost:9000"/>
>
> <Parameter name="org.apache.oodt.cas.curator.dataDefinition.uploadPath"
> value="/oodt/FileManager/cas-filemgr/policy" />
>
> <Parameter name="org.apache.oodt.cas.curator.fmProps"
> value="/oodt/FileManager/cas-filemgr/etc/filemgr.properties"/>
> </Context>
>
> Peyush
>
>
> On Sat, Feb 11, 2012 at 12:43 PM, Mattmann, Chris A (388J) <ch...@jpl.nasa.gov> wrote:
> Hey Peyush,
>
> Hehe, wasn't sure if this account was you (as it was labeled "JPSS Gravite") :)
>
> On Feb 9, 2012, at 11:48 AM, JPSS GRAVITE wrote:
>
> > Hi Chris,
> >
> > Actually, it turns out that the python script was not able to write .met file to the intended directory because of a permission issue. As soon as I fixed the permissions, it started working.
>
> Woot. Awesome.
>
> >
> > I noticed that .met files are created in both products/mp3 and metadata/mp3 folder.
>
> Meaning, that the met files are generated in both the staging area, and in the archive?
> That's odd, and shouldn't be happening. Can you pass along your curator.xml (context.xml)
> conf so I could see the properties that you are using?
>
> > Is there a reason why .met file is created in products/mp3? Because of this, on a web app page refresh, .met files also show up in the staging area.
>
> Yeah it shouldn't be doing this, it might be that the guide here is out of date:
>
> http://oodt.apache.org/components/maven/curator/user/basic.html
>
> How did you do the file ingestion? Can you take me through the sequence
> of events?
>
> I'm sure we'll figure this out.
>
> Cheers,
> Chris
>
> >
> >
> > On Wed, Feb 8, 2012 at 9:52 PM, Mattmann, Chris A (388J) <ch...@jpl.nasa.gov> wrote:
> > Hi there,
> >
> > Thanks for the feedback!
> >
> > Hmm, are you getting any specific errors in your Tomcat logs when you get no metadata
> > detected error? Also, can you verify that you have the following property set:
> >
> > org.apache.oodt.cas.curator.metAreaPath
> >
> > This should be set in your META-INF/context.xml file inside of the unpacked webapp,
> > or inside of a specific context.xml file that you configure in Tomcat. A couple of questions:
> >
> > 1. what value is that path set to?
> > 2. do you see a corresponding met file underneath org.apache.oodt.cas.curator.metAreaPath/mp3?
> > - if the answer to #2 is "no", then that's why you are getting the "No metadata detected error". It's not
> > exactly an error, it's just letting you know that there is no pre-computed metadata file that has been
> > generated, and thus it's not already there. To generate the met file, you click the "refresh" button in
> > the interface, which will run the mp3 extractor
> > - if the answer to #2 is "yes", then that definitely is an issue that we can look at.
> >
> > Let me know the answers to the above. Also thanks for the points to updates in the guide.
> > I'll open up corresponding JIRA issues and take a lead in getting those fixed!
> >
> > Cheers,
> > Chris
> >
> > On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
> >
> > > Hi,
> > >
> > > I am following Curator Basic User Guide to get a basic Curator interface up and running. When I select a Test.mp3 file, I get "No Metadata detected" error in the right pane (screenshot attached). I do see mp3extractor in the drop down list.
> > >
> > > I was able to run the python script to generate a valid xml file locally. But, I am not able to get the results of running python script on the web interface.
> > >
> > > x@/usr/local/extractors/mp3extractor: ls -al
> > > total 47016
> > > drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> > > drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> > > -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> > > -rw-r--r-- 1 root staff 333 Feb 7 16:55 mp3PythonExtractor.config
> > > -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> > > -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
> > >
> > > --------------------------------------------------------
> > > FYI: I noticed this guide had following errors:
> > > > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3)
> > > > Under Extractor Setup --
> > > Link to Extractor Basics Guide is broken in 2 places.
> > >
> > > Need to Remove ' after \n
> > > f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
> > >
> > >
> > > Thank you.
> > >
> > >
> > > <No Metadata Detected.png>
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: chris.a.mattmann@nasa.gov
> > 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: chris.a.mattmann@nasa.gov
> 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: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: CAS Curator - No metadata detected
Posted by JPSS GRAVITE <jp...@gmail.com>.
Hey Chris,
We are sharing this account. :)
Following the guide, we made staging/products/mp3 and staging/metadata/mp3
folders. So, when we first look at the mp3 file in the staging area of the
webapp, .met files are created in both of these folders.
Here is my context file:
<Context path="/my-curator"
docBase="/Users/pjain/NASA/JPSS/OODT/apache-oodt-0.3-src/curator/target/cas-curator-0.3.war">
<Parameter name="org.apache.oodt.security.sso.implClass"
value="org.apache.oodt.security.sso.DummyImpl"/>
<Parameter name="org.apache.oodt.cas.curator.projectName"
value="My Project"/>
<Parameter name="org.apache.oodt.cas.curator.stagingAreaPath"
value="/oodt/Curator/staging/products"/>
<Parameter name="org.apache.oodt.cas.curator.metAreaPath"
value="/oodt/Curator/staging/metadata"/>
<Parameter name="org.apache.oodt.cas.curator.metExtension"
value=".met"/>
<Parameter name="org.apache.oodt.cas.curator.metExtractorConf.uploadPath"
value="/oodt/Curator/extractors" />
<Parameter name="org.apache.oodt.cas.fm.url"
value="http://localhost:9000"/>
<Parameter name="org.apache.oodt.cas.curator.dataDefinition.uploadPath"
value="/oodt/FileManager/cas-filemgr/policy" />
<Parameter name="org.apache.oodt.cas.curator.fmProps"
value="/oodt/FileManager/cas-filemgr/etc/filemgr.properties"/>
</Context>
Peyush
On Sat, Feb 11, 2012 at 12:43 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hey Peyush,
>
> Hehe, wasn't sure if this account was you (as it was labeled "JPSS
> Gravite") :)
>
> On Feb 9, 2012, at 11:48 AM, JPSS GRAVITE wrote:
>
> > Hi Chris,
> >
> > Actually, it turns out that the python script was not able to write .met
> file to the intended directory because of a permission issue. As soon as I
> fixed the permissions, it started working.
>
> Woot. Awesome.
>
> >
> > I noticed that .met files are created in both products/mp3 and
> metadata/mp3 folder.
>
> Meaning, that the met files are generated in both the staging area, and in
> the archive?
> That's odd, and shouldn't be happening. Can you pass along your
> curator.xml (context.xml)
> conf so I could see the properties that you are using?
>
> > Is there a reason why .met file is created in products/mp3? Because of
> this, on a web app page refresh, .met files also show up in the staging
> area.
>
> Yeah it shouldn't be doing this, it might be that the guide here is out of
> date:
>
> http://oodt.apache.org/components/maven/curator/user/basic.html
>
> How did you do the file ingestion? Can you take me through the sequence
> of events?
>
> I'm sure we'll figure this out.
>
> Cheers,
> Chris
>
> >
> >
> > On Wed, Feb 8, 2012 at 9:52 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> > Hi there,
> >
> > Thanks for the feedback!
> >
> > Hmm, are you getting any specific errors in your Tomcat logs when you
> get no metadata
> > detected error? Also, can you verify that you have the following
> property set:
> >
> > org.apache.oodt.cas.curator.metAreaPath
> >
> > This should be set in your META-INF/context.xml file inside of the
> unpacked webapp,
> > or inside of a specific context.xml file that you configure in Tomcat. A
> couple of questions:
> >
> > 1. what value is that path set to?
> > 2. do you see a corresponding met file underneath
> org.apache.oodt.cas.curator.metAreaPath/mp3?
> > - if the answer to #2 is "no", then that's why you are getting the "No
> metadata detected error". It's not
> > exactly an error, it's just letting you know that there is no
> pre-computed metadata file that has been
> > generated, and thus it's not already there. To generate the met file,
> you click the "refresh" button in
> > the interface, which will run the mp3 extractor
> > - if the answer to #2 is "yes", then that definitely is an issue that
> we can look at.
> >
> > Let me know the answers to the above. Also thanks for the points to
> updates in the guide.
> > I'll open up corresponding JIRA issues and take a lead in getting those
> fixed!
> >
> > Cheers,
> > Chris
> >
> > On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
> >
> > > Hi,
> > >
> > > I am following Curator Basic User Guide to get a basic Curator
> interface up and running. When I select a Test.mp3 file, I get "No Metadata
> detected" error in the right pane (screenshot attached). I do see
> mp3extractor in the drop down list.
> > >
> > > I was able to run the python script to generate a valid xml file
> locally. But, I am not able to get the results of running python script on
> the web interface.
> > >
> > > x@/usr/local/extractors/mp3extractor: ls -al
> > > total 47016
> > > drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> > > drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> > > -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> > > -rw-r--r-- 1 root staff 333 Feb 7 16:55
> mp3PythonExtractor.config
> > > -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> > > -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
> > >
> > > --------------------------------------------------------
> > > FYI: I noticed this guide had following errors:
> > > > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (
> http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3
> )
> > > > Under Extractor Setup --
> > > Link to Extractor Basics Guide is broken in 2 places.
> > >
> > > Need to Remove ' after \n
> > > f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
> > >
> > >
> > > Thank you.
> > >
> > >
> > > <No Metadata Detected.png>
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: chris.a.mattmann@nasa.gov
> > 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: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: CAS Curator - No metadata detected
Posted by JPSS GRAVITE <jp...@gmail.com>.
Hey Chris,
We are sharing this account. :)
Following the guide, we made staging/products/mp3 and staging/metadata/mp3
folders. So, when we first look at the mp3 file in the staging area of the
webapp, .met files are created in both of these folders.
Here is my context file:
<Context path="/my-curator"
docBase="/Users/pjain/NASA/JPSS/OODT/apache-oodt-0.3-src/curator/target/cas-curator-0.3.war">
<Parameter name="org.apache.oodt.security.sso.implClass"
value="org.apache.oodt.security.sso.DummyImpl"/>
<Parameter name="org.apache.oodt.cas.curator.projectName"
value="My Project"/>
<Parameter name="org.apache.oodt.cas.curator.stagingAreaPath"
value="/oodt/Curator/staging/products"/>
<Parameter name="org.apache.oodt.cas.curator.metAreaPath"
value="/oodt/Curator/staging/metadata"/>
<Parameter name="org.apache.oodt.cas.curator.metExtension"
value=".met"/>
<Parameter name="org.apache.oodt.cas.curator.metExtractorConf.uploadPath"
value="/oodt/Curator/extractors" />
<Parameter name="org.apache.oodt.cas.fm.url"
value="http://localhost:9000"/>
<Parameter name="org.apache.oodt.cas.curator.dataDefinition.uploadPath"
value="/oodt/FileManager/cas-filemgr/policy" />
<Parameter name="org.apache.oodt.cas.curator.fmProps"
value="/oodt/FileManager/cas-filemgr/etc/filemgr.properties"/>
</Context>
Peyush
On Sat, Feb 11, 2012 at 12:43 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hey Peyush,
>
> Hehe, wasn't sure if this account was you (as it was labeled "JPSS
> Gravite") :)
>
> On Feb 9, 2012, at 11:48 AM, JPSS GRAVITE wrote:
>
> > Hi Chris,
> >
> > Actually, it turns out that the python script was not able to write .met
> file to the intended directory because of a permission issue. As soon as I
> fixed the permissions, it started working.
>
> Woot. Awesome.
>
> >
> > I noticed that .met files are created in both products/mp3 and
> metadata/mp3 folder.
>
> Meaning, that the met files are generated in both the staging area, and in
> the archive?
> That's odd, and shouldn't be happening. Can you pass along your
> curator.xml (context.xml)
> conf so I could see the properties that you are using?
>
> > Is there a reason why .met file is created in products/mp3? Because of
> this, on a web app page refresh, .met files also show up in the staging
> area.
>
> Yeah it shouldn't be doing this, it might be that the guide here is out of
> date:
>
> http://oodt.apache.org/components/maven/curator/user/basic.html
>
> How did you do the file ingestion? Can you take me through the sequence
> of events?
>
> I'm sure we'll figure this out.
>
> Cheers,
> Chris
>
> >
> >
> > On Wed, Feb 8, 2012 at 9:52 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> > Hi there,
> >
> > Thanks for the feedback!
> >
> > Hmm, are you getting any specific errors in your Tomcat logs when you
> get no metadata
> > detected error? Also, can you verify that you have the following
> property set:
> >
> > org.apache.oodt.cas.curator.metAreaPath
> >
> > This should be set in your META-INF/context.xml file inside of the
> unpacked webapp,
> > or inside of a specific context.xml file that you configure in Tomcat. A
> couple of questions:
> >
> > 1. what value is that path set to?
> > 2. do you see a corresponding met file underneath
> org.apache.oodt.cas.curator.metAreaPath/mp3?
> > - if the answer to #2 is "no", then that's why you are getting the "No
> metadata detected error". It's not
> > exactly an error, it's just letting you know that there is no
> pre-computed metadata file that has been
> > generated, and thus it's not already there. To generate the met file,
> you click the "refresh" button in
> > the interface, which will run the mp3 extractor
> > - if the answer to #2 is "yes", then that definitely is an issue that
> we can look at.
> >
> > Let me know the answers to the above. Also thanks for the points to
> updates in the guide.
> > I'll open up corresponding JIRA issues and take a lead in getting those
> fixed!
> >
> > Cheers,
> > Chris
> >
> > On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
> >
> > > Hi,
> > >
> > > I am following Curator Basic User Guide to get a basic Curator
> interface up and running. When I select a Test.mp3 file, I get "No Metadata
> detected" error in the right pane (screenshot attached). I do see
> mp3extractor in the drop down list.
> > >
> > > I was able to run the python script to generate a valid xml file
> locally. But, I am not able to get the results of running python script on
> the web interface.
> > >
> > > x@/usr/local/extractors/mp3extractor: ls -al
> > > total 47016
> > > drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> > > drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> > > -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> > > -rw-r--r-- 1 root staff 333 Feb 7 16:55
> mp3PythonExtractor.config
> > > -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> > > -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
> > >
> > > --------------------------------------------------------
> > > FYI: I noticed this guide had following errors:
> > > > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (
> http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3
> )
> > > > Under Extractor Setup --
> > > Link to Extractor Basics Guide is broken in 2 places.
> > >
> > > Need to Remove ' after \n
> > > f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
> > >
> > >
> > > Thank you.
> > >
> > >
> > > <No Metadata Detected.png>
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: chris.a.mattmann@nasa.gov
> > 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: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: CAS Curator - No metadata detected
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Peyush,
Hehe, wasn't sure if this account was you (as it was labeled "JPSS Gravite") :)
On Feb 9, 2012, at 11:48 AM, JPSS GRAVITE wrote:
> Hi Chris,
>
> Actually, it turns out that the python script was not able to write .met file to the intended directory because of a permission issue. As soon as I fixed the permissions, it started working.
Woot. Awesome.
>
> I noticed that .met files are created in both products/mp3 and metadata/mp3 folder.
Meaning, that the met files are generated in both the staging area, and in the archive?
That's odd, and shouldn't be happening. Can you pass along your curator.xml (context.xml)
conf so I could see the properties that you are using?
> Is there a reason why .met file is created in products/mp3? Because of this, on a web app page refresh, .met files also show up in the staging area.
Yeah it shouldn't be doing this, it might be that the guide here is out of date:
http://oodt.apache.org/components/maven/curator/user/basic.html
How did you do the file ingestion? Can you take me through the sequence
of events?
I'm sure we'll figure this out.
Cheers,
Chris
>
>
> On Wed, Feb 8, 2012 at 9:52 PM, Mattmann, Chris A (388J) <ch...@jpl.nasa.gov> wrote:
> Hi there,
>
> Thanks for the feedback!
>
> Hmm, are you getting any specific errors in your Tomcat logs when you get no metadata
> detected error? Also, can you verify that you have the following property set:
>
> org.apache.oodt.cas.curator.metAreaPath
>
> This should be set in your META-INF/context.xml file inside of the unpacked webapp,
> or inside of a specific context.xml file that you configure in Tomcat. A couple of questions:
>
> 1. what value is that path set to?
> 2. do you see a corresponding met file underneath org.apache.oodt.cas.curator.metAreaPath/mp3?
> - if the answer to #2 is "no", then that's why you are getting the "No metadata detected error". It's not
> exactly an error, it's just letting you know that there is no pre-computed metadata file that has been
> generated, and thus it's not already there. To generate the met file, you click the "refresh" button in
> the interface, which will run the mp3 extractor
> - if the answer to #2 is "yes", then that definitely is an issue that we can look at.
>
> Let me know the answers to the above. Also thanks for the points to updates in the guide.
> I'll open up corresponding JIRA issues and take a lead in getting those fixed!
>
> Cheers,
> Chris
>
> On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
>
> > Hi,
> >
> > I am following Curator Basic User Guide to get a basic Curator interface up and running. When I select a Test.mp3 file, I get "No Metadata detected" error in the right pane (screenshot attached). I do see mp3extractor in the drop down list.
> >
> > I was able to run the python script to generate a valid xml file locally. But, I am not able to get the results of running python script on the web interface.
> >
> > x@/usr/local/extractors/mp3extractor: ls -al
> > total 47016
> > drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> > drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> > -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> > -rw-r--r-- 1 root staff 333 Feb 7 16:55 mp3PythonExtractor.config
> > -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> > -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
> >
> > --------------------------------------------------------
> > FYI: I noticed this guide had following errors:
> > > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3)
> > > Under Extractor Setup --
> > Link to Extractor Basics Guide is broken in 2 places.
> >
> > Need to Remove ' after \n
> > f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
> >
> >
> > Thank you.
> >
> >
> > <No Metadata Detected.png>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> 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: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: CAS Curator - No metadata detected
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Peyush,
Hehe, wasn't sure if this account was you (as it was labeled "JPSS Gravite") :)
On Feb 9, 2012, at 11:48 AM, JPSS GRAVITE wrote:
> Hi Chris,
>
> Actually, it turns out that the python script was not able to write .met file to the intended directory because of a permission issue. As soon as I fixed the permissions, it started working.
Woot. Awesome.
>
> I noticed that .met files are created in both products/mp3 and metadata/mp3 folder.
Meaning, that the met files are generated in both the staging area, and in the archive?
That's odd, and shouldn't be happening. Can you pass along your curator.xml (context.xml)
conf so I could see the properties that you are using?
> Is there a reason why .met file is created in products/mp3? Because of this, on a web app page refresh, .met files also show up in the staging area.
Yeah it shouldn't be doing this, it might be that the guide here is out of date:
http://oodt.apache.org/components/maven/curator/user/basic.html
How did you do the file ingestion? Can you take me through the sequence
of events?
I'm sure we'll figure this out.
Cheers,
Chris
>
>
> On Wed, Feb 8, 2012 at 9:52 PM, Mattmann, Chris A (388J) <ch...@jpl.nasa.gov> wrote:
> Hi there,
>
> Thanks for the feedback!
>
> Hmm, are you getting any specific errors in your Tomcat logs when you get no metadata
> detected error? Also, can you verify that you have the following property set:
>
> org.apache.oodt.cas.curator.metAreaPath
>
> This should be set in your META-INF/context.xml file inside of the unpacked webapp,
> or inside of a specific context.xml file that you configure in Tomcat. A couple of questions:
>
> 1. what value is that path set to?
> 2. do you see a corresponding met file underneath org.apache.oodt.cas.curator.metAreaPath/mp3?
> - if the answer to #2 is "no", then that's why you are getting the "No metadata detected error". It's not
> exactly an error, it's just letting you know that there is no pre-computed metadata file that has been
> generated, and thus it's not already there. To generate the met file, you click the "refresh" button in
> the interface, which will run the mp3 extractor
> - if the answer to #2 is "yes", then that definitely is an issue that we can look at.
>
> Let me know the answers to the above. Also thanks for the points to updates in the guide.
> I'll open up corresponding JIRA issues and take a lead in getting those fixed!
>
> Cheers,
> Chris
>
> On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
>
> > Hi,
> >
> > I am following Curator Basic User Guide to get a basic Curator interface up and running. When I select a Test.mp3 file, I get "No Metadata detected" error in the right pane (screenshot attached). I do see mp3extractor in the drop down list.
> >
> > I was able to run the python script to generate a valid xml file locally. But, I am not able to get the results of running python script on the web interface.
> >
> > x@/usr/local/extractors/mp3extractor: ls -al
> > total 47016
> > drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> > drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> > -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> > -rw-r--r-- 1 root staff 333 Feb 7 16:55 mp3PythonExtractor.config
> > -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> > -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
> >
> > --------------------------------------------------------
> > FYI: I noticed this guide had following errors:
> > > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3)
> > > Under Extractor Setup --
> > Link to Extractor Basics Guide is broken in 2 places.
> >
> > Need to Remove ' after \n
> > f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
> >
> >
> > Thank you.
> >
> >
> > <No Metadata Detected.png>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> 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: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: CAS Curator - No metadata detected
Posted by JPSS GRAVITE <jp...@gmail.com>.
Hi Chris,
Actually, it turns out that the python script was not able to write .met
file to the intended directory because of a permission issue. As soon as I
fixed the permissions, it started working.
I noticed that .met files are created in both products/mp3 and metadata/mp3
folder. Is there a reason why .met file is created in products/mp3? Because
of this, on a web app page refresh, .met files also show up in the staging
area.
Thank you,
Peyush
On Wed, Feb 8, 2012 at 9:52 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hi there,
>
> Thanks for the feedback!
>
> Hmm, are you getting any specific errors in your Tomcat logs when you get
> no metadata
> detected error? Also, can you verify that you have the following property
> set:
>
> org.apache.oodt.cas.curator.metAreaPath
>
> This should be set in your META-INF/context.xml file inside of the
> unpacked webapp,
> or inside of a specific context.xml file that you configure in Tomcat. A
> couple of questions:
>
> 1. what value is that path set to?
> 2. do you see a corresponding met file underneath
> org.apache.oodt.cas.curator.metAreaPath/mp3?
> - if the answer to #2 is "no", then that's why you are getting the "No
> metadata detected error". It's not
> exactly an error, it's just letting you know that there is no pre-computed
> metadata file that has been
> generated, and thus it's not already there. To generate the met file, you
> click the "refresh" button in
> the interface, which will run the mp3 extractor
> - if the answer to #2 is "yes", then that definitely is an issue that
> we can look at.
>
> Let me know the answers to the above. Also thanks for the points to
> updates in the guide.
> I'll open up corresponding JIRA issues and take a lead in getting those
> fixed!
>
> Cheers,
> Chris
>
> On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
>
> > Hi,
> >
> > I am following Curator Basic User Guide to get a basic Curator interface
> up and running. When I select a Test.mp3 file, I get "No Metadata detected"
> error in the right pane (screenshot attached). I do see mp3extractor in the
> drop down list.
> >
> > I was able to run the python script to generate a valid xml file
> locally. But, I am not able to get the results of running python script on
> the web interface.
> >
> > x@/usr/local/extractors/mp3extractor: ls -al
> > total 47016
> > drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> > drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> > -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> > -rw-r--r-- 1 root staff 333 Feb 7 16:55
> mp3PythonExtractor.config
> > -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> > -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
> >
> > --------------------------------------------------------
> > FYI: I noticed this guide had following errors:
> > > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (
> http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3
> )
> > > Under Extractor Setup --
> > Link to Extractor Basics Guide is broken in 2 places.
> >
> > Need to Remove ' after \n
> > f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
> >
> >
> > Thank you.
> >
> >
> > <No Metadata Detected.png>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: CAS Curator - No metadata detected
Posted by JPSS GRAVITE <jp...@gmail.com>.
Hi Chris,
Actually, it turns out that the python script was not able to write .met
file to the intended directory because of a permission issue. As soon as I
fixed the permissions, it started working.
I noticed that .met files are created in both products/mp3 and metadata/mp3
folder. Is there a reason why .met file is created in products/mp3? Because
of this, on a web app page refresh, .met files also show up in the staging
area.
Thank you,
Peyush
On Wed, Feb 8, 2012 at 9:52 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hi there,
>
> Thanks for the feedback!
>
> Hmm, are you getting any specific errors in your Tomcat logs when you get
> no metadata
> detected error? Also, can you verify that you have the following property
> set:
>
> org.apache.oodt.cas.curator.metAreaPath
>
> This should be set in your META-INF/context.xml file inside of the
> unpacked webapp,
> or inside of a specific context.xml file that you configure in Tomcat. A
> couple of questions:
>
> 1. what value is that path set to?
> 2. do you see a corresponding met file underneath
> org.apache.oodt.cas.curator.metAreaPath/mp3?
> - if the answer to #2 is "no", then that's why you are getting the "No
> metadata detected error". It's not
> exactly an error, it's just letting you know that there is no pre-computed
> metadata file that has been
> generated, and thus it's not already there. To generate the met file, you
> click the "refresh" button in
> the interface, which will run the mp3 extractor
> - if the answer to #2 is "yes", then that definitely is an issue that
> we can look at.
>
> Let me know the answers to the above. Also thanks for the points to
> updates in the guide.
> I'll open up corresponding JIRA issues and take a lead in getting those
> fixed!
>
> Cheers,
> Chris
>
> On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
>
> > Hi,
> >
> > I am following Curator Basic User Guide to get a basic Curator interface
> up and running. When I select a Test.mp3 file, I get "No Metadata detected"
> error in the right pane (screenshot attached). I do see mp3extractor in the
> drop down list.
> >
> > I was able to run the python script to generate a valid xml file
> locally. But, I am not able to get the results of running python script on
> the web interface.
> >
> > x@/usr/local/extractors/mp3extractor: ls -al
> > total 47016
> > drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> > drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> > -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> > -rw-r--r-- 1 root staff 333 Feb 7 16:55
> mp3PythonExtractor.config
> > -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> > -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
> >
> > --------------------------------------------------------
> > FYI: I noticed this guide had following errors:
> > > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (
> http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3
> )
> > > Under Extractor Setup --
> > Link to Extractor Basics Guide is broken in 2 places.
> >
> > Need to Remove ' after \n
> > f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
> >
> >
> > Thank you.
> >
> >
> > <No Metadata Detected.png>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: CAS Curator - No metadata detected
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi there,
Thanks for the feedback!
Hmm, are you getting any specific errors in your Tomcat logs when you get no metadata
detected error? Also, can you verify that you have the following property set:
org.apache.oodt.cas.curator.metAreaPath
This should be set in your META-INF/context.xml file inside of the unpacked webapp,
or inside of a specific context.xml file that you configure in Tomcat. A couple of questions:
1. what value is that path set to?
2. do you see a corresponding met file underneath org.apache.oodt.cas.curator.metAreaPath/mp3?
- if the answer to #2 is "no", then that's why you are getting the "No metadata detected error". It's not
exactly an error, it's just letting you know that there is no pre-computed metadata file that has been
generated, and thus it's not already there. To generate the met file, you click the "refresh" button in
the interface, which will run the mp3 extractor
- if the answer to #2 is "yes", then that definitely is an issue that we can look at.
Let me know the answers to the above. Also thanks for the points to updates in the guide.
I'll open up corresponding JIRA issues and take a lead in getting those fixed!
Cheers,
Chris
On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
> Hi,
>
> I am following Curator Basic User Guide to get a basic Curator interface up and running. When I select a Test.mp3 file, I get "No Metadata detected" error in the right pane (screenshot attached). I do see mp3extractor in the drop down list.
>
> I was able to run the python script to generate a valid xml file locally. But, I am not able to get the results of running python script on the web interface.
>
> x@/usr/local/extractors/mp3extractor: ls -al
> total 47016
> drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> -rw-r--r-- 1 root staff 333 Feb 7 16:55 mp3PythonExtractor.config
> -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
>
> --------------------------------------------------------
> FYI: I noticed this guide had following errors:
> > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3)
> > Under Extractor Setup --
> Link to Extractor Basics Guide is broken in 2 places.
>
> Need to Remove ' after \n
> f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
>
>
> Thank you.
>
>
> <No Metadata Detected.png>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: CAS Curator - No metadata detected
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi there,
Thanks for the feedback!
Hmm, are you getting any specific errors in your Tomcat logs when you get no metadata
detected error? Also, can you verify that you have the following property set:
org.apache.oodt.cas.curator.metAreaPath
This should be set in your META-INF/context.xml file inside of the unpacked webapp,
or inside of a specific context.xml file that you configure in Tomcat. A couple of questions:
1. what value is that path set to?
2. do you see a corresponding met file underneath org.apache.oodt.cas.curator.metAreaPath/mp3?
- if the answer to #2 is "no", then that's why you are getting the "No metadata detected error". It's not
exactly an error, it's just letting you know that there is no pre-computed metadata file that has been
generated, and thus it's not already there. To generate the met file, you click the "refresh" button in
the interface, which will run the mp3 extractor
- if the answer to #2 is "yes", then that definitely is an issue that we can look at.
Let me know the answers to the above. Also thanks for the points to updates in the guide.
I'll open up corresponding JIRA issues and take a lead in getting those fixed!
Cheers,
Chris
On Feb 8, 2012, at 12:18 PM, JPSS GRAVITE wrote:
> Hi,
>
> I am following Curator Basic User Guide to get a basic Curator interface up and running. When I select a Test.mp3 file, I get "No Metadata detected" error in the right pane (screenshot attached). I do see mp3extractor in the drop down list.
>
> I was able to run the python script to generate a valid xml file locally. But, I am not able to get the results of running python script on the web interface.
>
> x@/usr/local/extractors/mp3extractor: ls -al
> total 47016
> drwxr-xr-x 6 root staff 204 Feb 7 17:06 .
> drwxr-xr-x 3 root staff 102 Feb 7 14:59 ..
> -rw-r--r-- 1 root staff 163 Feb 7 16:57 config.properties
> -rw-r--r-- 1 root staff 333 Feb 7 16:55 mp3PythonExtractor.config
> -rwxr-xr-x 1 root staff 871 Feb 7 16:47 mp3PythonExtractor.py
> -rw-r--r--@ 1 root staff 24056779 Feb 7 15:12 tika-app-1.0.jar
>
> --------------------------------------------------------
> FYI: I noticed this guide had following errors:
> > Under Staging Area Setup -- Link to Bach-SuiteNo2.mp3 is broken (http://incubator.apache.org/oodt/components/curator/media/Bach-SuiteNo2.mp3)
> > Under Extractor Setup --
> Link to Extractor Basics Guide is broken in 2 places.
>
> Need to Remove ' after \n
> f.write(fileName+'</val></keyval>\n'<keyval><key>FileLocation')
>
>
> Thank you.
>
>
> <No Metadata Detected.png>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++