Dashboard > Electronic Research Administration > Database Kuali Migration > Information > Page Comparison
Electronic Research Administration Log In   View a printable version of the current page.
Database Kuali Migration
Version 4 by K Lars Lohn
on Jul 14, 2005 16:12.


compared with
Current by Terry Durkin
on Jul 19, 2005 12:30.

(show comment)
 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 5 changes. View first change.

  
  
 h2. Questions about the ERA to Kuali database migration.
  
 # It is my understanding that the ERA database is being merged into the Kuali database. This process involves identifying tables with similar purpose and information and then modifying ERA to use the Kuali tables instead of its own. Is this essentially correct?
 {panel} no answer yet. {panel}
  {panel}We are mainly copying the current ER tables into the Kuali database and making minor changes to resolve naming and data type differences. The current integration point between ERA and the current FIS is the data in the FIS_ER schema. These will go away, as we migrate ERA into Kuali and begin to use the operational data from that system.{panel}
 # Where is the documentation of the changes being made?
{panel} no answer yet. {panel}
  {panel} You're lookin' at it :) {panel}
 # Are there any cases where a Kuali table has more columns than the equivalent ERA table? Are views being used to _trick_ ERA into continuing to work without modification of source code or is the ERA source being modified? Some of the ERA views use the SQL '*' wildcard in their definitions. This means that a change in the order of columns of an underlying table could cause a silent failure with data being associated with the wrong columns.
{panel} no answer yet. {panel}
  {panel} ERA source is being super-modified. The integration tables (FIS_ER) are batch fed in from the FIS. Therefore there should not be any instances of the FIS_ER tables having more/less data than what ERA knows about. {panel}
 # Does the Kuali database use referential integrity constraints? If so, will those contraints be spread through the ERA system?
{panel} no answer yet. {panel}
  {panel} That is currently being discussed by the Kuali architecture group. RI is being handled by OJB.{panel}
 # The automatic copying of data into the existing ERA FIS_ER tables (and the Universal User Table [ER.ER_UNVL_USR_T]) can be thought of as a functional _firewall_ separating the ERA database from other systems. When the integration is complete, will this separation and replication system remain in place?
 {panel} no answer yet. {panel}
  {panel} No. As ERA (KRA) is integrated into Kuali, this seperation will cease to exist. {panel}
Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.7 Build:#524 Jul 28, 2006) - Bug/feature request - Contact Administrators