Data Standards & Integrity Committee

Banner Training Center Building 2

Meeting Minutes

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

Members in attendance:

I.   Review Minutes

ˇ   The minutes of the January 31, 2005 meeting were reviewed and approved on motion of Deborah Bridges.

II.   Team Leaders Report of Actions

ˇ   The resolutions passed at the January 31, 2005 Data Standards meeting were presented to the Team Leaders committee for approval. The Team Leaders rejected all of the recommendations. The team leaders will implement only required changes to the codes.

III.   Process for to implement changes to the Data Standards Manual

ˇ   The membership discussed the recommendation process and methods for developing rationales for any proposed changes. Before bringing changes to Data Standards, the proposed changes should be discussed with the implementation team and have the support of the Team Leader. The committee agreed that future proposals should contain a justification for the suggested changes to the data standards.

IV.   Report on Name Changes

ˇ   Debbie Minyard and Maria Cisneros stated that there was no progress in their research on name changes and the self-service personal information page. This item was tabled until the next meeting.

V.   Report on Degree Type Codes

ˇ   Marlise McCammon provide a list of selected degree types and abbreviations used by Human Resources. The membership reviewed and discussed the codes used by both Human Resources and the Registrar’s office.

ˇ   Tina Hunter stated that Information Technology would need a list of degree type codes to from Human Resources to enter into Banner validation tables.

VI.   Citizenship Type

ˇ   Chairperson, Cathy Sarrazin, reported that the current data standards manual specifies a blank space to be used to identify an unknown citizenship type. Since Banner will not accept a blank space, the chair recommends that the code “U” identify an unknown citizenship type.

VII.   Relationship Codes

ˇ   Chairperson, Cathy Sarrazin, reported that the current relationship codes listed in the data standards manual are not accepted Banner format. Banner relationship codes are limited to 1 character.

ˇ   The membership proposed alternate codes. They will be presented at the next Team Leader meeting to be approved.

VIII.   Legacy Codes

ˇ   The membership agreed to lay this item on the table until more information becomes available. It will be forwarded to the Advancement Team for a recommendation.

IX.   Address and Telephone Type Requirements

ˇ   Tina Hunter reported on a list of items are “system required” by Banner and were not included in the Data Standards Manual.

ˇ   The Banner Summit conference revealed that most colleges do not use the self-service address change feature. The information is forwarded electronically to personnel who enter it into banner.

ˇ   Many of the conference participants reported that a previous version of Banner had corrected the problematic use of restricted symbols. However, recent Banner training on campus still teaches that the same characters still prohibited.

ˇ   Tina Hunter will present a follow-up report at the next meeting.

X.   Source Codes

ˇ   Tina Hunter provided a list of source codes available in Banner that would reference the source of information used to gather addresses and name type data.

ˇ   The members discussed the potential needs and whether or not source codes should be included in the Data Standards Manual.

ˇ   We have been told that we do not need name types and so far have not found a use for them, so at this time, we will not use name types.

ˇ   Tina Hunter also pointed out that Banner lists Ethnicity Code #5 as “Not Used” while IPEDS used Ethnicity code #5 as “White”. She recommended that we remove the Banner Code #5, ‘Not Used” to prevent future conflicts.

XI.   Hyphen, Apostrophes, Periods, and Slashes

ˇ   Chairperson, Cathy Sarrazin, reported that the current data standards manual prohibits the use of these characters based on a recommendation from SCT Banner. Several examples were presented to illustrate how confusing address data would become. It was recommended that the committee meet with the SCT Consultant to determine if the Hyphen, Apostrophe, Period, and Slash may be used for clarity.

ˇ   Judy Terrell and Debbie Bridges volunteered to research this topic further and report at the next meeting.

XII.   Tables for Appendix

ˇ   Chairperson, Cathy Sarrazin, suggested that data standards include a reference section listing abbreviations of street designations.

ˇ   The members reviewed and discussed list and further recommended that the Team Leaders consider adding this list to the Help Table in Banner

ˇ   The membership accepted the Chairs recommendation to include a reference section listing common abbreviation of street.

XIII.   Apartment and Suite Numbers

ˇ   Chairperson, Cathy Sarrazin raised the issue of address line length and the amount of available space to include an apartment number. Since an address line is limited to 30 characters, the apartment number may exceed the space provided.

ˇ   The membership debated the consequences and discussed other options. This topic was laid on the table until more information becomes available.

XIV.   Announcements

ˇ   Meeting Schedule - Spring 2005 -

Meeting Adjourned at 3:45 pm.

Back to top

1