Topic Hub Development Process Guide

Overview

This document provides an outline of a suggested process fordeveloping a single Topic Hub to serve the P2 Specialist (see definition) community. A Topic Hub is intended to provide a topic-specific guide to collected resources about the topic available and accessible from a browser connection to the internet. This document is directed to the Topic Hub developers, teams of information specialists putting together individual Topic Hubs as part of a larger Topic Hub Project. The suggested process within this document should be used in conjunction with the more precise information descriptions of the Guideline For Topic Hub Records.

Product

A Topic Hub provides a web-based guide to the resources specific to a particular subject, i.e., it is a "subject-specific resource guide." Additionally, the guide serves a particular user or set of users, in this case the P2 Specialists and their clients.

Process

1. Define the topic that is the subject of a Topic Hub. As a rule of thumb, the more narrowly defined, discrete topics will be easier to manage than will be broad topics. A place to find topics could be the current issues of list serves and rapid response services.

2. Build the pile of information pertaining to the topic. Requests for bookmarks/favorites on topic- or audience-related list serves are useful starts, as are visits to topic "authority" sites.

3. Sort and categorize the information about which the Topic Hub provides a guide. Issues to consider during thes process:

a. Information accessibility - resource copyright, security, or format can prevent accessility.
b. Content presentation - where the resource will best support the Topic Hub narrative.
c. Distributed usability - resource information provides "fit" with potential users, e.g., P2Rx

4. Write the narrative that guides the user through the collected resources.

5. Review, publish, and market the Topic Hub.

P2RIC model

The Topic Hub model presented by P2RIC at the spring meetings of P2Rx and NPPR adds value to a traditional "list of links" by adding the following features:

- Providing a short description of the resource.
- Assigning the most valuable resources to particular topic subcategories.
- Building a database and allowing full text search of the resources.
- Providing a review of the resource value
- User review capability
- Solicit additions to the resource database

Development Issues
- A collections policy for Topic Hub resources.
- Standard copyright/permission language for "deep link" resources.
- Information sharing, distributed data retreival mechanisms.
- Partnership/republishing agreements for external content publication.

Topic Hub Development P2RIC Process Guide

Overview

This document provides an outline of the work necessary to develop a topic hub to serve the P2 Specialist community. The Topic Hub is intended to provide a topic-specific guide to collected and community-reviewed resources on the internet. This document is directed to the Topic Hub developers, a team of specialists identified later in this document. This document should be used in conjunction with the Guideline For Topic Hub Records.

A. Preparation
1. Establish the author-publisher relationship. The primary author, as a subcontractor, collaborator, or staff writer, develops the topic hub in conjunction with the topic hub host. The web site program acting as host performs as the technical and editorial support for publishing the topic hub in a uniform presentation with other topic hubs. Roles and responsibilities are suggested in the process description below and in a supporting table. The primary author essentially provides the topic hub content, subject to format review and approval by the topic hub publisher.

2. Become familiar with the topic hub model and guidelines. A topic hub provides a structured, informative guide through an order list of several links to particular topic authorities. A topic authority is deemed to be the best source of information on a particular topic, often linked to by many hubs regarding that particular topic expertise.

3. Define the topic. This first definition should be broad enough to meet expected audience needs. This definition will likely be narrowed over the course of the project. For example, "Agriculture" is too broad to be handled well by the topic hub format, but confined animal feeding operations (CAFOs) are most likely suitable for a topic hub - typically not longer than 5-7 single page printed pages of content and a fully described and full-text-searchable collection of authority web sites.

4. Remember the intended audience. These topic hubs are developed to serve the P2 Specialists (Technical Assistance Programs (TAPs), Small Business Development Centers (SBDCs), Small Business Assistance Programs (SBAPs), NIST Manufacturing Extension Partnerships (MEPs), Cooperative Extension programs, consultants, vendors) and their customers (businesses, manufacturers, and public agencies). Page content is typically directed towards the end user, e.g., "Top 10" or "Things To Do" lists. Link descriptions, search function and resource reviews are directed more towards the P2 Specialist and service provider community.

B. Process

1. Identify peer reviewers/topic hub collaborators. This is done both by the primary author and the regional information center/topic hub publisher. Solicit their help in performing the topic hub construction. Benefits of their efforts can include acknowledging their work and linking to their program, developing a community, tool construction for use in a new or existing project/program.

2. Gather the pile of information. Typically done in conjunction with a rapid response service of the P2Rx, or subsequent to a list serve query that generates a "thread" of replies with good information sources. Ask peer reviewers for their favorite bookmarks on the subject, as well as one most important, "essential" reference site. Check the links lists of these initial sources for additional sources. [Note: Occasionally, "essential" topic material is not available as a web-based resource. With permission from the resource copyright holders, written publications P2Rx will convert these to .pdf files for web publication].

3. Research and develop the initial draft of the content pages of the topic hub. Content is written in easily digestible bullet or action item format. More editing guidance is available in the Guideline For Topic Hub Records.

- Introduction and Table of Contents. Most of this section to be done by publisher. This provides more of a description about the hub than the topic. Content categories are not expected to change. Credit to author(s) on this page.

- Topic Background/Overview. This section defines the topic, explains where it is found or used. Describes topic context in global sense

- Operations. This section describes how the topic works. Input/Output process diagrams are useful here. Descriptions to help one new to the topic understand working basics.

- Reasons for Change. This section identifies reasons to change. This provides a spot for regulatory and compliance issues, among others reasons for change. "Top 10" lists are helpful, as is a list of waste impacts. If typical wastes are mentioned in previous section, this section should identify pertinent body of regulations associated with the waste.

- Pollution Prevention Options. Alternatives for change are provided in this section. BMP (best management practice) and action lists helpful, especially when directed towards the issues identified in the previous section.

- Where to Go for Help. This section may best be done by the Publisher, reworking information from other topic hubs. Credit for author(s) here would be appropriate if the author wishes referrals.

- Staying Current. Organizations and publications pertaining to the topic. The publisher may be able to make this an active news page if collaborations are built with topic news sources.

4. Catalogue the web resources. A big topic hub may have well over 100 web documents that need to be catalogued. More often, the hub is expected to have closer to 50 web documents. The resources need to be described and assigned relative to each pertinent subtopic. Additionally, core or essential documents need to be selected for each subtopic. Publisher will seek permission for use. Data descriptor assignments should adhere to the guidance document and may be done in conjunction with publisher staff.

• Welcome & Table of Contents. At least 1 core reference authority web site or document.
• Topic Overview/Background. Usually a trade publication or introductory chapter from a comprehensive reference.
• Operations. Process flow diagrams helpful.
• Reasons for Change. Problems and opportunities typical to topic. If regulatory issues are pertinent, compliance centers often a core link.
• Pollution Prevention Options. Best mangement practices, or P2 checklists helpful here. This will likely be the largest subset of links and core links for each Topic Hub.
• Where to Go for Help. Publisher may provide regional listing of experts along with national organizations and evolving national program listings.
• Staying Current. Topic calendars, news pages.

5. Provide "user review" and ranking of selected web resources. Also, when the author or reviewer is familiar with a resource, ranking its usefulness is appropriate.

6. Review Topic Hub product. When all of the content and data elements have been created, the publisher will post them on line for in-house review. Check the product.

C. Topic Hub Team Skillset & Responsibilities

The following table lists likely team members, responsibilities and skills required for a successful Topic Hub. Note that while all the responsibilities and skills are necessary, they may not all be assigned to the team members as shown below.

Suggested Reading:

The Topic Hub is written for the P2 Specialist community. To find out more about a P2 Specialist, read the DACUM analysis at http://ateec.eiccd.cc.ia.us/dacum22.html. The DACUM contains lists of job tasks performed, and provides a valuable starting point.

There are many resources for the gateway model, but the first effort P2RIC found, which now has a handbook is Project DESIRE, http://www.desire.org. Strongly recommended is the DESIRE Information Gateways Handbook, http://www.desire.org/handbook.

The need to classify discrete sources of expert information to enhance information access is illustrated nicely at http://www.nuapublish.com/classify/index.html#1.

A good illustration for the concept of hub versus authorities or resources is found in the June 1999 Scientific American article, Hypersearching the Web, available at http://www.sciam.com/1999/0699issue/0699raghavan.html.

Back to P2Rx Administrative Information

TOP