Thanks Arthi for your help

Yes it worked now

best regards
tarandeep


On Tue, Jul 16, 2013 at 3:33 PM, <arthi.ven...@wipro.com> wrote:

>  Hi Tarandeep****
>
> Even I got a similar error.****
>
> On debugging figured out that the permissions are not there.****
>
> ** **
>
> Just add –u admin:admin to command and it should work.****
>
> ** **
>
> Thanks and Rgds,****
>
> Arthi****
>
> ** **
>
> P.S.  Marking the community also as I spent quite some time figuring this
> out and may benefit someone else.****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Sawhney, Tarandeep Singh [mailto:tsawh...@innodata.com]
> *Sent:* Tuesday, July 16, 2013 2:57 PM
>
> *To:* arthi venkataraman (WT01 - CTO Office)
> *Subject:* Re: Re : Custom Vocabulary****
>
> ** **
>
> Hi Arthi****
>
> ** **
>
> I believe you have used SolrYard in your configurations****
>
> ** **
>
> I intially used ClerezzaYard but ran into some issue, so i now tried using
> SolrYard****
>
> ** **
>
> Did you encounter any error while loading entities in your SolrYard ?****
>
> ** **
>
> We are getting a error message below on the command prompt. Can you please
> take a look and let me know if you faced such an error and how did you
> resolve it.****
>
> ** **
>
> *D:\Conde Nast Ontology>curl -i -X POST -H
> "Content-Type:application/rdf+xml" -T*****
>
> *{stanbol_sample.rdf} "
> http://localhost:9090/entityhub/site/testsolr/entity"*****
>
> *HTTP/1.1 100 Continue*****
>
> ** **
>
> *HTTP/1.1 500 Internal Server Error*****
>
> *Accept: application/json*****
>
> *Content-Type: text/plain*****
>
> *Transfer-Encoding: chunked*****
>
> *Server: Jetty(6.1.x)*****
>
> ** **
>
> *Unable to store parsed Entities to ManagedSite testsolr because of an
> error (Mes*****
>
> *sage: Exception while adding Documents to the Solr Server!)*****
>
> ** **
>
> best regards****
>
> tarandeep****
>
> ** **
>
> On Tue, Jul 16, 2013 at 12:25 PM, Sawhney, Tarandeep Singh <
> tsawh...@innodata.com> wrote:****
>
> Thanks so much Arthi****
>
> ** **
>
> best regards****
>
> tarandeep****
>
> ** **
>
> On Tue, Jul 16, 2013 at 12:23 PM, <arthi.ven...@wipro.com> wrote:****
>
> Sure Taran****
>
> Will update once I have tried****
>
> Currently Iam not using NER.****
>
>  ****
>
> Rgds****
>
> Arthi****
>
>  ****
>
>  ****
>
>  ****
>
> *From:* Sawhney, Tarandeep Singh [mailto:tsawh...@innodata.com]
> *Sent:* Tuesday, July 16, 2013 12:21 PM
> *To:* arthi venkataraman (WT01 - CTO Office)
> *Subject:* Re: Re : Custom Vocabulary****
>
>  ****
>
> Hi Arthi****
>
> i am just curious so may i request to please try to enhance text with name
> like "Rama sharma" after modifying your SKOS. Are you able to extract and
> link with custom entity in this case. Also, are you using NER entity
> linking engine ?  ****
>
> Can you please let me know****
>
> best regards,
> taran****
>
> On Jul 16, 2013 12:07 PM, <arthi.ven...@wipro.com> wrote:****
>
> Hi Rupert,
> Thanks a lot for this information.
> I created a simple set of concepts using SKOS and Iam now able to see the
> simple concepts
> I have defined when I run the sentence through the enhancer.
>
>
> Thanks and Rgds,
> Arthi
>
>
>
> Hi Arthi
>
> Regarding your data:
>
>   <rdf:Description rdf:about="#Rama">
>     <NinoNumber
> rdf:datatype="http://www.w3.org/2001/XMLSchema#int";>0</NinoNumber>
>     <rdf:type rdf:resource="#Person"/>
>     <owns rdf:resource="#Policy_2"/>
>     <dob rdf:datatype="http://www.w3.org/2001/XMLSchema#date
> ">2000-07-11</dob>
>     <city rdf:datatype="http://www.w3.org/2001/XMLSchema#string";></city>
>     <Name rdf:datatype="http://www.w3.org/2001/XMLSchema#string";></Name>
>    <customerId rdf:datatype="http://www.w3.org/2001/XMLSchema#string
> "></customerId>
>   </rdf:Description>
>
> Rama does not define a Name as he XML element is empty. In addition
> you should not define a rdf:datatype for natural language labels.
> Adding xsd:string as datatype is intended to be used for
> non-natural-language string values (e.g. an ISBN number, product
> codes, alpha-numerical ids ...)
>
> The missing label will also prevent Stanbol from linking Rama for the
> provided parsed. Note also that also "city" and "customerId" are
> empty. So please check your data.
>
>
> regarding:
>
> > When  I type a sentence like " Rama was born on 23/07/2000 and lived in
> Delhi" ,
> I expect to see following  :
> > Rama will be recognized as a Person
>
> If #Rama does have a Name value of "Rama" and you configure the "Label
> Field" of the EntityLinking engine to
> "http://www.owl-ontologies.com/InsuranceOntology.owl#Name"; it will be
> recognized and the Entity will be linked in the Enhancement results.
>
> > 23/07/2000  will be recognized  as Person:dob.   ( Date of Birth of Rama
> )
>
> Suggesting Entities based on a date mentioned in the text is not
> supported by any EnhancementEngine managed by the Stanbol community.
>
> > Delhi will be recognized as Person:city  ( City of Rama)
>
> Rama will not get Linked, just because "Delhi" is present in the text.
> Typically users would create (or better reuse an existing) Entity for
> "Delhi" and change the data model (ontology) to not refer the city as
> a String, but as a reference to the Entity.
>
> The following example refines #Rama to refer to "New Delhi" as defined
> by freebase.com
>
>   <rdf:Description rdf:about="#Rama">
>    [..]
>      <city rdf:resource="http://rdf.freebase.com/ns/m.0dlv0"; />
>    [..]
>   </rdf:Description>
>
> As soon as cities are defined as Entities Stanbol can extract them
> from parsed texts. Your user interface might than use those
> information to search for Persons that are located in the extracted
> cities.
>
>
> Regarding the Screenshots:
>
> The mailing list does not allow to send attachments. Because of that
> the pictures have not made it through.
>
> best
> Rupert
>
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com****
>
>  ****
>
>  ****
>
> "This e-mail and any attachments transmitted with it are for the sole use
> of the intended recipient(s) and may contain confidential , proprietary or
> privileged information. If you are not the intended recipient, please
> contact the sender by reply e-mail and destroy all copies of the original
> message. Any unauthorized review, use, disclosure, dissemination,
> forwarding, printing or copying of this e-mail or any action taken in
> reliance on this e-mail is strictly prohibited and may be unlawful."****
>
> *Please do not print this email unless it is absolutely necessary. *****
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. ****
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email. ****
>
> www.wipro.com ****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> "This e-mail and any attachments transmitted with it are for the sole use
> of the intended recipient(s) and may contain confidential , proprietary or
> privileged information. If you are not the intended recipient, please
> contact the sender by reply e-mail and destroy all copies of the original
> message. Any unauthorized review, use, disclosure, dissemination,
> forwarding, printing or copying of this e-mail or any action taken in
> reliance on this e-mail is strictly prohibited and may be unlawful."****
>
> * Please do not print this email unless it is absolutely necessary. *****
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
>

-- 

"This e-mail and any attachments transmitted with it are for the sole use 
of the intended recipient(s) and may contain confidential , proprietary or 
privileged information. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message. Any unauthorized review, use, disclosure, dissemination, 
forwarding, printing or copying of this e-mail or any action taken in 
reliance on this e-mail is strictly prohibited and may be unlawful."

Reply via email to