1. Astrogrid Registry Schema Use
Kevin Benson
28/02/2019

2. Introduction Components Use Current use of the schema elements.
Registry road of Components
Harvesting
What still needs resolving
Introducing the main attraction CEA
28/02/2019

3. Community Quick Background on community
Community now will lookup other communities via the Registry.
Community will lookup various Policy and Authentication services via Registry.
Not used as part of the registry, but accounts and groups are now in a ivo identifier form, for the community to look up in it’s database ex: ivo://org.astrogrid.mssl/kevin is my identifier at MSSL.
Services Registered
PolicyService: checkMembership and checkPermission
PolicyManager: setting up accounts, groups, permissions.
28/02/2019

4. Security Quick Background on Security
Security services are registered in the Registry, where Security uses Registry via the Community.
Services Registered
SecurityService: checkToken, checkPassword, splitToken
SecurityManager: setPassword
28/02/2019

5. VOSpace (Myspace) Quick background on Myspace
Myspace entries are in the registry.
DataCenter and other components use the registry to find the endpoint for Myspace, for storing data.
Only the Myspace services are registered, no directory structure or files are registered in any way.
A Community account may have an associated ivo identifier for their VOSpace registry entry.
Scenario: Means a component can look for my myspace location with the identifier ivo://org.astrogrid.mssl/kevin, which in turn will call the community services found in the Registry and get an ident of ivo://org.astrogrid.mssl/myspace which can then be looked up in the registry for the endpoint to this service
28/02/2019

6. Current elements used Very Little Identifiers and AccessURL
AccessURL since it was suggested that a Web Service needs to specify a WSDL. Using WSDL4J it finds an endpoint/url location from a WSDL. If it is not a WSDL then return the contents of what is in the AccessURL element.
Workflow uses a little on Title and other elements.
28/02/2019

7. Registry Road
Data Query - This will be the bigger one allowing data query components to get tables and columns for forming ADQL queries.
Myspace – will be using registry to communicate with other Myspace’s and their various servers.
28/02/2019

8. Harvesting
Astrogrid currently can now harvest WebBrowser and WebService.
Astrogrid can harvest other Registries plus will attempt to harvest Service entries.
Web Service operations:
Harvest: harvest metadata from all known entries that this registry manages. Using a “from” date of when the last harvest occurred. (“from” only is for Registry resource entries.)
harvestFrom: harvest metadata from all known entries that this registry manages with an attempt of a “from” date. (“from” only is for Registry resource entries)
harvestResource: harvest metadata from Resource entries submitted to this method. Also will add/update these submitted resources into the registry. (also a way to register new resources)
harvestAll: harvest metadata from all known entries that this registry manages. No dates used, much like a replicate. Rarely used or tested.
28/02/2019

9. What still needs resolving
These areas will be more addressed in later presentations.
Data – Still need data from the data centres to be registered in the registry. Strongly advise we need some more documentation on how to fill out the registry schema for the data centres.
Standard Query interface and Harvesting interface.
Harvesting is not automated as of yet, must be ran manually.
Small changes on harvesting via web services.
ResourceKey? What is a good way of using the resource key. Currently several of Astrogrid entries are very much like class names. Ex: org.astrogrid.community.PolicyManager
AuthorityID? Currently our AuthorityID is very much like a community/region representation is this okay. Ex: org.astrogrid.mssl, org.astrogrid.cam, org.astrogrid.le
AccessURL? Is this the right approach reading the wsdl for the location.
CEA is brand new expect some changes.
28/02/2019

10. Conclusion/End
CEA will be added later
28/02/2019