ODMA Project

 P010200: Bring ODMA Incident Reports Current

Last updated 2002-06-04-16:12 -0700 (pdt)
The latest version of this information is available on the AIIM DMware ODMA site.

Type: ODMA Support Project ID: P010200
Style: Ad hoc Status: Underway
Objective: 
1. Have all logged incidents reflected by reports.
2. Have all new logged incidents reflected. 
Note: It is not the objective of this project to resolve all incidents.  It is to have them all documented.
Related information/projects:
ODMA Incident Log
ODMA 2.0 Specification Errata
P000800: Capture All ODMA Questions and Problem Reports as FAQ and Incidents
P000701: ODMA Specification Errata
Assigned To: Dennis Hamilton Defined By: 
Dennis Hamilton (2001-03-01)
Date Opened: 2001-02-27 Date Completed: none

1. Requirements (2001-02-27):

Rank the known ODMA incidents and organize the creation of supporting reports, using the following prioritization scheme:

2. Activities (2001-02-27)

2.1 Incidents Involving ODMA Integrations
2.2 Incidents Impacting the ODMA Documentation Set
2.3 Incidents Impacting ODMA Development Libraries
2.4 Incidents Impacting ODMA Connection Managers
2.5 Miscellaneous Incidents and Enhancement Requests

The purpose of these activities is to have each logged incident supported by a report that describes the incident in more detail, and provides for expansion with investigation, ways of reproducing/confirming the incident, and any workarounds and resolution that becomes available.  

These activities do not involve closing the incident.  It is having the incident itself better known and documented.  The closing of the incident backlog is a second project.

The grouping reflects the relative importance to users of ODMA systems, followed by ones impacting developers.

All new incidents that are logged after this project starts always have reports filed immediately.

The assigned dates for the incident being reported are based on a rate of approximately one report per day.   This allows for new activities and other projects to continue in parallel.

2.1 Incidents Involving ODMA Integrations

Problems with ODMA integrations are ones that impact users of ODMA applications and DMS components.  These are incidents that impact the reliable usage of ODMA in operational settings.

Those incidents already logged are to be recorded first, so that those impacted by these incidents can contribute to trouble-shooting, and others can check to see if they are experiencing the same or different incident.

ID

Report By Actual

Component

STATUS

Summary Title

X001000 2001-03-03 2001-03-02 ODMA Integration Fatal Error: Critical Microsoft Word 2000 Save Failure
X000200 2001-03-13 2001-03-04 ODMA Integration Fatal Error: Critical (escalated 2001-03-04) Microsoft Office on Win98 & NT
X000100 2001-03-04 2001-03-04 ODMA32.dll 2.0.0 and ODMASAMP 2.0.0 Fatal Error: Critical ODMASAMP with Word on NT
X000011 2001-03-05 2001-03-05 ODMA 2.0 Connection Managers Fatal Error: Critical Trace Logging Failure
X010200 2001-03-09   ODMA Integration Functionality: Defect WordPerfect Invalid ODM_E_DOCID Recovery
X000300 2001-03-12   ODMA Integration Integration: Warning Problems with Dialog Boxes Resulting from ODMA Calls
X000101 2001-03-14   ODMA Integration Integration: Warning GroupWise ODMA Integration Troubleshooting
X000008 2001-03-15   ODMA Integration Integration: Warning Microsoft Office Consistency of DMS Dialogs from different places files are accessed in applications
X000005 2001-03-18   ODMA Interoperability and ODMClose Integration: Warning Deletion of working files in ODMClose.
X000004 2001-03-19   ODMA Interoperability Integration: Warning Adobe PDF Writer failing to print opened ODMA Documents

2.2 Incidents Impacting the ODMA Documentation Set

Incidents involving the ODMA Documentation Set must be reported so that the provision of a stable documentation library can be established.  In addition, the accuracy of the specification is critical to the arbitration and resolution of other incidents involving development and implementation of the ODMA Connection Managers.

ID

Report By Actual

Component

STATUS

Summary Title

X001001 2001-03-20   ODMA 2.0 Specification Specification: Precision ODMRegisterApp ODMSTATUS Ill-defined

2.3 Incidents Impacting ODMA Development Libraries

Accurate, complete development libraries are critical to the confident creation of ODMA-compliant components by the development community.  

ID

Report By Actual

Component

STATUS

Summary Title

X000009 2001-03-06 2001-03-06 Odma.h 2.0.0 Functionality: Critical Incorrect ODMOpenDoc ODM_REFCOPY Flag
X000301 2001-03-10   Odma.h and ODMA Constant Values Functionality: Defect Constant Definitions Managed Improperly
X000002 2001-03-11 2001-05-11 Odma.h 2.0.0 Functionality: Defect ODMA Error Codes Missing in Odma.h 
X001200 2001-03-25   ODMA 2.0 Library Interoperability: Warning Unsafe Interface ID Values
X000102 2001-03-26   ODMA Samples Vulnerability: Warning Problems Rebuilding Sample Code
X000007 2001-03-27   ODMA 1.5 SDK conman.h Packaging: Warning Misleading inclusion of conman.h with other headers missing

2.4 Incidents Impacting ODMA Connection Managers

Having clear understanding of the incidents that arise with Connection Managers, and being able to tell if they arise in practice, is also critical to the development and the application communities having confidence in the reliability of the critical ODMA middleware.

ID

Report By Actual

Component

STATUS

Summary Title

X000010 2001-03-07 2001-03-06 ODMA 1.5 and 2.0 Connection Managers Fatal Error: Critical ODMQueryGetResults Buffer Handling
X000006 2001-03-08 2001-03-09 ODMA32.dll 2.0.0 crash using ODMA 1.5 DMS Fatal Error: Critical ODMQueryCapability Crash
X000809 2001-03-28   ODMRegisterApp and ODMGetODMInterface beyond ODMA version 1.0  Functionality: Warning Down-level version support not implemented.
X000808 2001-03-29   ODMRegisterApp in all versions of Odma.dll and ODMA32.dll Functionality: Warning ODMRegisterApp Filters version incorrectly.

X000805

2001-03-30   Odma.dll and ODMA32.dll, all versions Interoperability: Warning Connection Manager does not adjust to code-page in use.
X000804 2001-03-31   Odma.dll and ODMA32.dll, all versions Interoperability: Warning Connection Manager depends on non-Standard string function stricmp

X000803

2001-04-01   Odma.dll, ODMA32.dll, and ODMA Specification Inconsistency: Warning Inconsistent Treatment of "Null" Document IDs and other string parameters

2.5 Miscellaneous Incidents and Enhancement Requests

These incidents are generally about activities that were underway at some point,  or have been requested.  The additional utility may be clear, and there may already be new activity in these areas.  However, in terms of the urgency of reporting, these items are not so urgent as ones involving potential defects, problems, and misunderstandings.

ID

Report By Actual

Component

STATUS

Summary Title

X000012 2001-04-02   ODMA Connection Managers Feature Request: Usability Manage Configuration without Manual Registry Manipulation
X000003 2001-04-03   ODMA Specification Feature Request Multibyte Character-Encoding Support
X000001 2001-04-04   supplemental Feature Request Visual Basic Friendly ActiveX Control for ODMA Access
X000000 2001-04-05   ODMA32.dll and ODMA specification DMS Interface and Installation Feature Request Building DMS Integration using Visual Basic

created 2001-02-27-13:11 -0800 (pst) by orcmid
$$Author: Orcmid $
$$Date: 04-11-18 14:16 $
$$Revision: 15 $