|
Hi Alvaro, indeed it is boring to have duplications :) The sync method is the right one to use. But as you have seen it requires a KIMDoc as a parameter. The envisaged workflow is like this: a new document comes to the system you process it and store it then if you like to re-process it, you find it in the repository, reannotate something or change some doc-level features and then you sync it. If this is your scenario - then this is how it is supposed to work. On the other hand, if you are passing the same corpus N times to the server you would get N versions of each document in it. Tell us your scenario and we will try to come up with a suggestion. all the best to you borislav Alvaro Hernandez wrote:
|
_______________________________________________ NOTE: Please REPLY TO ALL to ensure that your reply reaches all members of this mailing list. KIM-discussion mailing list [email protected] http://ontotext.com/mailman/listinfo/kim-discussion_ontotext.com
