Re: [PyWrapper-devel] A problem...

[Javier de la T. <ja...@gm...>]

Hi Markus,

This weekend I will add the possibility to choose the moby registry =20
and with this I think we are done!

Monday release!

Javi.

On 17/11/2006, at 13:51, Markus D=F6ring wrote:

> so I am gone over the weekend.
> if there are no more bugs detected by monday we do our first release?
> what do you think? javi, anythin from your side left to do? some =20
> code cosmetics?
> markus
>
>
> On 11/17/06, Skofic A. Milko (IPGRI) <M.S...@cg...> wrote:
> Oh sh... I am buggy!
> Sorry. Will check the MOBy files, probably there is an incorrect =20
> concept ID.
>
> Ciao!
> ink
> Milko
>
> On Nov 17, 2006, at 13:36 , Markus D=F6ring wrote:
>
>> Milko,
>> thats because you got the ABCD coordinate concepts wrong.
>> Theres a double DataSets/DataSets/ part in it. the wrapper doesnt =20
>> know it and evaluates the comparison (isNull) to False. butthe Not =20=

>> makes it True again!
>>
>> still no buggy code!
>> markus
>>
>>
>> On 11/17/06, Skofic A. Milko (IPGRI) < M.S...@cg...> wrote:
>> Put down those champagne glasses... :-) just joking, however there =20=

>> is a problem with the not null stuff. I am sending this query:
>>
>> <?xml version=3D'1.0' encoding=3D'UTF-8'?>
>> <request>
>> 	<header>
>> 		 <source =
accesspoint=3D"http://tapir.grinfo.net:8080/pywrapper/=20
>> pywrapper?dsa=3DEURISCO " sendtime=3D"2006-11-16T23:44:59.14"/>
>> 	</header>
>> 	<search count=3D'true' start=3D'0' limit=3D'50'>
>> 		 <externalOutputModel =
location=3D"http://eurisco.ecpgr.org/models/=20
>> moby/TestService.xml "/>
>>         <filter>
>>          	<and>
>> 				 <like>
>> 					<concept id=3D" =
http://www.tdwg.org/schemas/abcd/2.06/DataSets/=20
>> DataSet/Units/Unit/Identifications/Identification/Result/=20
>> TaxonIdentified/ScientificName/FullScientificNameString">
>>  					</concept>
>> 					<literal value=3D"b*" />
>> 				</like>
>> 				 <not>
>> 					<isNull>
>>  						<concept id=3D" =
http://www.tdwg.org/schemas/abcd/2.06/=20
>> DataSets/DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/=20
>> SiteCoordinates/CoordinatesLatLong/LatitudeDecimal">
>>  						</concept>
>> 					 </isNull>
>> 				</not>
>> 				 <not>
>> 					<isNull>
>>  						<concept id=3D" =
http://www.tdwg.org/schemas/abcd/2.06/=20
>> DataSets/DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/=20
>> SiteCoordinates/CoordinatesLatLong/LongitudeDecimal">
>>  						</concept>
>> 					 </isNull>
>> 				</not>
>>             </and>
>>         </filter>
>> 	 </search>
>> </request>
>>
>> This query is the query that TAPIR would use to get the data for =20
>> the getCoordinatesOfTaxon MOBY service.
>> When I try it with the training and EURISCO_TEST data sources it =20
>> works, when I send it to the EURISCO data source it returns a =20
>> bunch of records without latitude and longitude.
>>
>> When you look at the SQLs it produces you see nowhere in the WHERE =20=

>> clauses the test for the NULL latitudes and longitudes.
>>
>> If you want to test the corresponding MOBY services, for datasources:
>>
>> EURISCO		-> eurisco.ecpgr.org		-> =
TestServiceABCD
>> EURISCO_TEST	-> test.eurisco.ecpgr.org	-> TestServiceABCD
>> training			-> test.ipgri.ecpgr.org		-> =
getCoordinatesOfTaxon
>>
>> I am sending you the whole package of the MOBY service files in =20
>> case you need to check things, anyways you know the passwords of  =20
>> http://tapir.grinfo.net:8080/pywrapper/
>>
>>
>>
>>
>>
>>
>> I will get back to you during the week end, this afternoon I am =20
>> not here.
>>
>> Bye!
>>
>> Milko
>>
>>
>>
>
>