WHITEMARSH METABASE SOFTWARE SYSTEM Installation Process Warning -- READ THIS.. Really, READ THIS. It is STRONGLY advised that you read the Getting Started Guide to properly install the Metabase system and the DBMS Mimer. We recommend that you install the Metabase system first, then Mimer. After Mimer is installed, the Mimer ODBC administrator is left open. The Mimer website is www.mimer.com. You MUST then make the ODBC connections between the three Mimer databases and ODBC. These databases are: mbsysdb, Movies, and metabase. The COMPLETE intall contains the Mimer databases, MbSysDb, Movies, and Metabase. This install will overwrite these any existing Mimer databases. To keep an existing Mimer database, stop the server for that database, make copies of the dbf files, run the install script, copy back the dbf files, then re-start the server for that Mimer database. The PARTIAL install will ONLY overwrite the EXE files for the Metabase System and will ONLY overwrite the DLLs and other files that are required for the EXE files. Unless and until you make the ODBC connections you will get ERRORS from the Metabase functional modules (e.g., Business Information Systems) because the Metabbase functional module will NOT know where to go to get the data. The errors will be "File missing errors." STRATEGY TO KEEP YOUR DBF FILES. --- THIS APPLIES TO THE V6.9.5 VERSION If you are installing OVER an existing metabase system and you do NOT want to wipe out existing metabase databases, for example, MbSysDb, or Movies, or Metabase, then DO NOT STOP THE MIMER SERVER. This will cause ERROR messages in the Uninstall Process when the Uninstaller tries to delete the Mimer dbf files. THIS IS GOOD. Just press "Continue." At the end, all the dbf files will still be there. This only applies to a V6.9.5 version and the V6.9.6 Partial version. This has been fixed in the 6.9.6 FULL download version because the Full 6.9.6 and newer versions will NOT try to delete the Mimer dbf files. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Version History ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Version 6.9.8.5 (32Bit) 06/21/2008 This version fixes a number of small bugs that were discovered while writing the Data Semantics Management book. As bugs were found, messages were sent to Metabase users via the Whitemarsh Forum (access the forum from the front page of the Whitemarsh website). This version 6.9.8.5 is just a "refresh" of all those changes. This version consists of a complete install of all files. AND A Partial install of JUST the EXE files WARNING..... The demo files have been converted to run under Mimer 9.3.8 Version. These databases will NOT run under the Mimer 9.2.4 vesion.... You MUST upgrade to the NEW Mimer version, 9.3.8. You can do that by accessing the Mimer website at www.mimer.com then proceed to the download page for the new Mimer Version. If you want to KEEP your old version of Mimer and your existing demo files then JUST install the "partial" install. Version 6.9.8 (32Bit) 03/10/2008 This version fixes a number of small bugs that have been noticed while writing the Data Semantics Management book. These have been fixed. Some windows have also been changed to make the purpose of the process more explicit. We also noticed that an index in the Database Object Module was UNIQUE when it should have been NON-unique. The UNIQUE state of the index caused an error when adding an second record of data was being added to the Database Object Information System State table under a certain condition. To eliminate this potential error, a new metabase module, Convert Version 060907 to 060908 has been included. When you run this application, 1) select a Metabase Database, e.g., Metabase or Movies, and then 2) select the menu choice for conversion. 3) press the conversion button. It will 1) drop the old index, and 2) install a new index without the UNIQUE attribute. The new version of Mimer, 7.3.8 was installed. It seems to run OK against Metabase database data. It does, however REQUIRE a conversion of the specific databases (e.g., MbSysDb, Movies, and Metabase). This is shown by a "green up-arrow" next to the database name in the Mimer Administrator Module. Just right mouse-click the symbol and it will upgrade the database just fine. Version 6.9.7 (32Bit) 02/19/2008 There are just a few things fixed in this interim release. These all relate to the importing of SQL DDL into the Specified and Implemented Data Models. There has been no other significant changes. Version 6.9.6 (32Bit) 12/09/2007 There are four items in this interim release. These are: 1. Now lists, item by type and name the components that prevents another component from being deleted because of a Referential Integrity Constraint. E.g. Table has columns. Delete Table? NO, because it has columns... This now lists the names of the columns. This change has been implemented in 8 different places. 2. AutoDef now works on lists of attributes, columns, and DBMS Columns. E.g. Select Table and press AutoDef and all the columns in that table are automagically defined. The automagical definition includes a local definition as well. 3. There is now a easy way to synchronize the allocation of an ISO 11179 Data Element to Attributes and Columns. An ISO 11179 Data Element can be the parent to both an Attribute and a Column. An Attribute is the parent to a Column. Hence a Triangle, and hence ambiguity. This change enables you to get rid of the ambiguity. The Synchronize window is under reengineering in the Implemented Data Model. 4. You can now synchronize the local definitions for a given column across different tables and across different schemas. Same for Attributes of Entities, and DBMS Columns of DBMS Tables. These three screens are under the SDM, IDM, and ODM Reengineering main menu then Synchronize Definitions. Version 6.9.5 (32Bit) 11/01/2007 There is not spell checking for every description and name field in the metabase. Press F8 to activate. There is now comprehensive Abbreviation Management. This is managed in the Adminstrators Module. Abbreviation are accomplished in the Operational Data Model DBMS Column screen. You can import abbreviation files, and segregate abbreviations by business domain. You can also move one abbreviation from one business domain to another. You can now do a Reverse-Abbreviation on a DBMS Column By DBMS column basis. If you import SQL DDL to the Specified and Implemented data models, the Reverse- Abbreviation is implemented there as well. A comprehensive AutoDefinition facility has been added to Entities, Tables, and DBMS Table, and also to Data Elements, Attributes, Columns, and DBMS Columns. You can add your local definition phrase. When the AutoDef button is pressed, the metabase gathers definitions from all contextually related metadata to construct a comprehensive definition. ________________________________________ Version 6.9.1.1 (32Bit) 03/10/2007 There was a reported bug in the metabase once both the metabase and the DBMS, Mimer are installed. Once a metabase application is executed, a "Prop:SQL" error is posted to the screen as a background message window. Just click OK on this message. No harm seems to have been done. This problem was resolved and a new demo, 6.9.1.1 was posted. ________________________________________ Version 6.9.1 (32Bit) 01/16/2007 Remember to backup your data. Please consult the website, www.wiscorp.com for a complete description of the Whitemarsh Metabase Software Product line as well other WISCORP information. The website contains a larger release notes, and the very critical Metabase meta model diagrams. Metabase's Getting Started Guide can be found here: http://www.wiscorp.com/metabase ________________________________________ #### METABASE VERSION INFORMATION #### ________________________________________ [01/16/2007] NOTE: [v06.9.1.0 release] Several bug fixes were accomplished related to the automatic generation of Clarion Data Types. Buttons were installed that allow users to "clear" DDL output files during SQL and Clarion DDL generation. Clone data model menu items were installed in the Implemented Data Model and also the Operational Data Model Import Menu items. Finally, a menu item was created for generating the Clarion DDL for a single table. [12/01/2006] NOTE: [v06.9.0.1 release] Three column names and 11 key names have been shortened to be less than 32 characters so that the schema can be read by Oracle. [11/13/2006] NOTE: [v06.9.0.0 release] The key change in this version of the metabase is the inclusion of two columns in every single file recursion and bill-of-materials tables. This support a more explict printing of hierarchies and network structures through ODBC based report writers such as Crystal Reports. All the Crystal Reports "rpt" files have been updated and posted to the Whitemarsh metabase website. There has also been an large quantity of small changes for display and the like. A second Metabase, Metabase2 is installed other than Movies. This metabase consists of default data, data type data, and also commnonly used reference data that will greatly ease the immediate, out-of-the-box use of the metabase. A conversion program has been created for moving existing metabase databases. Check out the "docs" directory for the conversion guide. If you are merely replacing the the existing "Demo" database then that metabase database does not have to be converted. All production class metabase databases need to be converted. [03/23/2006] NOTE: [v06.8c2 release] The current View Data Model (mbdmvdm.exe) structure is missing an expected default data record for view column structure process. To remedy this, merely insert the standard VCStPr record with the name= 'Unknown', and description = 'Unknown' and the RI error reported for VCS inserts will cease. ****** Metabase v06.8c2 Version ***** [02/02/2006] --Fixed display error in Concepts Structures's bill-of-materials (implosion) description field. ****** Metabase v06.8c Version ***** [01/11/2006] --Enhanced Admin Login procedures --Added support for two more PRIMARY KEY statements when importing SQL in SDM, IDM & ODM modules. e.g.: CREATE TABLE hotel. (hotelID integer not null, name CHAR(128) not null, city CHAR(128) not null, PRIMARY KEY (hotelID) ); -- or -- CREATE TABLE MOVIE_COPY2 (MOVIE_COPY_NUMBER2 INTEGER PRIMARY KEY, GENERAL_CONDITION_ID INTEGER ); -- Changed the structure of four DCT items: To update your 0608b version of the Metabase to this new structure, get the SQL statements from: www.wiscorp.com/update_metabase_ddl_6.8b_to_6.8c.txt ****** Metabase v06.8b Version ***** [11/01/2005] --Fixed faulty Select Mission window in MOFPA's Database Domain Update. --Fixed explode/collapse buttons on MOFPA Reallocate Missions window. ****** Metabase v06.8 Version ***** [09/28/2005] --Added Users and Password protection to access datasets for specific Metabase Software modules. Default for Demo software is username='sysadm' and password='sysadm' --Added more complete description display boxes in many windows --Added Confirm-on-delete on Tagging windows for bridge tables. --Greatly simplified the install of the Demo Software. No longer having to create Mimer databanks and load the schema and bootstrap data, the demo software can now be set up in three basic steps. 1. Install Mimer SQL Engine DBMS. 2. Install Metabase Software System. 3. Create ODBC DSNs for the three example databanks. [mbsysdb, movies, and a blank metabase] Done! See the Metabase_Getting_Started_Guide_v6.8.zip [ www.wiscorp.com/metabase/ ] that has the only steps needed to begin using the Metabase Software System. --Metabase manuals have all been redone with new screen shots and updated to show the latest functionality. ****** Metabase v06.7 Version ***** [07/07/2005] --Incorporated use of Microsoft Word via OLE to do Spell Checking. MS Word Must be installed for this feature to work. --Added separate description windows for record browses. --Modified work flow model on some windows, based on user feedback. --Internally, broke down some of the various routines, and added two new DLL's to the Metabase's components. --Made presentation changes to various Metabase modules, including adding description boxes to most of the reference data windows. ****** Metabase v06.6b Version ***** [04/20/2005] --updated MbSysDB.ddl file (readded a missing table needed for login.) --Made minor presentation changes to various Metabase modules. ****** Metabase v06.6a Version ***** [04/14/2005] --Bug fixes in admin --RLC, BIS, DBO browse enhancements ****** Metabase v06.6 Version ***** [04/03/2005] --Added additional re-allocation functions for meta-category value and meta-category value type. --Put in an automated process that synchronizes a column's data element to be the same data element as that of the column's attribute. --Put in an automated process that synchronizes DBMS Column's datatype's properties, specifically the Length/Precision and the Scale fields, with the DBMS Column's datatype. --When we Import an Entity from SDM as a table in IDM, if the Attribute has a Data Element, then the system makes the Column's data type the same as the Data Element's data type. If there are multiple SQL Data Types then the system picks the one most likely to be chosen... Character vs VarChar, etc... --Put in an absolute Column to Data Element, Attribute to Data Element, and Column to Attribute Re-assignment override switch. --SQL Generator: several small changes, enhancing the SQL DDL output. --Created in SDM, IDM, and ODM a process to re-set Foreign Key's Column names to that of the Primary Key's Column names. --Create the Metabase Reverse and Forward Engineering Guide. --Begun the process of updating all the metabase user guides to use the Movies database example. Check back monthly for updated user guides. --Found and fixed SQL DDL loading bugs in SDM and IDM modules. ****** Metabase v06.5 Version ***** [01/15/2005] -- fixed admin module's path bug - new install created [01/05/2005] --All MB modules were redone with Clarion v6.1 (softvelocity.com) --NOTE: mbsysdb SYSADM password is now "sysadm" You must stop, delete, and re-create the mbsysdb databank. The mbsysdb.ddl script is in the /DOCS folder, of your MB installtion. --NOTE: For those upgrading from v6.03 there are two small table structure changes, see version_changes.ddl in the /DOCS folder. --Supports Mimer 9.2.2G DBMS (www.mimer.com) --Fixed MDI window startup bug. --Improvements to data modeling & re-engineering windows. ****** Metabase v06.03d Version ***** [11/19/2004] --Fixed (re)select new Dataset display error. ****** Metabase v06.03c2 Version ***** [11/15/2004] The mbsysdb.ddl file had an error in the script. The first line read: CREATE DATABANK SYSADM ; it SHOULD have read: CREATE DATABANK MBSYSDB ; To fix the error 90 that occurs at runtime run the following statements, after logging into the mbsysdb with an ODBC client: This will replace the LIMIT table with a properly defined structure. -- start ddl DROP TABLE LIMIT ; CREATE TABLE LIMIT( MBCLIENTNUM CHARACTER(255), MBDATE DATE DEFAULT CURRENT_DATE, MBTIME TIME DEFAULT LOCALTIME(0) ) ; ALTER TABLE LIMIT ADD CONSTRAINT LIMITPKEY PRIMARY KEY (MBCLIENTNUM) ; -- end ddl ****** Metabase v06.03c Version ***** [11/09/2004] -- Max Concurrent User Lockout bug fix for certain hard drive types -- Added wait event to reduce exe opening related MDI window error ****** Metabase v06.03b Version ***** [11/02/2004] -- Connect string error on table - ConValDomS and ConValDomST ****** Metabase v06.03 Version ***** [10/29/2004] -- This release included internal version upgrades. Several bugs have been fixed as well: e.g. ConValDomS, MCVDEC assignment, etc. ******Metabase v06.02***** [09/15/2004] -- This release will be to reflect a set of internal changes that will increase the performance of the metabase. ******Metabase v06.01***** [06/25/2004] -- AUTOPOPULATION OF DATA TYPES-- 1. On Import SDM to IDM, for each attribute, the metabase gets the attribute's data element, then gets the data element's value domain data type, then loops through the related SQL data types for that value domain data type. If there is a name match, then that SQL data type is the default data type for the newly created column. Otherwise, the last SQL data type that is related to the value domain data type is the default data type for the column 2. On import IDM to ODM, for each column, the metabase gets the column's SQL data type. Then, for the particular DBMS for the operational database data model, it loops through the related DBMS data types for that SQL data type. If there is a name match, then that DBMS data type is the default data type for the newly created DBMS column. Otherwise, the last DBMS data type that is related to the value domain data type is the default data type for the column 3. On the Generation of Clarion TXD, a) auto generate prefix (that's already there), and b) autogenerate a Clarion compatible data type. If the DBMS column already has a parent Column then the metabase will attempt to find the appropriate Clarion data type. If there is more than one possible choice then the software picks the first one. This clearly is not perfect, so you need to check. 4. Concurrent Users. The multiple user version of the metabase supports specific quantity of users. Users do not have to be named. The software merely checks to see that the maximum quantity of users or less are currently using the metabase. There is no maximum quantity of Crystal Reports users. Nor is there any maximum to the users given that the access is direcly to metabase instances through ODBC connections. ******Metabase v06.00b ***** [04/09/2004] -- Removed valdomdtid from SQLDATATYPEUNIQUEKEY and renamed the constraint to SQLDATATYPENAMEKEY. Run these two statements to alter each current Metabase dataset. ALTER TABLE SQLDT DROP CONSTRAINT SQLDATATYPEUNIQUEKEY ; ALTER TABLE SQLDT ADD CONSTRAINT SQLDATATYPENAMEKEY UNIQUE(MBNAME) ; ******Metabase v06.00***** [03/01/2004] --Implemented with Mimer SQL Engine 9.x DBMS backend (www.mimer.com) via ODBC. --Improved interface --Improved import/export capability --Too many changes to list... ******Metabase v05.08b***** [07/16/2003] --made improvements to Fkey update procedures autonaming routines in SDM, IDM, & ODM. ******Metabase v05.08***** [06/04/2003] --fixed the SQL DDL loader so that it will load without having to have an On Update or an On Delete subclause --separated precision and scale in all the data types --made it obvious that you can move entities from one subject to the next --enabled the use of role names so that "duplicate" foreign keys can exist from the same primary key table --improved the ability to automatically transform one data type to another between IDM and ODM --completed the ability to import just one column from an IDM table into an ODM DBMS Table --reengineered the Pkey select screens when making a foreign key ******Metabase v05.07f***** [04/15/2003] --fixed a browse display error in the database objects module. --in the specified dat model module, added the capability to make a subtyped entity a root entity including the automatic creation of a primary key and it's column --ditto for implemented data model module with subtyped tables --ditto for the operational data model module with DBMS subtyped tables ******Metabase v05.07e.1***** [03/26/2003] --fixed err48 on VDM module. ******Metabase v05.07e***** [03/19/2003] --Candidate Key changes to three tables. --make improvements to resource/restype update windows --fix to update/browse mbuser --Removed Transaction Control Framing (err48) from RLC module. --Added Promote only One DBMS table to IDM. --Added the ability to remove connection between IDM table column set and the corresponding ODM table column set. This greatly helps in data model re- engineering efforts. --Added the ability to remove connection between SDM table column set and the corresponding IDM table column set. This greatly helps in data model re- engineering efforts. --Added a direct Primary and Foreign key connection between Value Domain Data types and SQL Datatypes and DBMS Datatypes. Added browse windows that show the precise data type mapping. --Added facilities for automatic creation of data types in promotion (e.g., ODM to IDM) processes. --Added facility that automatically chooses the first valid data type in any importing process (e.g., IDM to ODM) --Added facility that exports the complete set of data types so that they can be re-used within different metabase instances. ******Metabase v05.07d***** [02/12/2003] --RLC - Changed Resource Lifecycle Node Database Schema to Resource Lifecycle Node Database Object Assignment. --SDM, IDM, ODM - Import SQL DDL procedures have increased accuracy, and newly added error logs to store DDL errors. --Auto Creation (importation) of both DBMS and ANSI SQL datatypes in the IDM and ODM --Auto Creation of a complete set of default data --The Operational Data Model module now supports the import and export of [unique] INDEXes when reading and writing SQL DDL. --Added six Re-engineering windows to Database Objects --Small fix in multiple modules disallowing the creation of orphan single file hierarchy records by using key- board shortcuts. --Small change that reenables the auto update feature for changing data file's structures, on the fly. --Removed ability to start a new data set from the main MB app. The Admin module now creates all new data sets and mandatory default data. --Increased support for ANSI standards by Name Length changes on all identifiers to 128 characters in the DCT. --In the ODM module, removed the DBMS Column Picture attribute from DBMSColumn table, and added DBMS Data Type Picture table as a parent table (fkey) to DBMS Datatype. A Data Type Picture for a given DBMS Datatype in a Clarion DBMS environment allows for global setting of Clarion Pictures, aiding the auto generation of Clarion TXD. --Some users (particularly at lower video monitor resolutions) may experience hidden portions of metabase windows or (conceivably) a completely hidden window. Upon closing the various Metabase windows, the coordinates of the various Metabase windows are stored in a file in the "C:\Windows\" directory. The file that is written to is the metabase.ini. If a metabase window has changed size, it may be that a portion of the window (after an upgrade) now is off the screen, or obscured by another window. Either delete the file (the quickest way) or correct the errant window's entry values. ******Metabase v05.06***** [08/23/2002] --IDM - created a "Create many Columns" feature that allows the user to assign a Data Element to one or more Tables. --SDM - created a "Create many Attributes" feature that allows the user to assign a Data Element to one or more Entities. --IDM - created a feature to manufacture a "Trivial" primary key for a newly created Table. This is accomplished by: 1) Auto creating a Column using the form: + "ID" 2) Creating a PrimaryKey using the form: + "Pkey". 3) Finally, assigning the newly created column to that Table's primary key. --SDM - created a feature to manufacture a "Trivial" primary key for a newly created Entity. This is accomplished by: 1) Auto creating an Attribute using the form: + "ID" 2) Creating a PrimaryKey using the form: + "Pkey". 3) Finally, assigning the newly created Attribute to that Entity's primary key. --DBO: In the non-demo version of the Metabase, fixed "Build" button in Database Objects Table creation window. ******Metabase v05.05***** [08/09/2002] --The main addition to V0505 is the ability to generate a Clarion TXD. The TXD file is in ASCII so you can read it. If you are a Clarion user you can then directly create a database design with it and the generate the application directly. --If you are not a Clarion user you might want to consider buying Clarion. The Professional Edition is reasonably priced and with it you can then really see your database designs in action. That is, through the generated application. --To make the TXD two columns had to be added to the DBMS Column table. These were: PICTURE and Prefix. A picture in Clarion provides presentation layer formatting for numbers, dates, strings and the like. The Prefix provides the method of disambiguating same named columns from different tables, such as Per:FirstName from Emp:FirstName. --Another item added to V0505 is a button on the Columns (maintenance) screen and the DBMS Columns (maintenance) screen. This new button, Refresh, causes the data type, length, picture (for Clarion) and quantity of decimals to be synchronized between columns of a primary key and columns of a foreign key. --When you import an IDM data model into the ODM the data types are set to Unknown as the ANSI SQL Data type may not be the same as a DBMS data type. Thus you have to set them. So, by setting data type, length, picture (for Clarion) and quantity of decimals for the Pkey columns you can implicitly set them also for the Fkey columns. So, after setting these properties for the pkey columns and for all the other columns, then press the Refresh button to have them set for all the Fkey columns. ******Metabase v05.04***** [06/15/2002] --Added to IDM the ability to copy in a complete SDM subject-based entity set --Added to ODM the ability to copy in a complete IDM schema-based entity set --Added the ability to import just attribute from SDM to an IDM table --Added the ability to import just one column from IDM to an ODM table --Added the ability to import multiple SDM trees into an IDM schema. --Added to SDM the ability to import SQL DDL --Added to IDM the ability to import SQL DDL --Added to ODM the ability to import SQL DDL --Fixed errors in the Tree-display of data models (data was Ok, the display was bad) --Fixed errors in the assignment of meta category values. It broke when we changed to conform to ISO 11179. ******Metabase v05.03b***** [04/29/2002] --Found and fixed errors im the importing of unrelated specified data model tables. --Found and fixed an error in the creating of foreign key names. ******Metabase v05.03***** [04/19/2002] --Finished the work to manage sub-typed entities,subtype tables, and sub-type DBMS tables. --Finished creating the ability to generate SQL DDL from the SDM, IDM, and ODM. And finished the ability to create SQL DDL for subtyped entities, tables, and DBMSTables. --Finished the ability to import and export comma delimited ASCII files for a number of data element meta-entity types. That is, Concepts, Data Elements, Data Element Concepts, Data Element Classifications, Value Domains, and Value Domain Values. ******Metabase v05.02b***** [04/05/2002] --Fixed a display error on the value domain selection screen while building a root entity for a value domain structure. ******** V5.02 additions/changes******** [02/08/2002] --Enabled the creation of Subtyped Entities, Tables and DBMS Tables --Conforms to upcoming ISO ANSI standard 11179 for data element metadata by changing Data Element Domain to Data Element Concept --Added Value domain Values --Added the ability to map Value Domain Values across value domains --Added the ability to map view column across views. --Created the ability to move attributes, columns, and DBMS columns within Entity, Table, and DBMS Table root and subtypes --Created the ability to move sub-typed entities, tables, and DBMS tables to different subtype "parents." --Expanded Business events to support Business Event Cycles and Calendar Cycles. --Related Business Event and Mission-Organization-Function. --Updated the Data Modeler Architecture and Concept of Operations --Updated the Data Element user guide --Updated the IDM, SDM, and ODM user guides WARNING..An intense review with key persons in the ISO 11179 data element metadata community has caused us to rename data element domain. It has become Data Element Concept. Further, it is a Bill of Materials. Finally, all Value Domains (that is, value domain, DataElementValueDomain, AttributeValueDomain, and ColumnValueDomain have been collected into a single BOM structure. This enables better across-the-enterprise visibility and increases 11179 compatibility. These changes are accomplished in this release. YOU MUST read and apply the following changes in the event you have production metadata that you want to migrate from V05.00 to V05.02. 1. The table, Conceptual Domain, has been changed to Conceptual Value Domain. Name changes also applied to Conceptual Domain Structure (now Conceptual Value Domain Structure and Conceptual Domain Structure type (now Conceptual Value Domain Structure. The reason for these changes is simple. The ISO 11179 definition for Conceptual Domain clearly shows that it is to represent the "value meanings of value sets." NOT the domain of concepts.... Hence the name change. 2. Created a table set, Concepts, Concept Structure, and Concept Structure Type. The ISO 11179 names for these tables are Object Class. However the 11179 definition for Object Classs clearly implies that it is to describe the concepts of the objects for which data element metadata is being created. So, it is named, Concepts. 3. Created the start of importing SQL DDL. With this release it only imports tables, columns and data types. It does not import primary and foreign keys. Look for a release v0503 by the first part of May 2002 to accomplish a full SQL DDL import. 4. Created the ability to do bulk data loading for both data elements and for value domain values. Depending on demand this type of facility may get expanded. So, make your needs known. 5. Added the ability to interrelate view columns from one view to another and to relate to that inter-view column collection a defined process for the transformation. 6. Once you install this new set of metadata EXEs into your directory, then to "use" your previously created Conceptual Domain tps files, change their names from: ConDom.tps ======> ConValDom.tps ConDomS.tps ======> ConValDomS.tps ConDomST.tps ======> ConValDomST.tps 7. Copy the TPS table, upg.tps into EACH metabase data directory that you have..... 8. Start the metabase. Bring up the Admin module, Select/Point to the data directory" Bring up FM (File Manager) screen, Press "Tag All", press "Freshen." That should do any conversion you need... ******** V5.00 additions/changes******** [12/10/2001] --Fixed a bug in the Database Objects Tables Assignments window in the DBO application. [11/12,14/2001] --recompiled all applications - No significant changes. [11/06/2001] --Added the ability to target particular meta category values to specific levels of a data element domain. [10/25/2001] --fixed the transfer of a table and its descendants from one Schema to another. --fixed the transfer of a DBMS table and its descendants from one DBMS schema to another. --modified a number of windows in the view data model. --finished all the data modeler user guides [10/11/2001] --fixed the inability to update some data in the IDM --added the reverse engineering capability to assign a table to different schema. --fixed a difference in behavior in two routines that updated columns within IDM [10/07/2001] --Updated Pkey delete business rules in SDM, IDM, and ODM to give severe warning messages before Pkey delete --Created the Specified Data Model Users guide [10/02/2001] --Updated SDM to fix non-display of the meta category values in the assign meta category values to attribute --Updated the displayed column names in the re-assign entity to subject window. [10/01/2001] --added missing relationship between value domains and data element domain value domains. --removed unnecessary intersection table between data element domain concept and data element domain. Users will have to reassign data element concepts to data element domains directly by updating the newly installed data element domain concept foreign key value within data element domain. --added a re-assignment of data element domain to conceptual domain --upgraded all the TXRs (report templates) and published them separately --created the data elements users guide. Other data modeler user guides will be created and posted at the rate of one per week. [09/18/2001] --fix display error in Database Object Table Process Column assignments window. --Implemented missing functionality related to value domains in the Data Element component of the data modeler module [09/17/2001] --fix Transaction Control Frame error 48 on form update [09/10/2001] --new Database Objects module: dbo.exe - fixed window display error, & includes new data. --re-added the ASCII data dumpload utility with new version --fixed install program - missing c55fm2x.dll, and c55hlpx.dll in 09/01 version of installer. [09/01/2001] --Now allow for install to any directory. --Writes SQL from ODM, SDM, and IDM. --removed Dumpload in demo (temporarily) --removed Security (users, groups, etc) in demo. ---new version of C-Scan admin utility. Password is still:"scan" ******** V4 ******** This was an internal version of the metabase that was never released because version 5 got finished a lot sooner than we expected. So, rather than have two releases in a six-month time frame we just skipped Version 4. ******** V3.04d additions/changes******** --fixes to the checking of acceptable semantic allocations for data element domains, data elements, attributes and columns. The 3.04c version was allowing allocations that were not proper contained semantic subsets. --fixed report in SDM, so that you can preview before printing. ******** V3.04c additions/changes******** --fixes to tagging displays in the specified data model and the data elements model --miscellaneous other fixes to make tagging go smother. ******** V3.04b additions/changes******** --fixes to display errors in windows... --support for candidate keys... --the ability to install semantic at a "higher" level, than already allocated... --support for secondary keys... --reverse engineering windows... --compound data element as bill of materials... --more... ******** V3.03a additions/changes******** 3/15/2000 --fixed display problem in Data Modeler Data Element module Derived Data Elements and Data Elements Assignment window. --fixed display problem DataElement module browse Data Element Value Domain. --includes week of 3/5/2000 change in demodata MetaCategoryType data file --fixes product installation problem that caused "Max Installs Exceeded" and other related errors. User prompted to re-enter beta registration info. ******** V3.03 additions/changes******** 3/1/2000 --upgraded C-Scan v2.9 admin functionality, now the Cs.exe password is variable, see the Help for that program. --Improved File Manager Utility in the Admin module, now it does many file maintenance procedures all in one place. --Included more TXR Reports for the Data Modeler Modules. --Added recursions throughout the entire metabase --Added full data modeler modules for semantics, data elements,specified data model, implemented data model, operational data model, and data interface model --integrated database objects with implemented data model. ******** V3.0 additions/changes******** --removed Security until gold release --removed support for DBASE III/IV Import Export. --Admin Functionality:--Added ASCII Data Dump-Load Utility --Upgraded Backup Utility to include clearer interface and also logging/reporting of backup and recovery processes. ******** V2.6 additions/changes******** Added Data Modeler modules: Implemented Data Model ******** V2.5 additions/changes******** Added Data Modeler modules :Operational Data Model ******** V2.2 additions/changes******** Added Data Modeler modules : added Specified Data Model ******** V2.0 additions/changes******** --Added Data Modeler modules : Data Elements, and Data Interface Model ******** V1.25 additions/changes******** --separated admin program from main Metabase application --added Capesoft C-Scan 2.6 admin functionality: allows for search and replace in data files, and tells other data file info. The password for this by default set to "scan" --fixes to some update windows --added program level Security manager. via use of login's coordinating with users and groups via a security admin program. ******** V1.22 additions/changes******** --fixed Admin Backup and Recovery utility for Metabase data sets. ******** Ver 1.21 Changes *********** --Fixed displays for intersection records assignment windows in INA and RLC component. 12/15/98 --Backup and Restore Utility is turned off until the next version of Metabase is available, probably around the new year. *********New Features of Ver1.2************* --Added Metabase component Database Objects. --TPSfix. automatically will automatically correct corrupted files, in the unlikely event your application crashes from a broken data file. --Added a new feature that will automatically upgrade (or downgrade--if you request it) the file schematics of a data file to allow for changes in the data structure of an application. *********New Features for Ver1.1************ --Added more "Canned Reports" to the various modules. --Added the ability to select/create multiple data sets. *********New Features of Ver 1.0b*********** --Fixed reports that called for infosys.tps