Utah State University Using XML for Archiving Banner Corrections

1
Utah State UniversityUsing XML for Archiving
Banner Corrections
An Oracle XML_ARCHIVE
Marvin (Joe) Burger   Database Analyst jburger_at_cc.
usu.edu [phone] Cell 760-4302 Information
Technology Utah State University UMC 4410 Logan,
UT 84322
2
USU XML ARCHIVE Where do you store the Duplicate
PIDMS and other records once they are
removedfrom the SCT Banner System?!!!
NOBTRAN
NORTRAN
NOREAER
XML_ARCHIVE Table
NORCMNT
NORROUT
3
USU XML ArchiveProcesses to be applied to data
in the Archive.
Research
XML_ARCHIVE Table
Warehouse
Remove
Restore
4
USU Projects Under Development
XML_ARCHIVE Table For Epaf Acat Removal
XML_ARCHIVE Table For Duplicate PIDM Removal
5
USU XML Archive System By PL/SQL Packages
BACKUP AND REMOVE ----------------------- Banner
INB Application
Research Warehousing Restore Archive
Removal ----------------------- Banner SSB
Application
ZGPARCH
ZGPARCH_UT
ZGPARCH
ZNOPEPAF
ZGPDPIDM
6
Z_ZGPARCH The XML ARCHIVE Utility Package
7
Z_ZGPARCH The XML ARCHIVE Utility Package
8
Z_ZGPARCHThe XML ARCHIVE Utility Package
9
Z_ZGPARCHThe XML ARCHIVE Utility Package
10
Z_ZGPARCH_UTThe XML Restore Utility Package
11
Z_ZNOPEPAFEPAF Removal Package
12
Z_ZGPDPIDMDuplicate PIDM Removal Package
13
BeginningDesign Assumptions
14
What the USU XML Transaction Archive is Not!

• It is not a Document Archive and should not be
  used as one.
• It will not be used as a NXD (Native XML
  Database.)
• It will not be used to backup massive amounts of
  data.
• Large scale archive of relational data should be
  discouraged .
• Independent archive tables should be used for the
  areas of data that are being corrected.
• It should be remembered that it is only intended
  to provide a method of non-destructive removal of
  records and their structure from the Banner
  Database System.
• It can only be used for simplified research of
  the data that was removed from the Banner System.
  The data must be restored to a standalone schema
  to allow a more complex analysis within its
  Native Relational Table structure.
• The data could also be extracted to a coma
  delimited file for user research using Microsoft
  EXCEL.

15
What the USU XML Transaction Archive Will provide.

• A method to store data removed from the Banner
  Database System.
• Allow for backup based on Jobsub form with six
  AND conditional statements.
• Allow for conditional statement using EQ, LT, LE,
  GT, GE, NE.

16
What the USU XML Transaction Archive Will provide.

• Provide executable oracle functions to store the
  structure and data.
• The functions will be reusable from independent
  Packages for batch processing.

17
What the USU XML Transaction Archive Will provide.

• Date range
• Table Name
• Selectable Table Columns to be displayed
• 10 - 20 Rows per a page
• Scrollable HTML page when data over flows the
  form.
• Next Page available after every full page display
• Return to date range page when end of data
  reached.

18
What the USU XML Transaction Archive Will provide.

• A method to remove data that is placed on the
  archive in error.
• A SSB password secured form to remove data that
  has been placed on the archive in error.
• The method will only be available to maintenance
  IT programmers.

19
Issues that need discussion concerning the USU
XML. The Transaction Archive should provide the
following for discussion

• Archived Table names.
• Schema name where Archive Tables will be
  retained.
• Schema name where Archived Structures and Data
  will be restored for research.
• Method to move the restored research tables to
  the Warehouse for the users.
• Placement of the maintenance and research HTML
  pages under the Web Tailor structure.

20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)