Thanks Rafa, Iam currently using only curl commands to interact with Stanbol and have not written any rest service.
Where is the additional metadata for a content stored? Is there a way we can use a curl command to retrieve / validate the additional metadata stored. Thanks and Rgds, Arthi -----Original Message----- From: Rafa Haro [mailto:rh...@zaizi.com] Sent: Tuesday, October 01, 2013 7:30 PM To: dev@stanbol.apache.org Subject: Re: Adding content specific metadata Hi Arthi, If you go through the ContentHub web interface at your Stanbol installation, you will be only able to see your enhancements (Enhancement Metadata), not your Additional Metadata. In fact, I'm not sure if the Additional Metadata is being stored in any way in the ContentHub. Have you tried retrieving it using GET REST services?? Cheers, Rafa El 01/10/13 15:33, arthi.ven...@wipro.com escribió: > Hi Rafa, > Yes Iam trying to load additional metadata with the content. > After executing the curl command I go to the Stanbol content hub. In this > Iam able to see the item added as well as the chain created enhancements. > However I do not see the content specific metadata added by me in the set of > enhancements. > > Thanks and Rgds, > Arthi > > > > > -----Original Message----- > From: Rafa Haro [mailto:rh...@zaizi.com] > Sent: Tuesday, October 01, 2013 6:56 PM > To: dev@stanbol.apache.org > Subject: Re: Adding content specific metadata > > Hi Arthi, > > Reading again your email I have realized that maybe there is a kind of > misunderstanding here. You are trying to upload Additional Metadata along > with the content to the ContentHub. Additional Metadata, within the > ContentItem structure [1], is not the same that Enhancement Metadata. When > you say that you are not able to see it, what do you actually mean? Where > can't you see it?. > > Regards > > El 01/10/13 14:48, arthi.ven...@wipro.com escribió: >> Thanks Rafa. >> >> I updated the RDF metadata to include this. However still I do not see >> the custom metadata in the list of enhancements . >> Is my understanding correct or Do I need to change something else.? >> >> >> <rdf:RDF >> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; >> xmlns:fise="http://fise.iks-project.eu/ontology/"; >> > >> <rdf:Description > >> <title>Test Metadata</title> >> <owner>Arthi</owner> >> <subjectOfArticle>General posts</subjectOfArticle> >> <fise:extracted-from> urn:my-content-item4</fise:extracted-from> >> <rdf:type >> rdf:resource="http://fise.iks-project.eu/ontology/Enhancement"/> >> </rdf:Description> >> >> Thanking you and Rgds, >> Arthi >> >> -----Original Message----- >> From: Rafa Haro [mailto:rh...@zaizi.com] >> Sent: Tuesday, October 01, 2013 5:40 PM >> To: dev@stanbol.apache.org >> Subject: Re: Adding content specific metadata >> >> Hi Arthi, >> >> Try adding fise:extracted-from property. According to my experience, RDF >> resources without extracted-from property are filtered by the ContentHub. >> >> Hope that helps. >> >> Cheers, >> Rafa >> >> El 01/10/13 13:58, arthi.ven...@wipro.com escribió: >>> Hi, >>> In addition to the content file I want to upload some per document >>> metatdata - ( Document subject, Document title, etc ). >>> >>> Iam unable to see the additional metadata. The other enhancements / content >>> ingestion goes through fine. >>> >>> 1. Is the curl command below correct >>> >>> 2. Is the RDFmetadata format below correct >>> >>> 3. I assume if the enhancement works I would be able to see the >>> additional metadata also in the enhancements. Is this correct? >>> >>> I have used the below curl command. >>> curl -i -X POST -H "Accept:multipart/form-data" -H >>> "Content-Type:application/msword" --data-binary @TextToEnhance.docx >>> -H >>> "Content-Disposition: form-data; name=urn:my-content-item4" -d >>> @SampleRDFMetadata.txt >>> "http://localhost:8080/contenthub/contenthub/store?uri=urn:my-conten >>> t >>> - >>> item4" -u admin:admin >>> >>> The SampleRDFMetadata has this content : >>> <rdf:RDF >>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; >>> > >>> <rdf:Description > >>> <title>Test Metadata</title> >>> <owner>Arthi</owner> >>> <subjectOfArticle>General posts</subjectOfArticle> >>> <rdf:type >>> rdf:resource="http://fise.iks-project.eu/ontology/Enhancement"/> >>> </rdf:Description> >>> >>> >>> >>> Thanking you and Regards, >>> Arthi >>> >>> >>> 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 message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. Zaizi Ltd is registered in England and Wales with the registration number 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road, London W6 7AN. 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
