netDCRequest

Mainly useful for accessing data that is not available via Fissures/DHI, such as restricted PASSCAL datasets or data from datacenters that have a netdc system but not DHI seismogram servers. Of course the network information must be available to SOD. As this subsetter always returns true, processing will continue past this point. In most cases, the whole reason to generate netdc requests is that it is the only way to get the data, and so there is not much point in proceeding down the waveform arm. You will generally want to wrap the netDCRequest in a requestNOT so that the return value is false. This will allow SOD to proceed to the next piece of work and avoid the wasted time in going to the server to get data.

Example 

<netDCRequest>
  <name>Jenny Seismologist</name>
  <inst>Univ. of Example</inst>
  <email>joe@seis.example.edu</email>
</netDCRequest>

This consists of

<netDCRequest>

<workingDir>Any text</workingDir> optional
<location>Any text</location> optional
interleave
<label>Any text</label> optional
<name>Any text</name>
<inst>Any text</inst>
<mail>Any text</mail> optional
<email>Any text</email>
<phone>Any text</phone> optional
<fax>Any text</fax> optional
group optional
<media>Any text</media>
<altmedia>Any text</altmedia> optional
<format_waveform>Any text</format_waveform> optional
<format_response>Any text</format_response> optional
<merge_data>Any text</merge_data> optional
<disposition>Any text</disposition> optional
</netDCRequest>

Places this can be found

In request there is a choice between all of the following