This list of steps in the OSTI-to-Site TAPping process covers three main phases. Preparing to enter into the process is when the site actually does the most work; this is when metadata mapping and the technical development takes place. The testing phase is simple but takes up a significant amount of time in the process. The production phase is an ongoing one based primarily on monitoring for quality control. In the lists below, S stands for “Site” and notes a step that is performed by the participating site; O stands for OSTI, indicating OSTI’s responsibility for that task.
Preparing: Mapping and Technical Development
|
1
|
S
|
Site contacts OSTI’s TAP manager (TM) to express interest.
|
|
2
|
S
|
Site sends data dictionary to TM via email. Data dictionary may be as simple as a list of the fields (and their definitions) in the site’s review/approval or other database from which metadata could be retrieved for TAPing.
|
|
3
|
O
|
TM prepares first draft of a mapping matrix and returns it to site for review.
|
|
4
|
S&O
|
Back and forth editing until matrix is relatively complete.
|
|
5
|
S&O
|
Conference call to go over matrix together and ask final questions, make final agreements. Call includes site contacts, TM, and OSTI’s TAP programmer (TP). Questions that are resolved via the matrix are:
The call is also used to discuss the technical requirements for the next step in the process.
|
|
6
|
O
|
TM includes all changes from conference call and outputs final version of the mapping matrix. Distributes to all involved. Also prepares detailed data and parsing specifications and provides to OSTI’s TP.
|
|
7
|
O
|
TP builds the customized directories, parser/mapping file, and default processes that will handle the site’s metadata.
|
|
8
|
S
|
Site programmer (SP) establishes a web service for TAPing and provides URL to OSTI.
|
|
9
|
S
|
SP prepares query script and sample XML output file. Sends sample file to OSTI.
|
|
10
|
O
|
TP manually loads the sample file into the test E-Link database. Suggests revisions as needed.
|
Practicing: The Test Phase
|
11
|
O
|
TP runs specific tests on the connection with the web service newly established by the site. Adjustments may be needed on either end.
|
|
12
|
O
|
OSTI manually conducts a TAPing run against the site’s database. It is a real-time test of the new web service, the site’s query script and XML output file, OSTI’s customized mapping file for the site, etc. It is the first chance to see how the real process will work.
|
|
13
|
O
|
TM individually checks all citations, comparing how they appear as raw data in the XML output file with how the citation is loaded and formatted into Test E-Link. Problems are relayed back to the site for correction.
|
|
14
|
S&O
|
When the first run is deemed successful, a scheduled is agreed upon for the test runs. These typically occur once a week on a Tuesday, Wednesday, or Thursday. The start date for the test runs is set.
|
|
15
|
O
|
TP sets the test system to perform these test runs automatically.
|
|
16
|
O
|
Following each test run, TM reviews the records and informs site of errors or changes in mapping that need to be made. Testing is done until all document types have been represented and all runs have been error free on a consistent basis. This typically takes six weeks, but may take longer depending on down times, time lost while corrections are being made, etc.
|
|
17
|
O
|
When OSTI and the site agree that the testing is consistently stable and successful, the OSTI TM prepares the final test report and provides to the site.
|
Doing: The Production Phase
|
18
|
S
|
Site notifies OSTI that it has resolved any issues that were still open when the test report was issued.
|
|
19
|
O
|
OSTI does some spot checking, tests changes, etc.
|
|
20
|
S&O
|
Schedule for production runs is set. It is often the same time that was used for the test runs. Final decisions are made on things such as:
|
|
21
|
O
|
TP sets the production system to perform these test runs automatically.
|
|
22
|
O
|
The first production run is performed according to the agreed-upon schedule. The automated email is sent to the site and to the appropriate OSTI distribution list.
|
|
23
|
O
|
TM reviews the first production run in the same detailed way that the test runs were checked. Confers with site on any errors.
|
|
24
|
O
|
After the production run is pronounced successful, TP performs the catch-up run according to the agreed upon schedule.
|
|
25
|
S
|
Each week the site checks to ensure that their citations TAPed in the previous week have moved into the Dublin Core database and appear with the correct OSTI ID. Site notifies OSTI of any omissions.
|
|
26
|
S&O
|
Site notifies OSTI of any changes in URLs or metadata. TM ensures that the changes are reflected in the mapping matrix, DTD, parser, etc.
|
|
27
|
S&O
|
OSTI notifies site of any system changes that require site to modify query script or XML output file. Site ensures these changes are made in a timely manner.
|
