Other Experience and Professional Memberships

2005-09 NIH Risk, Adult Addictions Study Section, member

2003-04 NIH Peer Review Committee: Psychobiology of Aging, ad hoc reviewer

2003- Board of Advisors, Senior Services of Eastern Missouri

2000- Associate Editor, Psychology and Aging

1998- Member, American Geriatrics Society

1998- Member, Gerontological Society of America

1995- Member, American Psychological Association

Honors

2008 Award for Best in Interdisciplinary Ethnography, International

Ethnographic Society

2005 Excellence in Teaching, Washington University, St. Louis

2003 Outstanding Young Faculty Award, Washington University, St. Louis

Publications

Most relevant to the current application

1. Merryle, R.J. & Hunt, V.L. (2004). Independent living, physical disability and substance abuse among the elderly. Psychology and Aging, 23(4), 10-22.
2. Hunt, V.L, Jensen, J.L. & Crenshaw, W. (2007). Substance abuse and mental health among community-dwelling elderly. International Journal of Geriatric Psychiatry.
3. Hunt, V.L, Wiechelt, S.A. & Merryle, R. (2008). Predicting the substance-abuse treatment needs of an aging population. American Journal of Public Health.
4. Hunt, V.L., Newlin, D.B. & Fishbein, D. (2009). Brain imaging in methamphetamine abusers across the life-span. Gerontology, 122-145.
5. Hunt, V.L. & Sher, K.A. (2009). Successful intervention models for older drug-abusers: Research across the life-span. American Psychologist, in press.

Synergetic activities

We plan to measure changes in cognitive ability and mental and physical health across a five-year period in a group of older drug users and matched controls. I have the expertise, leadership and motivation necessary to successfully carry out the proposed work. I have a broad background in psychology, with specific training and expertise in key research areas for this application. As a postdoctoral fellow at Berkeley, I carried out ethnographic and survey research and secondary data analysis on psychological aspects of drug addiction.

At the Division of Intramural Research at the National Institute on Drug Abuse (NIDA), I expanded my research to include neuropsychological changes associated with addiction. As PI or co-Investigator on several previous university- and NIH-funded grants, I laid the groundwork for the proposed research by developing effective measures of disability, depression, and other psychosocial factors relevant to the aging substance abuser, and by establishing strong ties with community providers that will make it possible to recruit and track participants over time. In addition, I successfully administered the projects (e.g. staffing, research protections, budget), collaborated with other researchers, and produced several peer-reviewed publications from each project. As a result of these previous experiences, I am aware of the importance of frequent communication among project members and of constructing a realistic research plan, timeline, and budget.

The current application builds logically on my prior work, and I have chosen co-investigators (Drs. Gryczynski and Newlin) who provide additional expertise in cognition, gerontology and geriatrics. In summary, I have a demonstrated record of successful and productive research projects in an area of high relevance for our aging population, and my expertise and experience have prepared me to lead the proposed project.

SAMPLE PROJECT SUMMARY OF THE PROPOSAL

THE NORTH CAUCASUS & VOLGA BASIN ACQUISITIONS PROJECT

The principle objective of this Project is to increase awareness and disseminate information about libraries in the North Caucasus and Volga Basin (paying particular attention to the non-Russian republics of the region) among the American library and academic community. This Project will accom­plish these objectives by conducting two acquisitions workshops, one in Rostov-na-Donu (North Caucasus) and one in Samara (Volga Basin), that will assess the current state of exchange relations with libraries in the area as well as conduct a survey of regional publishing.

The innovative workshop approach to acquisitions survey travel was used with great success in Khabarovsk (Russian Far East) and Irkutsk (Eastern Siberia) under IREX sponsorship in October 1994. These two workshops received outstanding reviews from both the participants and the Russian Ministry of Culture. The lessons learned in organizing workshops in these remote regions of Russia will make the North Caucasus and Volga Basin workshops even better.

Approximately twenty-six representatives from the most important libraries in each region (see attached list of candidate libraries) will be invited to each three-day workshop.

Each workshop will include sessions on: establishing exchange relations with American research libraries, the use of email to improve communications, and American librarianship, as well as one-on-one interviews with representatives of each library on everything from publishing trends in their city to their particular problems. The Russian Ministry of Culture has once again agreed to support these innovative workshops.

SAMPLE PROJECT DESCRIPTION OF THE PROPOSAL

Background

The Eclipse Business Intelligence and Reporting Tools Project addresses a broad range of needs in the business intelligence and reporting space using the Eclipse platform.

The business intelligence and reporting space is focused on tools and capabilities that extract data from data sources, process that data, and present the processed information to the end users. The information may be needed to enable the users to perform their operational or analytical job functions, or it may be customer-centric information such as a transaction statement. The capabilities can range from application- and production-level reporting, through ad hoc user-driven query tools, to highly interactive multi-dimensional online analytical processing (OLAP) and data mining tools. While many business intelligence and reporting applications access operational data sources, it is often the case that developers provide specific data warehouses to support the business intelligence and reporting needs of an application. The tools in this space can include facilities to help build these data warehouses.

It should be noted that a given application often needs a range of complementary capabilities in this area to meet the needs of different users of the application. For example, consider components of an online order processing application: The individual order invoices will be printed for inclusion in the shipping box and the shipping clerk will need an online or printed shipping list (both production-level reports); while a product line manager may want to perform ad hoc queries to see which products generate the most returns; while the purchasing agent may use analytics to look for trends and improve stocking levels. Providing a range of coordinated and complementary capabilities under the Eclipse Business Intelligence and Reporting Tools Project is intended to ensure that the developed technology can effectively be used to meet this broad range of needs.

Initial Goals

Initially, the Project will focus on leveraging the Eclipse platform to provide infrastructure and tools for the designing, deploying, generating and viewing of reports in an organization, including ad hoc query and reporting tools. While not an initial focus, the BIRT project scope includes complementing these reporting capabilities with Online Analytical Processing (OLAP) and Business Intelligence dashboard functionality. Over time, but not in the initial scope, the creation of additional projects is anticipated and encouraged to address additional aspects of business intelligence, such as Executive Information Systems (EIS), statistical analysis, modeling capabilities (what-if analysis), Data Mining Tools, Data Warehouse Modeling Tools, Extract Transform and Load (ETL) tools and Data Quality Tools.

The initial deliverable of the Eclipse Business Intelligence and Reporting Tools Project is to provide a robust platform that can be used to quickly and effectively create and deploy reports with any degree of complexity without having the developer create the data access, processing and formatting logic using Java code or components. In the majority of cases, the report developer will design a report within the Eclipse framework using a 100% visual design paradigm. However, in recognition of the fact that the variety of report layouts and complexity of data access is infinite, the project will also support extensive programmatic customization of the report generation processes, including programmatic creation of report designs.

About Reports

Reports extract data from a data source or sources, perform manipulations and calculations on the data to answer business questions, and present the results as information in a formatted and convenient form for the business user to use. This information is then typically used for operational or decision support purposes within an organization. Reports vary dramatically in size, content and complexity and will include or combine characteristics such as:

• Listings of information. Example: Transactions in an account.
• Sorting, grouping and aggregation of data with and without subtotals. Example: A listing of all product sales for each sales person, grouped by state.
• Charts to present information in easy to understand formats. Example: Pie chart showing an investor's portfolio allocation by High Growth/Growth/Income/etc. categories.
• Matrix or cross-tab layouts. Example: Financial budget reports with cost codes as rows, columns for each month, and cells containing numerical data for that cost code/month.
• Delivery of information as one or a combination of web pages, PDF files, printed documents, Excel files, etc. Example: Frequent flyer statement delivered as a web page online and a printed document in the mail.
• Precise, highly formatted layouts. Examples: Bank statements; utility bills; commission statements; invoices; government forms.
• Page navigation for long reports. Examples: Hundreds of pages corporate cell phone usage bill with First Page, Next Page, Go to Page, etc. buttons).
• Table of Contents. Example: Multi-page Investment Portfolio summary with Table of Contents to quickly navigate to Account Summary; Fund History; etc.
• Keyword or content search within a report. Example: find information on a customer in a 1000 page customer account report.

This can be contrasted with data-driven JSP pages where the data manipulation and presentation needs are more transaction driven and do not include recurring reporting needs such as complex aggregation (performed outside of the database) and highly complex layouts.

Target Users

For report development, the project broadly targets three classes of developer:

• Application Developers. These are Java developers who are creating applications that include the need to retrieve data and present that data in the form of reports. This is likely to be a subset of the overall application and will include many of the characteristics discussed above. In this case, the report generation and viewing will be embedded in the overall application.
• Report Developers. Report developers are not typically skilled in writing Java code. They expect to use a visual desktop tool to create any type of report - including defining database connections, report content and report layout. These reports may then be deployed as part of an application, or through an easy to use deployment framework.
• Business Users. Business users often want to create their own report layouts or customize existing reports. They work through a very easy-to-use web-based report creation and editing facility to answer business questions on an ad hoc basis.

Architecture

The project will address both the design time needs of report creation as well as the run-time requirements of report generation and deployment. A high-level architecture diagram is provided below. The project will adopt and support accepted open standards wherever feasible.

The Eclipse Business Intelligence and Reporting Project is divided into a number of sub-projects that reflect the initial focus on the reporting aspects of business intelligence and the high-level architecture of the project. These are discussed in the sub-project section below. As discussed above, the creation of additional sub-projects is anticipated and encouraged to address additional aspects of business intelligence.

Due to the wide variety of potential applications, it is recognized that BIRT cannot meet all the requirements of all applications. It is therefore a core design principle for the projects within BIRT to support a broad range of extension points within the tools and frameworks that allow developers to address additional needs. These extension points may be utilized for adding value in commercial products using BIRT, or may be developed and contributed into the Eclipse open source community.

For example, logging tools can use BIRT's data extension point to plug-in a data query user interface and access logic to read and process log files, use BIRT's report engine to present the information in the log, and extend BIRT's output/rendering adaptor to email or send a short message to a user with the report output in a format targeted for that device.

We expect the Business Intelligence and Reporting Tools Project to produce functional requirements that are more appropriately satisfied through the Eclipse Project or other Eclipse foundational projects. In such cases, the Business Intelligence and Reporting Tools Project PMC will coordinate the corresponding Project PMCs the design and implementation of the corresponding contribution.

http://www.eclipse.org/birt/phoenix/project/description.php

Appendix7. Sample business letters

Structure of formal letter

Government of Canada¹

Office of the Chairman Public Service Commission²

Ottawa, Ontario K1A ON7

Attention: P. Smith³

Decembers 8, 1996 ⁴

Dear Sir: ⁵

Ref: PC Program analyst ⁶

Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx⁷

Yours sincerely, ⁸

²⁾ Robertson Director⁹

General Services Division

AP/CL ¹⁰

Encl. ¹¹

cc : D.Dube¹²

1. Заголовок

2. Внутренний адрес. Адрес того, кому предназначено письмо, размещается вверху. Если Вам известно имя человека, которому предназначено письмо, то его звание и полное имя указываются здесь же.

3. Строка: внимание.Включается в тех случаях, когда письмо отправляется, например, в компанию, но адресовано кому-либо лично.

4. Дата

5. Приветствие

6. Ссылка

7. Основная часть

8. Комплиментарная концовка. Обычные окончания:

British	American
Yours truly,	Truly yours,
Yours sincerely,	Sincerely yours,
Yours faithfully,	Faithfully yours,

9. Подпись, должность, отдел. Подпись, расшифровка подписи, должность следуют друг за другом в строку в левом или в правом углу письма.

10. Посылочные инициалы. Посылочные инициалы указывают на тех, кто писал / печатал / переводил письмо.

11. Вложения. Если к письму прилагаются какие-либо материалы, то об этом упоминается после посылочных инициалов.

12. Копии. Указания на адресатов копий письма даются в самом конце.

Structure of informal letter

Heading:

Salutation: Body:

Closing: Signature:

316 Indiana Drive

Glenshaw, Pa. 11651

February 26, 1975

Dear Mary,

As you may have heard by now, I’m planning to attend Indiana University in the fall. I’m not certain about my major yet, but I’m very much interested in ecology. Does Indiana have such a major? Maybe I’ll have to settle for biology and specialize later. Un­doubtedly the catalogue will answer this question and similar ones. Could you send me a copy?

I have a million questions I would like to ask about dormitory living, social life, etc., but I’ll wait till you get home for vacation. Let me know when you’re coming. I want to plan a welcome home party.

Love,

Jane

Sample report

Site accident report Executive summary Damage has been caused to the emergency generator on the Witherby power plant site. It was caused by a fire started by the electrical contractors Mullet & Sons. Although the packing material that caught fire was left by another subcontractor, the personnel from Mullet started work before clearing the waste matter away, in contravention or contract regulation 2.3.8. Mullet & Sons should therefore pay for the replacement of the damaged equipment. Introduction This report will look at: • the sequence of events • the subcontractors involved • the responsibilities of the subcontractors • the financial compensation from the subcontractors • recommendations to avoid future incidents of this nature Findings 1. Fire broke out at 17.30 on Friday 13 October in the working area around the emergency generator. Ail personnel were cleared from the site and the fire service informed by 17.45.The fire-service arrived at 18.00 and the blaze was extinguished by 18.30. 2. The electrical contractors Mullet & Sons started the fire accidentally when carrying out the connection work of the generator to the main power line. Packing material left on the ground by another subcontractor Harvest Macdcugail plc caught fire and this quickly spread. 3. Although Harvest Macdcugail are obliged to remove any packaging material they bring with them it seems that the electricians from Mullet told them to just leave it. We assume they wanted to get their own work done as quickly as possible so that they could finish for the weekend. Starting welding work without first making sure there is no inflammable material around is in direct contravention of contract regulation 2.3.8. Conclusion Mullet & Sorts must pay for the replacement of the generator (? 90,000) as they are solely responsible for the damage. Recommendations 1. Moist & Sons should not be offered any more work on site if they do not accept these terms. 2. Harvest Macdougoil should receive a formal warning. 3. All subcontractors must be reminded of their obligation to follow all fire and safety regulations.     Normal Poole Site Manager 19 October

Sample letter of request