<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Got it. The network start/end dates don't change often but on occasion they do. I think the most common case is when a temporary network code is extended to match an extended experiment time window. The only other useful identifier that I can think of is the network description contained in the <Description> tags, although that is subject to change as well but also doesn't change often. Perhaps by checking the description you can figure out when it's the same network versus something new more often than not.</div><div><br></div><div>Chad</div><br><div><div>On Jun 14, 2011, at 5:04 PM, John D. West wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">That was what I assumed from the output of the web service. The question is: can a start date or end date EVER change? If an incorrect date is entered and then later corrected, I end up with overlapping networks because network code + start date + end date combine to form the unique identifier.<div>
<br clear="all"> -- John<br>
<br><br><div class="gmail_quote">On Tue, Jun 14, 2011 at 4:58 PM, Chad Trabant <span dir="ltr"><<a href="mailto:chad@iris.washington.edu">chad@iris.washington.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hello.<br>
<br>
In general, networks, like stations and channels, have the notion of a start time and an end time. For permanent networks there are normally not breaks in the continuity. For temporary networks there are often blocks of years allocated for specific experiments, for example XY 2005-2006, XY 2007-2009 and XY 2010-2010. We would not consider those temporary networks to be modifications of an existing network, but instead to be logically different networks. Essentially the network code combined with the start and end time uniquely identifies a "network", when the dates change and the network code is recycled it should be considered a new network. Not sure I understood your question, did that help at all?<br>
<br>
Chad<br>
<div><div></div><div class="h5"><br>
On Jun 14, 2011, at 2:00 PM, John D. West wrote:<br>
<br>
> Hello.<br>
><br>
> I'm using the station webservice in EMERALD to maintain a local cache of network, station, and component metadata. In the Network level, reuse of network codes makes it difficult to differentiate between new and modified networks, e.g., if a network EndDate changes, my system registers it as a new usage of the network code instead of modification of an existing network.<br>
><br>
> Is there some unique identifier for each network which can be included in the web service?<br>
><br>
> Thanks!<br>
><br>
> -- John<br>
</div></div>> _______________________________________________<br>
> webservices mailing list<br>
> <a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
> <a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
<br>
</blockquote></div><br></div>
</blockquote></div><br></body></html>