Data Standards & Integrity Committee

Banner Training Center Building 2

Meeting Minutes

Meeting called to order on March 28, 2005 at 2:15 p.m. by Chairperson Cathy Sarrazin.

Members in attendance:

I.   Review Minutes

·   The minutes of the March 14, 2005 meeting were reviewed and approved on motion of Gwen Boutte.

II.   Team Leaders Report of Actions

·   The proposed changes recommended at the March 14, 2005 Data Standards meeting were presented to the Team Leaders committee for approval. The Team Leaders accepted all of the recommendations to change citizen, relationship codes, a street abbreviation appendix and Address Source codes.

III.   Report on Name Changes

·   Debbie Minyard stated that there was no progress in there research on name changes. This item was tabled until the next meeting.

IV.   Report on Degree Type Codes

·   Debbie Minyard stated that her research has revealed a variety of possible codes for degree types. There does not appear to be a standard list of abbreviations for degree types.

·   Debbie Minyard recommended that a list of degree type’s codes used by the college be drafted.

V.   Legacy Codes

·   Chairperson, Cathy Sarrazin, received a suggested list of legacy codes from Connie Boudoin of the Resource Development Office. The recommended changes to the data standards would meet Banner requirements limiting legacy codes to one character width. The membership reviewed and discussed the proposed legacy codes.

·   On motion of Cathy Sarrazin, the committee accepts the following legacy codes.

VI.   Address and Telephone Type Requirements

·   Tina Hunter reported to the membership that Banner could attach the Telephone type to match the Address type code. She questioned whether that the Data Standards committee should consider using this option.

·   It was also questioned by Tina Hunter that the committee consider adding BI for Billing address and PA for Parent address to the codes. In addition, the address/telephone type codes include two unidentified codes XX and TA. It was suggested that if these codes are not going to be used that the committee consider removing them from the list of type codes.

·   Mickey Hughes, SCT Banner consultant from the finance-training module, joined the meeting briefly to give an opinion on these issues. He stated that the XX and TA codes system required by Banner in order to process “TGRr feed”. In addition, he saw no reason by telephone and address types should be attached to share the same code and does not think it necessary to add any new type codes.

·   The membership reviewed and discussed all of these options and agreed that no action should be taken until more information is available.

VII.   Hyphen, Apostrophes, Periods, and Slashes Report

·   Judy Terrell stated that an SCT Consultant confirmed that the slash “/ ” can be used when entering data. The membership reviewed and discussed the available options.

·   It was suggested that members of the committee meet with the SCT Technical Consultant to determine if the Hyphen, Apostrophe, and Period may also be used.

VIII.   New Business

·   Tina Hunter reported that SSPS currently uses 2 characters to identify county codes. She recommenced that the data standards be amended to use 3 characters to identify county codes to match the format of data provided by other agencies.

·   Tina Hunter reported that Canadian provinces must be included in the state codes validation table.

·   Tina Hunter recommended that the Data Standards Appendix include a list of abbreviations for Canadian provinces, U.S. states, and county codes.

IX.   Announcements  

·   Meeting Schedule - Spring 2005 –

·   The meeting scheduled for April 4, 2005 has been canceled.

Meeting Adjourned at 3:36 pm.

Back to top

1