# Program Portal JAD Meeting

**Date:** October 9, 2001

**Time:** 1:00--4:00 p.m.

**Location:** Logicon, 1700 Research Blvd., Room 4005

**Facilitators:** Bud Erickson, Carlos Caban

**Technical Leads**: Krishna Collie, Michael Martin

[**Next Meeting**: **Monday**, October 15, 2001, 1 p.m., Logicon, Room
4005]{.mark}

**[Agenda:]{.mark}** Revisit the Functional Decomposition List

Review and determine broad content areas (e.g., pending, awarded)

### Action Items

-   Krishna to determine the ICs that have an Intranet.

-   Krishna to get a list of status codes for the JAD's evaluation.

-   Johnnie to send the GILS specs to Krishna.

### Overview

The JAD continued identifying requirements for the program process flow.
The program universe in the process flow diagram (p. 4 of Program
Process Flow handout) was further delineated by Krishna, grouping the
"planets"(functions) into "constellations," (related functions). After
the JAD has identified the requirements, it will prioritize them within
each phase. *It will then determine those to be included in the first
release of the portal. The remainder will be assigned to future
releases.*

### Extension Systems

Richard Fisher asked if the portal will link to extension systems
developed and used by individual ICs. During the discussion, the
following points were made:

-   If the local extension system is already Web-enabled, it's possible
    to link it to IMPAC II and be accessible through the portal.

-   The purpose of the IMPAC II and portal projects is to make all the
    data and functionality needed by ICs available. Over time, as the
    functionality of the local extensions is built into IMPAC II and
    available through the portal, many local extensions will disappear.

-   The JAD is trying to crystallize the requirements of the ICs (must,
    could, should, won't) to determine what can be plugged into the
    portal that would be of use to the broadest number of people in all
    ICs.

### Process Workflow

The JAD made the following suggestions and changes for developing the
portal.

-   **Broad Content Areas**. Separate grants into "Pending" and
    "Awarded."

-   **Intranets**. Leverage the information on IC Intranets. Not all ICS
    have them but a survey of what's available would be useful.

> **Action: Krishna to determine the ICs that have an Intranet.**

-   **Application Status Codes.** Each application has a status code,
    and there are several codes. From a portal perspective, it might be
    useful for the JAD to examine each status code and determine what
    information is needed and what action needs to be taken.

> **Action: Krishna to get a list of status codes for evaluation.**

-   **My Portfolio.** The JAD agreed that what is really needed on the
    portal is a "My Portfolio" portlet, which would include the status
    codes of assigned applications, action list and an embedded paylist.
    It could also include a "To Do" list and a notes section, one
    personal and one subject to FOIA.

-   **GILS.** Use the government indicator locator service (GILS), which
    is an indexing standard for the Web, for standardization of data and
    key words, and more efficient search capabilities.

> **Action: Johnnie to send the GILS specs to Krishna.**

-   **Scientific Resources (p. 21).** Add the following for possible
    portlets.

```{=html}
<!-- -->
```
-   Yellow sheet calendar of seminars and workshops.

-   Filter/profile for individual calendar.

-   Drop-down list (societies, journals).

-   Scientific societies. Maintain own list. Provide a master list from
    which to develop own list (indexed).

-   Porpoise (search engine).

-   Card catalog (esp. Library of Congress).

```{=html}
<!-- -->
```
-   **Current Scientific Trends/Knowledge.** Add the following for
    possible portlets.

```{=html}
<!-- -->
```
-   Interest groups at NIH. If minutes, could tap into them.

-   Local events: My Meetings.

-   Committee websites.

```{=html}
<!-- -->
```
-   **General Program Administration.** Add the following for possible
    portlets.

```{=html}
<!-- -->
```
-   My Portfolio.

-   Committee Service identification (p. 23) with advanced person
    search, expertise and committee service history.

-   Medline/Pub-Med.

-   People: who's funded, progress reports, expertise, and committee
    service history.

```{=html}
<!-- -->
```
-   **Miscellaneous**

```{=html}
<!-- -->
```
-   Provide the ability to track progress of PIs via progress reports.

-   Provide a "Hot Topics" portlet as a repository of personal files.

### Demonstration of FirstGov

Johnnie demonstrated the FirstGov website, which he developed for the
Clinton Administration. He showed how he programmed key words for each
page so that search engines could more easily find information. He
suggested that as we develop the portal and programs, we keep aware of
commonalities so that our systems will be easier to use and access.

Attendees

Caban, Carlos, Co-Facilitator, OD

Chatterjee, Ranesh, Logicon

Sue Kennell, NIMH

Collie, Krishna, RNSolutions

Erickson, Bud, Co-Facilitator, NCI

Fisher, Richard, NEI

Greenleaf, Andy, Logicon

Hann, Della, OD

Lederhendler, Israel, NIMH

Panniers, Richard, CSR

Pearson, Johnnie, Z-Tech

Seppala, Sandy, LTS/OPAE