[PyWrapper-devel] MOBY registries in PyWrapper

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

Hi Milko,

Ok. I have implemented some sort of multiple biomoby registry  
awareness in pywrapper.

Now in the MOBY tab there are two new fields in the General Settings:

"BioMOBY registry end point" and "BioMOBY registry Namespace".

This let you choose the registry you want to use. This information is  
saved as a general setting for this datasource. But preparing the  
work for the future now when you register a service the information  
of the end point and the namespace is stored in the service on the  
config files, thats allowing the same service to be register in  
multiple biomoby registries.

When you click on register a service the configtool uses the registry  
specify at this moment on the general settings, but when you click on  
Deregister it uses the registry that was used for registration.

By default I have left configured the CENTRAL MOBY REGISTRY in  
Canada. Milko, if you think more people are going to use the IRRI one  
I can change it, give me the end point and ns and I change it on the  
default config file so that new installations will appear with this.

There are some limitations still that I hope will not prevent us from  
delopying right now:

-Althought the config tool stores the info on the registry that was  
used for registering a service, the interface will still not offer  
you the possibility to register the same service in multiple  
registries. If the config tool detects that a certain service has  
been already registered in a registry is not offered as a potential  
service. In the config files is still possible to configure the same  
service in multiple registries, altought you would have to manually  
register them using Dashboard or something like this...

-The BMTTS file gives pywrapper a list of service templates, but it  
does not tell you for what registry this templates are designed.  
Different registries have different data types. So a service template  
for the IRRI server does not necessarily have to work with the  
Central one in Canada... Therefore is needed that the BMTTS stores  
information about to which registry a certain template was designed.  
Then the config tool should read this info and react according to  
this...

I have only tried it with the central moby registry in Canada, but I  
suppose it should work with others. I havent tried because I dont  
have the url of the IRRI registry and the getCoordinatesOfTaxon  
service template will probably not work with the data types there...  
Could you try Milko with yours?


It is commited now.

Javi.