Web call on meta tagging of hubs, Hub search engine, and CVS server was held on January 17, 2003. Fernando, Laura, Daeho, Tim, Curt, Andy, Todd, and Jean were on the call.

Action items:

• Add “metatags.cfm” (second version, with center_id variable at top) to your hubs folder
• Add code (cfinclude template=”metatags.cfm”) to index.cfm and bottom.cfm files
• Chris will develop an interface in the administrative pages of the topic hubs that allows Centers to associate programs in their region with the topic hub
• Daeho will develop an interface in the program directory input form that allows centers to associate programs with topic hubs
• Supply Tim with username and password (different words, eight characters each) so you can have access to the CVS server
• Use the CVS to make any changes to the topic hub code
• Use bugzilla to report bugs in the code (see Tim if you need info on how to do this)
• Keywords call for web group on Monday, Jan. 27th at 1:00 ET, noon CT, 11:00 MT, 10:00 PT, 402-472-6899

Meta tagging topic hubs
Fernando sent a file that is a template that needs to be added to hubs folder. (He sent two versions, use the second one, which contains a variable at the top for your center ID.) The file name is “metatags.cfm”. This file is specific for topic hubs. It allows topic hub pages to be meta tagged for recognition by the EPA search engine. Centers need to addcode to the index.cfm and bottom.cfm files. Code to add is, “cfinclude template=”metatags.cfm””

Fernando also sent a template for example purposes so we can see a template that can be used for the whole site, but it’s not met to be installed.

Where to go for help (WTGFH)
We will keep the authority keywords out of the picture for now. The “quick fix” is to keep it simple. We’ll create a table,

This relates the organization ID (org_id) from a Center’s regional programs database to specific topic hubs (hub_id). Since the center displaying the topic hub (center_id) is included in the table, it won’t matter that different centers will have the same organization IDs for different programs in their directories. The date the program record was added or modified is captured also (date_stamp).

We’ll use real time exchange to get national programs from hub owner. In the current process of exchanging the hubs, we get lots of information as to where things are located on the host Center’s site, including images, addresses, etc. Every hub has a WTGFH gateway. When we share the hubs, we’ll automatically know where this gateway is. Then if a user clicks on WTGFH, it will automatically query the hub host center. If the hub host’s site is down, the query will fail. The regional programs should still come up, though. This solution does not allow us to display programs other centers have identified as associated with that hub for their region.

We’ll need to develop an interface in the administrative pages of the topic hubs that allows Centers to associate programs in their region with the topic hub.

We should also have an interface in the program directory input form that allows centers to associate programs with topic hubs they’re entering or modifying. Daeho will work on this when he reworks the programs directory administrative forms.

Individual Search Engine
Andy sent a zip file for us to unzip for the topic hub search engine. There were bugs identified so Andy will send two revised files within the hour. Implement as we discussed on the call. If you have questions, call Andy.

CVS Server

Tim demonstrated the CVS server. He needs a password and user name (must be different, eight characters each) from everyone who wants to be able to check out the code. He pointed out that we all need to upload the code daily so we don’t get behind if we or anyone else makes changes. There’s a function that allows you to view the differences in two versions of code. If two people check out the code and make changes that conflict, the last one to submit changes will be notified in order that they can resolve the conflict.

Tim also showed us Bugzilla, program management software where people can report different bugs they find, the bugs can be assigned to someone to be fixed, and when fixed, e-mail is automatically returned to the person that reported the problem.

Laura suggested we all commit to using this system. Various levels of torture were discussed as a means of enforcement.

Keywords

We haven’t talked about all the pending code changes and the changes to the keyword table. We’ll have another call Monday, January 27th at 1:00 ET, noon CT, 11:00 MT, 10:00 PT. The number to call is 402-472-6899.

TOP