/odma/support
Construction Log

Change History

2001-05-04-04:35 Make Consistent with DMware Construction Structure (orcmid): The construction structure and home pages are touched up to reflect the expansion of DMware coverage and tying of ODMA support to DMware coming out of AIIM 2001.

2000-07-11-11:24 Tie in ODMA 2.0 Support Summary and Use ODMA Logo (orcmid): 1. So that copies of the ODMA 2.0 Specification always have a persistent location to reference for the latest status of ODMA and ODMA 2.0, the ODMA 2.0 Status page is created here.
2. Title blocks of the home page and this page are also corrected to provide greater integration with AIIM DMware, using the ODMA logo image for context and linkage.
2000-06-24-10:28 Move FAQtips to separate odma/faq section (orcmid): In responding to a request to allow links to some of the FAQtip material, I decided that it was a good time to move these items into their own section where management will be easier separate from the incident-report material here.
1. The faq section is created.
2. The draft of FAQtip Q000600 is moved to that section immediately so the URL can be confirmed. There is trivial cleanup and the works is loaded to the VServers site.
3. Even though this draft FAQtip was not linked into the support section, it was on the server, and I mentioned it to people. So I branched the VServers copy here and shared it back to here after the move in (2). Then I turned the branched copy to a tombstone in the usual way.
4. The unpublished FAQtip page is also moved to the new section. No tombstone is required.
5. The material in this change history about creation of the FAQtip is incorporated in the new construction page and abbreviated here.

2000-06-23-09:22 Create Summary Pages for Incident Reporting (orcmid): Now that there are two incident reports, it is time to organize the summaries and change the way people are able to find out what is being worked on, what is resolved, and what changes may be coming. This is being done manually to develop a sense of what works and what the connections are, taking advantage of HTML for organizing material in many ways. This practice doesn't scale. After creating structures that work, we will look at use of automated tools to support the management of support projects and maintenance of the reports that are our instruments for this. (Here's a nice specimen document-management situation that also relates to process quality techniques.)
1. I reviewed the SourceForge bug-list format for minimum required information and then built X00-log for the year 2000 chronological index. This log is maintained in reverse chronological sequence and is a simple table of all incidents that are ever given X-number IDs in 2000. Any problems recovered from earlier years will be given IDs in 2000 month 00 (!), punting Y2k to Y2.1k.
2. I used this file to create the active-incident page, using the identical format. This file has critical problems listed ahead of non-critical and change-request problems (when we have them). It also drops out items that have been completely closed. It links to the full history, even though there is no difference at the moment.
3. The home page for ODMA Support is updated to link to the active-incident page, and the complete list of incidents. The text about support coverage is updated and the marquee is updated for ODMA Summer Bug Hunt 2000. A bug-hunt paragraph is added following the status-summary table.
4. Other pages with marquees or announcements about recent ODMA incident reports are reviewed and updated with the Summer Bug Hunt announcement: the ODMA home page, the InfoNuovo entrance page, and the DMware entrance page are updated .

2000-06-23-08:58 Expand X000600 Component List (orcmid): 1. The ODMA 2.0 SDK 2.0.0 is added as the key component for this incident. The component list is hyperlinked to the appropriate places in the download section.
2. For this update, I added a change element at the bottom of the form itself, rather than linking to here. This practice will be expanded so that pages which will be mirrored on dmware.org will not depend on links to construction information on infonuovo.com. Also, when material is downloaded or archived for download, this will cut down on external dependencies that show up as broken links in an user's file system.
2000-06-22-22:22 Update X000600 Materials (orcmid): Based on tests conducted under Windows 98, I have come up with the information needed to further explore this incident.
1. The message is added as page X000600C, identified as the Investigation Request.
2. The Investigation Request is linked as a response from X000600B, the Initial Acknowledgment, and X000600A, the Initial Report.
3. Page X000600A is also modified so that link colors are not automatic, but fixed, as for all material here.
4. Page X000600 is modified to reflect this degree of progress.
2000-06-22-20:42 Tidy up X000500Z for use with X000600 Report (orcmid): Although the note from Clay Gibney was in response to another investigation, I want it on the system in support of X000600. I have provisionally given it identification X000500Z.htm, though it may move when the other material for other problems is caught up on the Web site. In rereading this, I see we have cause to place another report against ODMA32.DLL concerning the ability to operate the log.
1. The note is put in the same format used for X000500A, although the name of the page and the problem it supports can change.
2. I have to figure out how to thread this into two or more separate incidents. Not today.
2000-06-22-14:40 Create New X000600 Incident and Supporting Material (orcmid): Clay Gibney reported that he had seen the test fixtures fail, and would look at that again. Almost concurrently, S. Ramananthan reported a specific instance of ODMA test fixture failure. I responded and began setting up the investigation.
1. The incident report is set up with the initially-known information.
2. The original comments from Clay are stored in a provisional location as part of work on the earlier problem. (This will be integrated in the trouble-shooting for incident X000500.)
3. Ramananthan's original report is catalogued as part of the Web background material. This report is in an edited HTML format. For purposes of authentication and verification, the Microsoft Outlook message format that was originally received is linked as an attachment to the HTML version.
4. This is being done manually as practice in organizing incident coverage material in a systematic and accountable manner. The intention is to automate as much of this as possible once a reliable and usable mechanism is developed.
2000-06-19-15:45 Begin and refine Draft of WordPerfect Trouble-Shooting Information (orcmid): To continue investigation of problem X000500 and any similar ones that arise, new material is added so that people can create and interpret logs on WordPerfect use of ODMA.
1. Q000600 is created for general WordPerfect-ODMA Troubleshooting. Links to deja.com are verified.
2. The structure for WordPerfect Trouble-Shooting is completed, but some details require more work. As part of researching the material, I generate two workaround ideas and see the need to start collecting separate related tips, such as helping people to make sure they have the latest version.
3. The odma32.dll is added to the ODMA download page in anticipation of reference from needed tips.
4. I name Q000600 a FAQtip, and begin the FAQtip page. The FAQtips are identified just like incident reports, but with prefix Q instead of X.
5. 2000-06-24: The FAQtips are moved to a separate section for organization there.

2000-06-19-15:20 Correct Support Coverage Broken Links (orcmid): The Support Approach and Statement of Work pages are checked for broken internal shortcuts as the result of recent editing.
1. One shortcut in the table of content of the Support Approach page is corrected to reach the renamed target paragraph.
2. Find and correct 3 shortcuts in the Statement of Work table of content. Note that interior subsections, though numbered in the body, are not reflected in the table of content, which is also an image of the Statement of Work.
2000-06-19-14:07 Cleanup of New Support Coverage Material (orcmid): The revised support materials were reviewed on-line and defects repaired:
1. The home page expression about "organizing farther" is replaced with "expanded". The similar expression on the support page is also corrected.
2. A damaged Support Approach paragraph, Every Question Matters, couldn't be recovered from an earlier Visual Source Safe revision -- I didn't do precautionary check-ins often enough and needed to re-invent an appropriate statement.
3. The sections of the Support Approach document are numbered to provide better cues to location and context. The table of content is made an accurate mirror of the sections, including subsections 3.1-3.2.
4. In the Statement of Work, every item in the body is giving a date so that chronological progression can be traced as further changes and expansion of support are accounted for. The term "test DMware site" is used to refer to the DMware material that is created at http://www.infonuovo.com before publication on the official AIIM DMware site.
2000-06-19-08:51 Expand Support Coverage (orcmid): The DMware site will have a consistent, consolidate Support and Support Coverage information. At the moment, ODMA is where the action is, and users are reporting and dealing with urgent ODMA support issues. I am going to develop the DMware Support materials here first. This provides an active laboratory for perfecting the support model while also being responsive to where the action is.
1. Created ODMA Support page, support.htm. This provides a sketch of the Support model and the related policies. This can be woven into the FAQ page(s) as they are established.
2. The Year 2000 Statement of Work for ODMA Support is published as part of the section.
3. The ODMA Support home page is updated to link the approach definition.

2000-06-16-08:16 Tweak Incident X00500 Report (orcmid): 1. As noticed in establishing the new ODMA Support section, the title of the page used by browsers was changed to "ODMA Critical Problem Report X000500" and the date removed from the title. This reflects the new incident-report identification system.
2. The time zone in the last-updated entry is corrected, and the link changed to reference this entry.
3. The Importance field is renamed "Category" and the Source Forge "Fatal Error" category adopted for this category (which is still also named "Critical."). Any category involving damage to data or failure to operate is automatically declared Critical.
4. The Priority field is augmented by the Source Forge Priority Level value. In this case, level 9 to reflect the urgency and criticality of the situation.
5. Worldox is added to the list of DMS integrations that fail under the conditions being reported. Some wording adjustments are made to the summary.
2000-06-15-15:33 Change Status Section to be Support Sub-Project (orcmid): The status section is renamed to be the support section. Adjustments are made for further changes and additions.
1. The title block of this construction page is corrected. All links on this page are inspected: The tombstone to an old name for the current problem report is left in the old status section only.
2. The tombstone that was cloned from the status section to this new support section is deleted since its url was never published. (It is deleted from the VServers image under VSS also.)
3. On the home page, the name is changed to ODMA Support in the title block. The InfoNuovo and Hard Hat images are deleted and the background is changed to white, reflecting this being production content. All links on the page are reviewed for correctness in the new context. No links need to change. The "Last Updated" entry is made into a hyperlink to the current change history entry.
4. The index.htm page is updated to change the name from "status" to "support" everywhere. The title of the page is also corrected, and wordings are adjusted to reflect the new r�le. All links are found to be fine.
5. The only incident report so far, X000500.htm was checked for validity in this new context. A small defect was noticed, but its remedy (the title of the page) delayed until the page is updated with more substantial information.
6. The section was declared clean enough for correct referencing from the now-defunct status area and also from anywhere in the DMware web that it might have been referenced.
2000-05-29-19:03 Adjust Incident Report Format Further (orcmid): The format for incident reports (the phrase that I will now use) is adjusted further to reflect the version of component against which an incident is reported, as well as the version in which any repair occurs.
1. The last-updated entry is now linked to the change history/log entry that describes the actual changes.
2. The title is changed to ODMA Incident Report
3. The Version of the Component is identified
4. The Workaround field is replaced by a "Repaired In" field for identifying the component with the repair and the version of that component.
5. The dates are moved to the bottom of the form block and the top of the form block is rearranged to have the key information close to the top.
6. For the specific X000500 incident report, the title is improved and there are some wording improvements in the summary.

2000-05-27-08: Update Critical Problem Report Format (orcmid): The format for problem report files was updated to reflect a simpler naming scheme that stays within 8.3 filename structure.
1. The file 20000509.htm was renamed to X000500.htm, initiating the new system.
2. The original 20000509.htm file was checked back in from the VServer upload/mirror area and used to record a tombstone for the earlier version of the file. 2000-06-15: This original file is retained only in the status section where it is left as part of all of the tombstones.
3. The "Last Updated" entry at the top of pages is modified to show the time zone and offset of local time from GMT, so that people won't be so surprised to see change dates that are later than the local time from which the page is being accessed.
4. "Component" and "Incident ID" fields are added to the form for incident reports.

2000-05-17-22:44 Manually Enter Critical Problem Report Document (orcmid): A problem-report form is created manually in order to expedite recording and reference to this problem. At some point, a problem reporting system with electronic forms will be used to receive and track problems for material in the DMware clearinghouse. For now, the few problems that are reported will be documented manually.
1. The basic form is created and linked from the status page.
2. The marquee with the problem alert is tested and a simple side-to-side version is chosen to be used everywhere the alert is given.
2000-05-17-18:22 Add Critical Problem Information and Clean-Up Structure (orcmid): 1. Corrected the shortcuts from the table of contents to the body of the status page.
2. Added a marquee and notification of the March 9 critical problem report. There is no problem report text itself yet.
2000-05-17-12:52 Create odma/status Project & Construction Log (orcmid): 1. The odma downloads area is created to provide and archive ongoing status information about ODMA.; 2. I established an index.htm and this construction.log to provide the initial construction structure.
3. The initial content consists of a default.htm that provides a summary of overall status information, with extended details to be introduced by linking to supplementary pages.
4. This material was cloned by copying the construction pages from odma/downloads. In the course of customizing that boilerplate, an error in the wording of the odma/downloads construction log was caught and repaired.

/odma/support Construction Log

Change History

/odma/support
Construction Log