BEE-spoke-data/govdocs1-by-extension huggingface dataset:
Federal Knowledge Management Initiative Backgrounder
====================================================

The **Federal Knowledge Management Working Group**, over 700 Federal
employees, contractors, academicians and interested members of the
public, have mounted a campaign to enhance collaboration, knowledge and
learning in the Federal Government by implementing formal knowledge
management.

**Knowledge Management (KM)**, a discipline that uses management tools
along with culture change, has been effective in the private sector.
Some agencies have succeeded at KM, including **NASA** and the **US
Army**, but there is **no formal Federal program**. There is no policy,
standards or direction. There is no central clearinghouse of lessons
learned or "what works." Agencies and Departments must spend scarce
consulting dollars to find their own way, "reinventing the wheel" in a
wasteful duplication of effort. To fill this leadership void, the
Federal KM Working Group presents an Action Plan for formal KM
governance, with these goals:

1.  **Establish a Federal Knowledge Management Center** to serve as a
    centralized resource for agencies in carrying out their own
    knowledge management efforts. The center will provide consulting and
    serve as a clearinghouse of Federal KM resources, such as software,
    expertise, and lessons learned.

2.  **Establish a Federal CKO Position.** This person, the face of
    Federal KM, will coordinate with Federal departments to explain the
    benefits of sharing and collaborating across agencies.

3.  **KM Governance.** Enact Government-wide Policies, Standards and
    Practices that specify the general direction and intent of Federal
    knowledge sharing efforts.

4.  **Awareness Campaign and Web Presence.** To communicate the serious
    need for KM and distribute content "from those who know to those who
    need to know."

5.  **Build a Knowledge Sharing Culture in the Federal Government.**
    Change the Federal mindset from "need to know" to "need to share."

6.  **Train Federal Workers in KM Skills.** By learning KM competencies,
    they will also acquire a deeper understanding and appreciation of
    the value of knowledge sharing.

7.  **Meet the Challenges of the Retirement "Age Wave."** KM includes
    "knowledge retention," an effort to reduce "brain drain" due to
    thousands of retiring baby boomers. The other side of the coin,
    today, is the Federal challenge in recruiting Generation Y
    employees, who have been raised on Web 2.0 and social computing
    tools.

The Federal KM Working Group (also known as KM.gov) utilizes a wiki
maintained by NASA/JPL containing documents related to the Federal KM
Initiative at this link: <http://wiki.nasa.gov/cm/wiki/?id=3907>

For more information, please contact:

Neil Olonoff\
Committee Chair

[olonoff\@gmail.com](mailto:Olonoff@gmail.com)

Cell: 703.283.4157

Office: 703.614.5058

4 Feb 09, v. 1.0
C3PR Training Materials

WFU per discussions within the C3PR has created the draft training
materials package to be reviewed by other developers, adopters and
elaborators. This package is composed of 4 parts.

1)  A review of the caBIG C3PR tools page

2)  A Directors overview presentation on C3PR (target audience: Cancer
    Center Directors)

3)  A user overview presentation: (target audience, study coordinators,
    registrars and patient coordinators)

4)  An online training module (utilizing materials from the user
    overview presentation in a to be determined online media format.

Delivery will be in two stages:

1)  Draft. The presentations and reviews will be primarily in outline
    form, or labeled slides, to be filled in with final screen shots and
    details once the final iteration of C3PR is complete. The online
    training module which will be composed of a recorded online
    presentation of the user overview (replacing screenshots with video
    of the application in use) will not be part of the draft.

2)  Final. All screenshots are supplied, specific workflows filled in.
    The online training module will be created from the approved user
    overview.
**Fire Incident Records Management**

**Return comments to: larson.louise\@gmail.com**

**Name: Date:**

**Phone: E-mail:**

**Agency: Unit: Region:**

**IMT ID/Position on IMT:**

**Tools to assist Incident Management Teams implement fire incident
records management are available on the NIFC website (
<http://www.nifc.gov/policies/records/index.html> ). Your feedback,
suggestions for improvement, or comments about how your team uses the
IMT tools to implement the policy is welcome at any time during the
season. Please comment on any of the tools shown below or otherwise to
help make the process more efficient.**

**Retention Guidance:**

**IMT Instructions:**

**Graphic Examples for File Organization:**

**IMT Filing Labels:**

**Final Documentation Index/Box Indexes:**

**Other:**
Project UML Models and caDSR

As a Project Manager, what do you do next?

Date: August 27, 2008

Version 0.1\
Table of Contents

[1. Introduction 1](#introduction)

[2. Where to find information 1](#where-to-find-information)

[2.2. XXX 1](#xxx)

Introduction
============

This document does not provide specific instructions on how to lad your
UML model to caDSR. Rather it seeks to set general context of what
involving caDSR means to your project for scheduling purposes and points
you to the resources you'll need to accomplish the task.

Where to find information
=========================

#### Go to XXXX

#### Document of complete instructions: http://gforge.nci.nih.gov/docman/view.php/64/10674/submission\_form\_ModelName\_vX\_rvY.doc

XXX
---
Regional Advisory Council

Outreach to Health Professionals Committee

August 13, 2007 Meeting Minutes

Leading:

Sheila Snow-Croft

Attending:

> Martha Earl
>
> Frances Henderson
>
> Allison Howard
>
> Cathy Jordon
>
> Diana McDuffie

Rita Smith

> Feili Tu
>
> Toni Yancey

The meeting began with general introductions. Allison Howard, from the
University of South Florida, has replaced Ellen Sayed, who has moved to
Doha, Qatar, for a new position.

Sheila Snow-Croft provided a general RML Update:

-   New NN/LM SE/A classes include Grants and Proposal Writing,
    Measuring Your Impact: Using Evaluation for Library Advocacy, the
    online version of ¿No Comprende?: Spanish Health Information
    Resources for English Speaking Librarians, and the Patient Safety
    Resource Seminar.

-   Upcoming NN/LM SE/A classes and resources include Evidence Based
    Nursing, an online version of Nursing on the Net, Outreach for
    Hospital Librarians, Patient Informatics, Veteran's Health, and a
    Health Literacy Toolkit. A general discussion followed regarding
    in-person and distance education needs and expectations.

-   On 8/14 at 8:30 and 2:30 EST, the NN/LM SE/A will host a web
    conference, "It Takes a Village: Community outreach can be
    rewarding, challenging, and daunting," led by Toni Yancey.

-   Update on NN/LM SE/A funding available for Year 02 of the 2006-2011
    contract. Available funding includes one Library Improvement Award,
    two Express Welcome Awards, three Express Planning Awards, and the
    Katrina Relief/Delta Information Access Project Awards, which will
    be available until August 24th.

-   The RML has a new Community Outreach Coordinator: Mandy Bayer Meloy.
    She was a hospital librarian at Northeast Georgia Health System and
    an AHEC librarian at the Foothills AHEC in Gainesville, GA. Mandy
    earned both her MLIS and an MA in Comparative Literature at USC, and
    is very excited to be working with the RML.

-   Our Outreach Challenge was discussed. We issued one in February, 13
    each in months March and April, 23 in May/June, and 26 in July.
    Participants were encouraged to help spread the word and continue to
    send in reports so their outreach efforts can be documented.

The RAC Oversight Committee consists of Linda Gorman (Consumer Health
Outreach), Patricia Hammond (Technology), Jan Orick (Access), and Dan
Wilson (Disaster Preparedness Task Force), along with Diana McDuffee,
who is representing our OHP group. Diana gave a brief overview of the
first Oversight Committee meeting and discussed challenges for the year
ahead.

Emergency Preparedness is a topic of great importance, and NLM Resources
were discussed, along with general discussion regarding what is involved
and needed to meet possible disasters. We will be covering this in more
depth in future meetings, and all input and suggestions are welcomed as
we try to make sure we are all prepared for many different types of
emergencies.

JCAHO changes are particularly relevant to this group, and the web
resources for a white paper on Health Literacy and the National Patient
Safety goals were shared with the committee.
![](media/image1.png){width="6.5in" height="4.858131014873141in"}

![](media/image2.png){width="6.5in" height="4.858131014873141in"}

![](media/image3.png){width="6.5in" height="4.858131014873141in"}

![](media/image4.png){width="6.5in" height="4.858131014873141in"}

![](media/image5.png){width="6.5in" height="4.858131014873141in"}

![](media/image6.png){width="6.5in" height="4.858131014873141in"}
**caBIG^TM^ ICR Face to Face Meeting**

**September 17-18, 2007**

1.  **Attendees/participants** from Washington University School of
    medicine-

-   Hrishikesh Deshmukh

-   Sunita Koul

-   Rakesh Nagarajan

-   Mukesh Sharma

2.  **Presentations** by Washington University School of medicine
    attendees-

    -   Day 1 --September 17^th^ (1:30-2:30 PM): Rakesh Nagarajan
        presented a talk titled "caBench-to-Bedside (caB2B)" under the
        caBIG Tools for Translational Research.

    -   Day 1 --September 17^th^ (4:40-5:00 PM)-Mukesh Sharma presented
        report on "Adoption of caBIG^TM^ Tools" under reports from EY1
        adopters.

    -   Day 1 --September 17^th^ (6:00-8:30 PM)-Hrishikesh Deshmukh,
        Sunita Koul, Rakesh Nagarajan and Mukesh Sharma participated in
        the review of/discussion on caArray 2.0 wireframes.

    -   Day 2-September 18^th^ (9:00-10:00 AM)-Hrishikesh Deshmukh
        presented a talk titled "Workflows" under Community Member
        Presentations--Workflow needs.
Date: October 15, 2008

Topic: CTCAE v3.0 Help Desk Tickets SOC Nervous system disorders

Working Group \# 4: Psychiatric disorders; Nervous system disorders

From: Ann Setser

Issue: **Cerebral edema**

Not listed in CTCAE v3.0. Consider addition in CTCAE v4.0 

However, one might report the symptom and not the diagnosis. So if
someone has cerebral edema, how did it present?

Tough one, not well covered. unless it is related to lymphatic issues, I
would put it in neurology.

 

I handle these generally by the symptom, and not the DX, so if someone
has cerebral edema, how did it present? If it is just an imaging finding
without symptoms, perhaps grade it as cerebral edema.  But if
presentation is with symptoms, perhaps report the symptoms such as
somnolence, seizures, encephalopathy, etc) to determine the AE and then
use cerebral edema as the attribution.

 

 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

Hemorrhage/Bleeding - CNS Hemorrhage - Grade 3 misspelling
\'thombolysis\' should be changed to \'thrombolysis\'

CTEP Response: YES THIS IS A TYPO AND SHOULD BE THROMBOLYSIS

In the CTCAE version 3, \"Depressed level of consciousness\" was revised
to Somnolence / depressed level of consciousness;\" and Grade 1 was
deleted. When a very mild sleepiness with the grade less than 2 is
observed in a trial and the physician thinks it is caused by a study
drug, how we should record it and what grade we should put on it?

Suggestions for addition in CTCAE v4.0: Oncologic emergencies:

-   MedDRA: Hypertensive encephalopathy; SOC Nervous system disorders

-   MedDRA:Spinal cord compression SOC Nervous system disorders

-   MedDRA: Increased intracranial pressure SOC Nervous system disorders

-   MedDRA: Hemiparesis

-   MedDRA: Migraine

-   poor balance -- Not in MedDRA

    -   MedDRA LLT Balance difficulty; PT Balance disorder

-   smell hypersensitivity -- Not in MedDRA

    -   MedDRA options: LLT Smell alteration; Smell perversion; Strange
        smell sensation; all LLTs for PT Parosmia
"Tissue Banks & Pathology Tools" Workspace

Weekly Developer Call

Wednesday, Oct 8, 2008

8:00 AM to 9:00 AM (ET)

Dial-in Number: 1-888-790-1566

International Dial-in Number: 1-773-681-5890

Pass code: 75787

Breeze Session Details:
[[http://webmeeting.nih.gov/catissuecore]{.underline}](http://webmeeting.nih.gov/catissuecore)

Meeting Facilitator: LiMing Shen

AGENDA

1.  Suggestion for agenda (10min)

2.  RC1 (15 min)

    a.  Testing overview

    b.  Bug status

    c.  LSD testing coordination

3.  Tech review summary (10 min)

4.  Security Prototype (20 min)

5.  Open discussion (5 min)
**Statement of Work**

**Sewer Lift Pump Replacement**

**[Scope of Work]{.underline}**

Provide labor for the installation of Sewer Lift Pumps, and panel and
replacement of values at 615 S. 43^rd^ Avenue, Phoenix, AZ 85009 as
detailed below:

Furnish and install two (2) each Wilo-Emu 4" FA101-163 Submersible pump
with 4 HP, 1700 RPM, 460 volt, 3 phase motor. Design point is 100 gpm @
25" TDH **(or equal)**

Furnish and install one (1) each Duplex Pump Panel, all related
electrical power and controls are included as follows:

Duplex Pump Panel 2x5 HP 460Volt NEMA Enclosure

Phase los relay, 2 x lapse time meters, 4 Float Switch Signal, Run and
Alarm Pilot Lights, Seal Failure Relays, High Level Alarm, PLC Control,
MMS Disconnect, Hand Off Auto Switching

Notes:

1.  The vendor will complete the Sewer Lift Pump Replacement without
    taking the facility out of service

2.  The installation must meet NEC Code requirements.

All material and labor to come with a one year warranty except for the
Duplex Pump Panel components. The Duplex Pump Panel and Components to
come with a five (5) year warranty.

**Site Visits**

For bidding purposes it is recommended that you visit the site. Please
contact Ken Nelson (602) 388-7805 or Shawn Foley (602) 388-7806 for
appointment.
![](media/image1.jpeg){width="1.625in" height="0.4527777777777778in"}NIH caBIG \| CCTS Security Requirements Project
====================================================================================================================

Topic: Parking Lot Issues 
-------------------------

Date: August 18, 2008

The following issues have been identified as outside the scope of the
CCTS Security Requirements project, and should be considered in future
releases of the suite.

1.  **DSSF --** The Data Sharing and Security Framework (DSSF)
    initiative identifies a number of issues that will be elaborated and
    added to subsequent releases of CCTS. E.g.,

    a.  **"Click-through Terms" and Conditions**

    b.  **Bi-Lateral and Multi-Lateral Agreements**

2.  **Deployment Requirements --** It is our understanding that is the
    responsibility of each institution that chooses to install the CCTS
    to understand the regulations that govern the use of these tools
    (e.g., FDA regulations related to physical control of the data,
    documented procedures, training records, etc.).
+--------------------+------------------------------------------------+
| Computing Division |                                                |
+====================+================================================+
| To:                | Vicky White, Pier Oddone                       |
+--------------------+------------------------------------------------+
| From:              | Jack C. Schmidt x4060 04081N                   |
+--------------------+------------------------------------------------+
| CC:                | Amber Boehnlein, Ray Pasetes                   |
+--------------------+------------------------------------------------+
| Date:              | 7/16/2008                                      |
+--------------------+------------------------------------------------+
| Re:                | JLAB Remote Website at FNAL                    |
+--------------------+------------------------------------------------+
| Comments:          | The attached MOU outlines Fermilab hosting a   |
|                    | remote website for JLAB in the case of an      |
|                    | emergency. The remote website will provide     |
|                    | JLAB with a way to inform users of that        |
|                    | facility with information during an emergency  |
|                    | state at the lab(such as power loss during     |
|                    | hurricane season).                             |
|                    |                                                |
|                    | The MOU has been reviewed and approved by Gary |
|                    | Leonard of the Fermilab Legal Department and   |
|                    | by Roy Rubinstein of the Fermilab Directorate. |
|                    |                                                |
|                    | The initial goal was to have this MOU signed   |
|                    | and the website functioning before hurricane   |
|                    | season started in Virginia. Since we have      |
|                    | missed this date I have assumed the            |
|                    | responsibility of creating a                   |
|                    | "proof-of-concept" website for JLAB until the  |
|                    | MOU is officially signed by Fermilab and JLAB  |
|                    | officials.                                     |
|                    |                                                |
|                    | If there are any questions regarding the MOU   |
|                    | please contact I or Ray Pasetes, who directly  |
|                    | manages the central web servers.               |
|                    |                                                |
|                    |   Jack Schmidt        Ray Pasetes              |
|                    |   ------------------- ----------------         |
|                    |   schmidt\@fnal.gov   rayp\@fnal.gov           |
|                    |   x\. 4060            x\. 5250                 |
+--------------------+------------------------------------------------+

![](media/image1.emf)
"Tissue Banks & Pathology Tools" Workspace

Monthly Developer Call

Wednesday, Oct 1st, 2008

8:00 AM to 9:00 AM (ET)

Dial-in Number: 1-800-366-7242

International Dial-in Number: 1-858-826-6757

Pass code: 72451043

Breeze Session Details: [http://webmeeting.nih.gov/TBPT]{.underline}

Meeting Facilitator: LiMing Shen

AGENDA

1.  Open discussion, suggestion for agenda (10 min)

2.  Current status (20 min)

    a.  Available resource and organization

    b.  Ongoing tasks

    c.  Type of requests from community and resolution workflows

    d.  Workload

    e.  Gaps and issues

3.  Tools (KC Forum, Bugzilla and Subversion) (20 min)

    a.  Functions

    b.  Timelines

    c.  Relationship with Dev team(s)

4.  Other issues (10 min)
Wiki Searching Auto-complete Feature Instructions
=================================================

Setting up Auto-complete:

The auto-complete feature within search can be set up automatically (via
my preferences) or it can be used at the time you wish to search.

To set it up via preferences, after you've logged in click on the My
Preferences link (Figure 1).

In My Preferences, click the Misc tab (Figure 1).

Now check the box for Auto-triggered auto-completion (Figure 1).

Click the Save button to save your changes.

Figure1![](media/image1.png)

If you do not wish to set your preferences for the auto-complete feature
you may type the word in the Search box and click CTRL-spacebar to
activate auto-complete.

Using Auto-complete

Note: Since the new CTCAE SOC is the coding scheme for the 2^nd^
iteration, if you type in CTCAE SOC (does not have to be capitalized)
and then your term it will allow you to find the AE term within this
namespace.

Begin typing CTCAE SOC and then the AE term you wish to find (see below-
example: Hypohidrosis).

If your auto-complete is auto-triggered you should see a red swirling
circle, which signifies that the auto-complete is working to find your
term.

You will then see a drop down box with a list of terms (see Figure 2).

> Figure 2
>
> ![](media/image2.png)

Choose your term from the list. This will place that name in the Search
field (see Figure 3).

> Figure 3
>
> ![](media/image3.png)

If you click the Go button, you will be directed to the AE term page
(see Figure 4).

Figure 4

> ![](media/image4.png)

If you click the Search button, you will be directed to a Search results
page (see Figure 5). At this page you can also click on the link for the
AE page and be directed to that page.

Figure 5

> ![](media/image5.png)

Icons within Search:

Within the auto-complete search you may see icons next to search results
drop-down box. These indicate whether the search result is a property
(P), category (C), or Adverse event term (which has no icon).

For CTCAE purposes you may only need to search for the CTCAE SOC Adverse
event name. Therefore please disregard the items with an icon next to
them.

If you choose your search word (without an icon) and click Go, it will
take you to that particular AE term page. From there you can either
choose the Discussion tab or make a proposal.

Troubleshooting

If you have problems searching for a word, try entering in just part of
the word and then using the auto-complete. This should help you get a
broader search range.

If you have any other problems with Search, please consult the Help link
located on the main page.
**Test Log Document completion Plan**

+----------------------+----------------------+----------------------+
| > **Component**      | **Status**           | **Estimated          |
|                      |                      | Completion Date**    |
+======================+======================+======================+
| 1.  Adopter Test Log | Submitted in latest  | April 15, 2008       |
|     (for API)        | form                 |                      |
+----------------------+----------------------+----------------------+
| 2.  Software code    | Submitted in latest  | April 15, 2008       |
|     that shows       | form                 |                      |
|     objects input    |                      |                      |
|     and output from  |                      |                      |
|     system.          |                      |                      |
+----------------------+----------------------+----------------------+
| 3.  Test cases       | Submitted in final   | N/A                  |
|     document         | form                 |                      |
+----------------------+----------------------+----------------------+
| 4.  Final bug        | Submitted in latest  | April 15, 2008       |
|     reports          | form                 |                      |
+----------------------+----------------------+----------------------+
| 5.  Meeting on March | \-                   | March 31, 2008       |
|     31, 2008 to      |                      |                      |
|     update progress  |                      |                      |
+----------------------+----------------------+----------------------+

As part of this deliverable we are submitting: The software code for
analytical services, test cases document and test log document.
Documents are submitted in latest form and the plan for completion is
presented below.
![](media/image1.jpeg){width="1.625in" height="0.4527777777777778in"}NIH caBIG \| CCTS Security Requirements Project
====================================================================================================================

Topic: Questions for Legal Team 
-------------------------------

Date: August 8, 2008

The following questions will be used to filter and sort the use cases.

**Data Control**

*Patient Data Entered / Transferred*

-   Is patient data controlled at entry?

-   Is patient data controlled when transferred between applications?

-   Is access to patient data controlled?

-   Is patient data controlled in multi-site configuration?

*Study Data Entered/ Transferred*

-   Is study data controlled at entry?

-   Is study data controlled when transferred between applications?

-   Is access to data controlled?

-   Is study data controlled in multi-sit configuration?

**Administrative control**

*Rate-Specific Data Entered*

-   Is role criteria controlled at entry?

-   Is role criteria consistent between applications?

-   Are users assigned to roles according to documented controls?

-   Are role criteria consistent between sites in multi-site
    configuration?

*User Data Entered/ Authenticated*

-   Are users authenticated at login?

-   Is access to user/role assignments controlled?

-   Are users controlled in multi-site configuration?

*Audit Log Data Captured*

*Authentication*

-   What LOA (using the NIST pub 800-63 guidelines) is required for
    access to this data set based on HIPAA defined type of data and data
    steward determination? (authentication done at the cross application
    level and passes to data steward/application for determination to
    grant/withhold authorization)

*Authorization*

-   What is the (HIPAA-defined) type of data:

    -   PHI

    -   LDS

    -   De-ID

    -   Non-human

-   Who may access/transform the data (role based; data steward's
    determination)

    -   HIPAA may constrain (minimum necessary)

    -   Donor/patient informed consent (HIPAA or Common Rule) may
        constrain

-   Where will the data be sent/to whom (likely the who may access
    question but if mandated reporting, constraints may be obviated.

    -   HIPAA may constrain (minimum necessary)

    -   Donor/patient informed consent (HIPAA or Common Rule) may
        constrain

-   What if any FDA regulatory constraints are there on authorization
    (will this be imposed by the steward or in the application?)
Table 1: Polarization losses due to various components and diagnostic
tools typically used in their estimation:

+----------------+----------------+----------------+----------------+
| **             | **Component**  | **Typical      | **Diagnostic   |
| Polarization** |                | value**        | tool**         |
+================+================+================+================+
| Kinetic        | Anode          | 10-20          | Half-cell      |
|                |                | mV/decade      | (H~2~/H~2~)    |
+----------------+----------------+----------------+----------------+
|                | Cathode        | 120 mV/decade  | RDE            |
+----------------+----------------+----------------+----------------+
| Ohmic          | Membrane       | Iρl, ρ = 0.1 Ω | Current        |
|                |                | m, l = 50-175  | Interrupt      |
|                |                | μm             |                |
+----------------+----------------+----------------+----------------+
|                | Bipolar plate  | Iρl, ρ = 0.05  | Four probe     |
|                |                | mΩ m, l = 2-5  | method         |
|                |                | mm             |                |
+----------------+----------------+----------------+----------------+
|                | Catalyst Layer | Iρl, ρ = 0.2-1 | EIS, H~2~ pump |
|                |                | Ω m, l = 5-20  |                |
|                |                | μm             |                |
+----------------+----------------+----------------+----------------+
|                | Contact        | IR, R =        | \-             |
|                | resistances    | \~15-30 mΩ     |                |
|                |                | cm^2^          |                |
+----------------+----------------+----------------+----------------+
|                | GDL            | Iρl, ρ =       | Four probe     |
|                |                | 0.1-0.2 mΩ m,  | method         |
|                |                |                |                |
|                |                | l = 100-300 μm |                |
+----------------+----------------+----------------+----------------+
| Concentration  | H~2~, O~2~     | Nernstian      | Helox          |
+----------------+----------------+----------------+----------------+

.
![](media/image1.png){width="7.40625in" height="5.751798993875766in"}

Top three panels shows the pure positive and negative NAO composites of
250-hPa height anomalies for December, January and February. In January,
the height anomalies are zonally symmetric, with strong negative
anomalies in the polar region and positive anomalies around the latitude
circle in the midlatitude. In the February, the negative anomalies in
the Arctic Sea weakened and shift to the Iceland. Meanwhile, there is
negative anomalies forms in the Mediterranean???, emanating the second
wave train across North Atlantic.

The pure negative NAO composites for January shows similar anomalous
pattern as the counterpart of the NAO (+) with high degree with
annularity. However, distinct difference can be seen between composite
NAO(+) and NAO(-) in February. The anomalies in Aleutian are
significantly enhanced in February, and the positive anomalies in Arctic
Sea maintains through February, the second wave train propagate more
further down to the ??? . It is suggested that the non-linearity of the
transition from January to February between the NAO (+) and NAO (-).

![](media/image2.png){width="7.541666666666667in"
height="5.393624234470691in"}

Top panels are wave activity flux with (arrows) based on the pure NAO
(+) of height anomalies at 250-hPa, superimposed on contours for the
streamfunction (psi'=z'\*g/f, 10^6^m^2^s^-1^). In January, the wave
activity in the Aleutian region propagates eastward equatorward for NAO
(+), with none polarward component of wave activity. Thus the negative
anomalies disappear in Arctic Sea in the following month. While for NAO
(-), the wave activity propagates polarward to the Arctic Sea region.
The convergence of the wave-activity flux in the Arctic Sea explains the
maintenance of strong positive anomalies in the following month. In
February, the wave activity in the Aleutian region splits into two
branches, with one propagating polarward and the other one eastward and
equatorward. What's more, the wave activity flux propagating more
equatorward and east ward associated with the second wave train
emanating from the Iceland and North eastern Atlantic.

![](media/image3.png){width="7.473759842519685in" height="4.5in"}

The positive (top) and negative (bottom) NAO composites of the
stramlines for the mean flow at 250-hPa.

The split of the mean flow over Alaska is more distinct in the NAO(-)
composites. Specifically, the polarward branch is in the south-to-north
direction. Since the mean flow serves as a "wave guide" for the
high-frequency migratory eddies, it may be related to the more northward
wave-activity flux over that region.

![](media/image4.png){width="7.447916666666667in"
height="5.153397856517936in"}

The wave-activity flux based on the composite streamfunction anomalies
are very similar to the counterpart based on the composite height
anomalies, indicating it is reliable to getting the streamfunction using
the geostropcial approximation in the middle and high latitude.
A PILOT PROGRAM BRINGING COMPUTER TECHNOLOGY TO THE FIELD LEVEL IS BEING
EXPANDED BY THE NATURAL RESOURCES CONSERVATION SERVICE. THE MOBILE
TECHNOLOGY FIELD UNIT PUTS A LAPTOP COMPUTER WITH WIRELESS INTERNET
TOGETHER WITH A SCANNER AND PRINTER IN A PICKUP THAT NRCS SPECIALISTS
CAN TAKE OUT TO THE FIELD, EXPLAINS NRCS SOIL CONSERVATIONIST JEFF
VANDER WILT. "WE CAN TAKE .... Q: IN THEIR FIELDS :30.

ALREADY SEVEN MOBILE UNITS ARE IN PLACE ACROSS THE STATE AND FOUR MORE
WILL BE ADDED IN THE COMING WEEKS, BRINGING MOBILE TECHNOLOGY VIRTUALLY
STATEWIDE. VANDER WILT SAYS THE MOBILE TECHNOLOGY HAS BEEN ESPECIALLY
USEFUL IN THE PLACEMENT OF WATER PIPELINES AND TANKS AS WELL AS
CROSS-FENCING. "WE CAN SHOW .... Q: THAT WAY :23.

A FUTURE APPLICATION WITH THE MOBILE TECHNOLOGY WILL BE ADAPTED TO
MANURE SPREADER CALIBRATION FOR FIELD ACCURATE NUTRIENT SPREADING.

VANDER WILT SAYS AG PRODUCERS ARE THE CUSTOMER.... AND THIS MOBILE
TECHNOLOGY ENABLES NRCS TO BE MORE RESPONSIVE TO THEIR NEEDS.

I'M PG REPORTING FOR THE NATURAL RESOURCES CONSERVATION SERVICE, HELPING
PEOPLE HELP THE LAND

2/4 U
S.No. Tracker Id -- Reqr id-Reqr

1.  15859- -Automatic cache update between admin and cab2b server

2.  15860-User based experiments

3.  15861-User based saved queries

4.  15863-Asynchronous execution of queries.

5.  15864-User to override the services to be queried

6.  15865-Home page experiments links functional + show all

7.  15866- Popular categories and making home page category links
    functional + show all

8.  15867- Fixing the current washU services for index service

9.  15868-Support WS enumerations data services

10. 15869-**Need to revisit save / not save strategies-yet to clarify**

11. 15870-Asynchronous of save data list.

12. 15871-intermodel joins for a group like washU, NCICB , Intermodel
    joins with pair of service instances,

13. 15872-Experiments with multiple datalists, edit expr to add data
    list with way to re-query (more likely)

14. 15873-Support for getting probe data from caArray. For CEL files no
    need to bring data back to cab2b server, just get the URL and send
    it to analytical service.

15. 15874-Support basic analytical services (support for ICR services,
    if needed, do customizations)

16. 15875-Viewers for supported analytical services

17. 15876-Returning result of a federated query even if only one of the
    instances is failed.

18. 15877-Intermodel joins with multiple attributes

19. 15878-Technology Stack Migration

20. 15879-DE Release- **Why? What new features will it add to caB2B?**

21. 15880- Tree based view- The result view should be like a tree rather
    than the browsable view. It should be possible to add classes just
    to view without having to define predicates on these classes. The
    results should be available in a tree like view in the left panel
    and the spreadsheet view on right hand side.

22. 15881- Metadata to be selected in the Add Limit panel- Metadata that
    the user has searched for should be selected in the add limits panel
    when the user clicks on the metadata search results. For example, if
    user searches for Acute myeloid leukemia, as this is a PV for
    Clinical Diagnosis, the value in the Add Limits Panel should be
    selected or highlighted in some way.

23. 15882- Search for the child ontology's- It should be possible to
    search in the children values when specifying the parent node as the
    limit. For example, when I search for tissue site equals Breast then
    the query should also include sites which are the children of the
    above site in the ontology tree, like Axillary tail of breast,
    Central portion of breast, etc.

24. 15883-Expansion of categories- Category representation in different
    applications, that is category creation with different models. For
    example, we can define a category with different caTissue version
    like caTissuecore v1.0, caTissuecore v2.0, caTissueSuite v1.0,
    caTissueSuite v1.1 etc.
Results of Iteration 6 stress test at CCCWFU submitted 9/11/07 Robert
Morrell

Setup: 30 CCCWFU staff were provided a link to the CCCWFU instance of
caAERS, iteration 6. They were also provided instructions on the login,
and a script for adding an adverse event. Each user was expected to
spend 20-30 minutes entering events. Each user had been created as a
patient in the system, and users were instructed to create an event on
themselves. The caAERS adopter team (Robert Morrell, Steven Cheng and
Kim Livengood were also amongst the 30 invitees, and were working at the
same time to gauge system effects. All users except the adopter team
were using IE 6 or IE 7.

Results:

22 users were available and attempted to logon.

21 successfully logged onto the system (one user ignored instructions
and froze at the IE7 security prompt.

At least 4 users had a display problem (tracker bug 8869) that blocked
access to the routine AE screen, through which they were going to enter
events.

7 other users were unable to enter events for unspecified reasons.

10 users (7 users plus the three the adopter team users) were able to
successfully create an event.

The adopter team noticed some slowdown in the system (minor, on the
order of seconds), but were able to work. A batch effect was also noted
on the email notification (that is they were delivered at intervals in
large batches.

Other observations: Users' attitudes towards the system were certainly
clouded by the repeated security warnings caused by Internet Explorer.
The same workflow navigation issues noted in previous iteration testing
was encountered immediately. It was noted that protocol regulatory staff
did significantly better than patient managers navigating the system and
accomplishing the assigned tasks.

The google search feature was not well received, and some users were
convince that they had not been added to the system because when they
typed a letter, their name did not appear (other names pushed them off
the list until a second or third letter was typed). This will be a
blocker bug if there is a large patient set, and only initials are used.

Conclusion:

While the numbers were small, the system was able to handle the
workload. Since the current instance is a workstation, not a server,
better performance is expected when the instance is on a server
dedicated box. It remains to be seen whether the same test would be
successful once large patient and protocol data sets were imported. User
interface issues remain the largest concern, however, it should be noted
that several users, including those that did not like it, said it was on
par with other reporting systems, including ADEERS.
14 de mayo del 2008

Reglamentos de la Venta
=======================

**[Hora:]{.underline}** Se abrirán las puertas a las 9:00 a.m. La
subasta comenzará a las 9:30 a.m. y las puertas se cerrarán al concluir
la venta.

**[Términos:]{.underline}** Todas las ventas serán al
**[CONTADO]{.underline}**. No se aceptarán cheques y solamente billetes
hasta 20 dólares. Cualquiera excepción será previamente aprobada por el
Supervisor Encargado de la Venta.

**[Orden de Venta:]{.underline}** Los artículos serán subastados de
acuerdo al orden numérico de los lotes tal como lo especifica el listado
de venta.

**[Condición de los Artículos:]{.underline}** Todos los artículos serán
vendidos "como están" y "dónde están". No hay garantía. No habrá
reembolsos.

**[Base:]{.underline}** El subastador anunciará una suma mínima por cada
artículo. Los Artículos no serán vendidos a un precio menor a la suma
establecida.

**[La Venta Final:]{.underline}** El subastador hace la venta final
cuando anuncia: "Artículo 1 vendido al Licitador "X" por "US
\$\_\_.\_\_". **Las decisiones del licitador no son objetables**.

**[Pago de Artículos:]{.underline}** La forma del remate será **al
martillo.** Al final de la subasta, habrá 60 minutos para cancelar el
saldo mínimo de cada lote (**10% del valor**) o la totalidad de su
saldo. **Al día siguiente** se debe cancelar el resto de su saldo en el
Consulado General (Av. 9 de Octubre y García Moreno) en el
**Departamento de Caja entre 09:00 y 11:00 a.m.** Licitantes interesados
en arreglos de pago especiales podrán contactar directamente al
supervisor encargado de la venta.

**[Rechazos de Artículos:]{.underline}** Los licitantes deben pagar por
TODOS los artículos adjudicados. El rechazo de cualquier artículo lo
descalificará para las subastas siguientes y perderá el 10% del valor
cancelado.

**[Artículos No Vendidos:]{.underline}** Los artículos que no se vendan
NO se volverán a subastar al final de la venta.

**[Recolección de Artículos:]{.underline}** Ningún artículo será
entregado sin el recibo de pago. Los artículos pueden ser recogidos al
final de la venta del día miércoles 13 de 14h00 a 16h00, o el día jueves
15 de 9h00 a 16h00 y el viernes 16 de junio de 9h00 a 14h00. Los
artículos que no se recojan se re-venderán en una próxima venta.

**[Niños:]{.underline}** El Consulado no será responsable por la
seguridad de niños que vienen a la subasta y les pediremos a los padres
que salgan si tienen hijos disruptivos.
**Service Development:**

-   Reuse a syntactic model assigning different semantics

    -   Schema types used for serialization across multiple models

-   Reuse a logical model using different syntax

    -   Object Class resuse

    -   CDE reuse

    -   "whole model" reuse

**Resource Discovery:**

-   Discovery of Semantics for a given XML/WSDL type

    -   E.g. workflow or other dynamic invocation tools wanting to
        augment user/machine-assisted invocation

-   Discovery of Syntax (XML Schemas) for a Logical Model

    -   E.g. "I want to know how this data is serialized"

-   Discovery of available data/resources on the grid

    -   E.g. current discovery client

    -   What does finding services uses a class named "Gene" mean (if
        anything)?

**Runtime Invocation:**

-   Data pipelines

    -   Data-\> Analytical

        -   E.g. query a data service for experiment results and send
            them to a analytical service to do data summary/statistics

    -   Analytical -\> Analytical

        -   E.g. standard biomedical processing pipelines

    -   Analytical -\>Data

        -   e.g. "I have data from an experiment I want to store on the
            grid for others to see"

-   Federated Query Across multiple models (CDE-based joins)

    -   E.g. Current FQP does this

-   Data Mining Across multiple Models

    -   CDE extract

        -   E.g. "I want to find every 'drug name' that is mentioned in
            all the Data Services on the grid"

    -   Object extract?

        -   E.g. "Find me all the data related to the Object Class Drug"
Date: October 15, 2008

Topic: CTCAE Help Desk Tickets -- WG \# 6 SOC: Metabolism and nutrition
disorders

From: Ann Setser

Obesity Grade =3 states BMI 30 - 39.99 kg/m2 and Grade 4 states BMI \>
40 kg/m2. There is currently no way to grade = 40 kg/m2. Which grade
should this be incorporated into?

CTEP Response: GRADE 4 = 40 KG/M2 AND GREATER.
1.  caB2B\_Y3\_001-Automatic cache update between admin and cab2b server

2.  caB2B\_Y3\_002-User based experiments

3.  caB2B\_Y3\_003-User based saved queries

4.  caB2B\_Y3\_004-Asynchronous execution of queries.

5.  caB2B\_Y3\_005-User to override the services to be queried

6.  caB2B\_Y3\_006-Home page experiments links functional + show all

7.  caB2B\_Y3\_007- Popular categories and making home page category
    links functional + show all

8.  caB2B\_Y3\_008- caB2B\_Y3\_009-Fixing the current washU services for
    index service

9.  caB2B\_Y3\_009-Support WS enumerations data services

10. caB2B\_Y3\_010-**Need to revisit save / not save strategies-yet to
    clarify**

11. caB2B\_Y3\_011-Asynchronous of save data list.

12. caB2B\_Y3\_012-intermodel joins for a group like washU, NCICB ,
    Intermodel joins with pair of service instances,

13. caB2B\_Y3\_013-Experiments with multiple datalists, edit expr to add
    data list with way to re-query (more likely)

14. caB2B\_Y3\_014-Support for getting probe data from caArray. For CEL
    files no need to bring data back to cab2b server, just get the URL
    and send it to analytical service.

15. caB2B\_Y3\_015-Support basic analytical services (support for ICR
    services, if needed, do customizations)

16. caB2B\_Y3\_016-Viewers for supported analytical services

17. caB2B\_Y3\_017-Returning result of a federated query even if only
    one of the instances is failed.

18. caB2B\_Y3\_018-Intermodel joins with multiple attributes

19. caB2B\_Y3\_019-Technology Stack Migration

20. caB2B\_Y3\_020-DE Release- **Why? What new features will it add to
    caB2B?**

21. caB2B\_Y3\_021- Tree based view- The result view should be like a
    tree rather than the browsable view. It should be possible to add
    classes just to view without having to define predicates on these
    classes. The results should be available in a tree like view in the
    left panel and the spreadsheet view on right hand side.

22. caB2B\_Y3\_022- Metadata to be selected in the Add Limit panel-
    Metadata that the user has searched for should be selected in the
    add limits panel when the user clicks on the metadata search
    results. For example, if user searches for Acute myeloid leukemia,
    as this is a PV for Clinical Diagnosis, the value in the Add Limits
    Panel should be selected or highlighted in some way.

23. caB2B\_Y3\_023- Search for the child ontology's- It should be
    possible to search in the children values when specifying the parent
    node as the limit. For example, when I search for tissue site equals
    Breast then the query should also include sites which are the
    children of the above site in the ontology tree, like Axillary tail
    of breast, Central portion of breast, etc.

24. caB2B\_Y3\_024-Expansion of categories- Category representation in
    different applications, that is category creation with different
    models. For example, we can define a category with different
    caTissue version like caTissuecore v1.0, caTissuecore v2.0,
    caTissueSuite v1.0, caTissueSuite v1.1 etc.
GENERAL DECISION: **MO20080025** 07/25/2008 MO25

Date: July 25, 2008

General Decision Number: **MO20080025** 07/25/2008

Superseded General Decision Number: MO20070025

State: Missouri

Construction Type: Residential

Counties: Barton, Dade, Jasper, Lawrence, McDonald and Newton

Counties in Missouri.

RESIDENTIAL CONSTRUCTION PROJECTS consisting of single family

homes and apartments up to and including 4 stories.

Modification Number Publication Date

0 02/08/2008

1 07/25/2008

\* SUMO1990-006 01/29/1990

Rates Fringes

BRICKLAYER\...\...\...\...\...\...\.....\$ 7.00

Carpenters\...\...\...\...\...\...\.....\$ 7.98

Cement Mason/Concrete Finisher\...\$ 8.00

Electricians\...\...\...\...\...\...\...\$ 6.55 6% + .66

Laborers:

Screen Rakers\...\...\...\...\...\$ 8.63

Unskilled\...\...\...\...\...\....\$ 6.55

PAINTER\...\...\...\...\...\...\...\.....\$ 8.29

Plumbers and Pipefitters\...\...\...\$ 11.175 .92

Power equipment operators:

Backhoes\...\...\...\...\...\.....\$ 10.00

Blade Operators\...\...\...\....\$ 10.48

Bulldozers\...\...\...\...\...\...\$ 8.13

Cranes\...\...\...\...\...\...\....\$ 10.48

Hi-Loaders\...\...\...\...\...\...\$ 10.00

Pavers\...\...\...\...\...\...\....\$ 12.53

Rollers\...\...\...\...\...\...\...\$ 11.22

Tractors\...\...\...\...\...\.....\$ 10.25

Roofers\...\...\...\...\...\...\...\.....\$ 7.00

Sheet Metal Worker\...\...\...\...\...\$ 11.03

Sheet Rocker\...\...\...\...\...\...\...\$ 7.20

Soft Floor Layers\...\...\...\...\....\$ 10.08

Truck drivers:

Single Axle\...\...\...\...\.....\$ 8.00

Tandem Axle\...\...\...\...\.....\$ 8.27

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

WELDERS - Receive rate prescribed for craft performing

operation to which welding is incidental.

================================================================

Unlisted classifications needed for work not included within

the scope of the classifications listed may be added after

award only as provided in the labor standards contract clauses

(29CFR 5.5 (a) (1) (ii)).

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

In the listing above, the \"SU\" designation means that rates

listed under the identifier do not reflect collectively

bargained wage and fringe benefit rates. Other designations

indicate unions whose rates have been determined to be

prevailing.