There's several of layers of configuration and customization, including policy files and mapper subclasses. At some level some of these things must be hard coded, and the user has to match the customized bits with the repository (the mapper's job is to know how to find the the data in a specifically formatted repository).
nate
________________________________________
From: Gates, John H
Sent: Friday, January 22, 2016 9:39 AM
To: Lim, Kian-Tat; Becla, Jacek
Cc: Pease, Nathan; qserv-l
Subject: Re: [QSERV-L] webserv and butler issue
Is there a way to make it so that this doesn't need to be hard coded?
For Bremerton, we needed to access SDSS data, and it wasn't until after
talking to Jim that we had all the details needed to access the images.
-John
On 01/22/16 09:14, Kian-Tat Lim wrote:
> Jacek,
>
>> Yes, it is hardcoded in imgserv, but somehow it used
>> to work at Bremerton...
> It worked because you were accessing an SDSS repository.
>
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
|