Leaking Private GOV Emails (NAWQA) #FuckSysteme./

#FuckSysteme./
.
..
...
#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#
#+#                  [+] Privat GOV Emails (NAWQA) By: ~{  J!h4d-X  }~              #+#
#+#                  [+] Contact: Jih4d-X@FBI.al                                    #+#
#+#                  [+] Greetz: { X-muslim ~ Root Max ~ KiNG H4ck3r ~ Rajaoui PS } #+#
#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#

___________________________________________________________________________________________
___________________________________________________________________________________________
Sandy K Williamson   06/17/2008 11:14 AM

To: Nathaniel L Booth/WRD/USGS/DOI, Richard W Bell/WRD/USGS/DOI,
      jlthomps@usgs.gov, kaskach@usgs.gov, Daniel E Kester/WRD/USGS/DOI@USGS
cc: Jonathon C Scott/WRD/USGS/DOI@USGS, Richard J Wagner/WRD/USGS/DOI
Subject: Changes to release of "recent" data to public - NAWQA and NWIS

How hard would it be to implement this functionality for the dwh
release to the public? Rick Wagner suggested it and he will be asking
Ken and Jon how hard it would be to modify the NWIS 'pusher' program
run by jobtimer to have similar results?

the release to public flag would be a set based on samples that have
been uploaded to NWIS at least NN number of days [default say 42 days
or 6 weeks] before release to public.  that way data of nn day 'age'
would automatically be release to public and every data collector
would have nn days, say 6 weeks to review each sample before it was
public.  If we could do this, it would make a lot of people happy and
more comfortable.

Nate and Jessica, please let me know what level of effort in
approximate person days [apd] for this or something like it.

Sandy


========================================================================================================
----- Forwarded by Sandy K Williamson/WRD/USGS/DOI on 05/20/2008 06:00 PM -----
Donna N Myers  4/16/2008 11:44 AM
To: Sandy K Williamson/WRD/USGS/DOI@USGS
cc: GS-W NAWQA nlt, GS-W NAWQA nst, GS-W NAWQA ntt@USGS, GS-W_NAWQA_Data_Synthesis@usgs.gov
Subject: Re: Changes to release of "recent" data to public - NAWQA and NWIS

Hi Sandy, Maybe we need to schedule a call about this topic before you
hit the go button on an all hands email. I'm getting some email chat
and would like to know more about the topic before your deadline of
this Friday.


=======================================================================================================
Sandy K Williamson   4/15/2008 03:39 PM
To: GS-W NAWQA nlt, GS-W NAWQA ntt@USGS, GS-W NAWQA nst
cc: GS-W_NAWQA_Data_Synthesis@usgs.gov
Subject: Changes to release of "recent" data to public - NAWQA and NWIS

To: NLT, NTT, NST, and after 1 week of comment period  to SU chiefs.

Now that it's possible for WSC's to upload data stored in NWIS/QWDATA
to NWISWeb on a daily basis (see links below to Tim Miller's 6/26/07
memo and Mark Hamil's 3/4/08 memo), the DataSyn team has been
discussing options for serving recent data to the public NAWQA Data
Warehouse (DWH) and trying to avoid the undesirable possibility that
at some point the DWH might serve data that are different from data
served by NWISWeb.  This follows years of adjustments to make our data
release policy match NWIS's.

This data-disconnect could occur if (1) WSC's modify their QWDATA
upload frequency from the default value (daily) to something much less
frequent;  or, (2) as rumor has it, some WSC's that oppose timely
QWDATA uploads to NWISWeb, might decide to forego installation of the
software that performs the uploads.  In these cases, because the
~weekly DWH reload process retrieves data directly from WSC host
computers, the DWH might then be serving recent data to the public
that haven't been uploaded yet to NWISWeb.  (The NAWQA data warehouse
data-retrieval mechanism has been in use for several years and is
much different than the one developed recently by NWISWeb.)

We think that some study units might not have considered the
possibility that their recent data could be served to the public via
the DWH and we want to take appropriate measures.  A fuller
description of the issue and DataSyn's proposed course-of-action is
described below.  We would appreciate your comments and suggestions
before we forge ahead.


Description of Issue and DataSyn's planned actions

-It is desirable for the NAWQA DWH to release water-quality data to
the public on a continuous basis, since NWISWeb now does
so.  (Currently, we keep a whole water-year's worth of samples out of
the public DWH, until we decide the data reports are
"done".  Normally, we would release WY 2007's sample to the public
sometime in MAY or JUNE, 2008.  Until then, the most recent
water-quality data in the public DWH is through September, 2006
(WY06). )

-We will add a DQI field to public-query tables containing result
values. This ensures users get relevant information about the status
of data review and although it's not yet "well populated" -- it's
still the best tool we have.  (Doing this will be a motivation for
WSC/NAWQA staff to populate DQI correctly!)

-NAWQA data teams (topical teams, status&trends, study units, etc)
should be duly informed about their increased responsibility to code
DQI (at the result level), and/or ASTAT (at the sample level) for
appropriate public consumption.  Some of the issues to educate the
NAWQA data teams about include:

   -Immediate release of water-quality data to the public means they
    should code ASTAT and/or DQI immediately after sample login or receipt
    of their data from the lab(s).  They need to do this for NWISWeb,
    regardless of how the DWH releases their water-quality data.  OWQ
    Technical Memo 2007.04 (link below) explained how to code for
    restricting data from the public.

   -The DWH no longer keeps a list of "approved parameters" for
    release to the public.  (We did at one time, but we discontinued that
    practice a couple years ago.) However, NWIS maintains a "public flag"
    in its parameters table, with 2,744 (out of 18,755 total) pcodes
    flagged as "NOT public".

-Datasets retrieved from the DWH would use the same disclaimer as
NWISWeb:

USGS endeavors to ensure the accuracy of all water-quality data
provided to the public. As part of our efforts to improve the
timeliness and relevance of our data-collection efforts, provisional
data are provided which may not have been reviewed. The majority of
results are not changed during the review process, but errors do
occur. The "data-quality indicator" (DQI) is provided to guide data
users.  Results are initially coded with a DQI of "S" (presumed
satisfactory).  After review by a project hydrologist, the DQI is
usually changed to "R" (reviewed and accepted).  Laboratory results
are initially reviewed at the laboratory and subsequently by the
hydrologist.  Sometimes, comprehensive reviews of quality-assurance
data cause revisions to previously reviewed data, therefore an "R" DQI
coding does not guarantee that results will never be updated.

To view additional data-quality attributes, output the results using
these options:  one result per row, expanded attributes.


Thanks for your comments/suggestions.

DataSyn

-----

Tim Miller's  6/26/07 OWQ Technical Memo 2007.04 memo, Controlling Flow of Water-Quality Data to NWISWeb :
  http://nm.water.usgs.gov/nawqa_natsyn/docs/OWQ_07.04_dataflow.doc

Mark Hamil's 3/4/08 software release memo:
  http://nm.water.usgs.gov/nawqa_natsyn/docs/NWIS_release_of_QW_Incremental_Software.doc

_

Sandy (Alex K.) Williamson  akwill@usgs.gov  PH (253) 552-1683 fax-1581 c:253-376-8273 h:253-531-1481
NAWQA Nat'l Data Base Team Leader, US Geological Survey,   water.usgs.gov/nawqa/data & wa.water.usgs.gov
934 Broadway, Suite 300, Tacoma, WA 98402
__________________________________________________________________________________