[Go-essp-tech] replicas and search

[Luca Cinquini]

Hi Don,
	from Bryan's use case, it seemed to me that he already knew which  
gateway to consult...
But I do agree that we will not be able to perform file-searches  
across the federation based on the RDF metadata, it has been long  
known that we don't want to store files inside the triple stores  
because of performance issues. Obviously, if this use case is really  
important, each gateway could expose a web service to perform this  
kind of queries in a distributed fashion.
thanks, Luca


On Dec 2, 2009, at 9:47 AM, Don Middleton wrote:

> A follow-on to the call, as I had to leave a bit early. We were  
> discussing being able to use the tracking id for various files. If  
> the tracking id is not in the federated metadata, how does one know  
> which gateway to consult for information?
>
> don
>
>
> On Dec 1, 2009, at 2:30 PM, Luca Cinquini wrote:
>
>> Hi,
>> 	as I mentioned today at the telecon, I think the RDF query  
>> services should be able to handle the concept of dataset replicas  
>> quite nicely. The main concepts are that the RDF records generated  
>> from replicas must have different RDF identifiers, so they can be  
>> exchanged independently among gateways, and must reference their  
>> original RDF record.
>>
>> If you are interested, I've documented some of the details here:
>>
>> https://wiki.ucar.edu/display/esgcet/Metadata+Search+and+Replicas
>>
>> I'm also including a snapshot of an ESG Gateway that shows multiple  
>> replicas returned as part of a DRS search (note that how the  
>> replicas are presented in the result page can be easily changed -  
>> the picture is just to show that the query can handle replicas).
>>
>> thanks, Luca
>>
>> <DRS with Replicas.tiff>
>> _______________________________________________
>> GO-ESSP-TECH mailing list
>> GO-ESSP-TECH at ucar.edu
>> http://mailman.ucar.edu/mailman/listinfo/go-essp-tech
>