Page 1
Cameron University Banner Project
Meeting Agenda and Notes
May 29, 2016
Banner Technical Team
Committee/Meeting Name
December 14, 2009
10:00am
Date
Time Convened
Time Terminated 11:15am
Julie Duncan
Location Admin 201
Recorder
Kurt Jn Marie, Chase Bailey, Cheryl Davis, Dawne Massey, Debbie Goode, Rick Clyburn, Julie A. Duncan, Angela
Members Present
Melton, Kelly Simon
Greg Duncan, Sherry Hendrix
Members Absent
Visitors
Topics
Minutes from Nov 30
Next meeting
Update from Sherry
Discussion, Information
Action Taken, Decisions, Recommendations, Time Line
okay
1. ODS: Dawne and Kurt are administrators
a. Update: Cognos training:
Jan 25: Business Author: ST
Jan 26: Business Author lab time
Jan 27: Consumer training: ST morning and afternoon
sessions
b. We need to decide on some guidelines for writing scripts
and which database to use: ODS or Production. There are
instances where scripts have to be written against production
(updating, triggers, etc.). For the most part though, we want
scripts written against the ODS. The ODS data for a particular
area can be refreshed on demand. We don’t want to do that
on a regular basis, but we can set up schedules to refresh
every two to four hours as a temporary measure. Let’s
discuss.
2. Nolij: Kelly is the administrator (Julie is helping with general
person)
a. GP Sync Update
b. SASR Update: Admissions/Recruiting sync update from
week of 12/7/09
3. e-Print: Greg, Chase and Kurt are the administrators
a. Update
Lynn Lackey needs a business author license.
Only Greg and Chase will have update access to PROD and
TEST. Send email to them to run the information.
We need to run as much as possible from ODS and only
absolutely necessary reports should be run directly against
production. We can run sql against ODS. It doesn’t have to be
only cognos.
Nolij: The GP sync took 8.5 hours for the first pass of 1669
records. Julie is still going through the suspended records and
making some more changes from problems that arose with
duplicates and will have to reprocess some of the records.
SASR is being tested by Nolij. .
Page 2
Topics
Cameron University Banner Project
Meeting Agenda and Notes
Discussion, Information
4. E-Vision: Rick and Cheryl are the administrators
a. Update:
5. AppWorx: Greg and Chase are the Administrators; Angela will
be the technical lead
a. Update: nothing new
6. Workflow: Greg and Rick are the administrators
a. Training:
Tuesday 12/15/09: FA
Wednesday 12/16/09: ST
Thursday 12/17/09: ST
7. Luminis: Julie is the administrator
a. Update: load testing completed yet?
8. Update on interfaces/extracts
a. Early Alert: 9/10/10
b. Blackboard Connect-Ed: 8/15/10
c. ID Card: 8/1/10
d. Library interface: 11/30/09 Pretty much done.
e. Clean Address for HR, FI, AD & FA: 2/1/10
f. Clean Address for ST: 8/10/10
g. Diplomas: 7/31/10
h. Directory Labels: 11/23/09 Cheryl working with Kelly
i. Extracts to accommodate insurance-related data. Kurt is
working on and plans on having it done today. 11/30/09
9. Installations:
a. Outstanding PROD: Ken Rickard to install Cognos
10. Integrating Banner access into existing user management
system. Complete
11. Cameron’s code tree for Banner ($CAMERON_HOME) on
dev-db01:
Keeping the directory structure similar to that of Banner’s
Code tree ($BANNER_HOME) will make the Banner
May 29, 2016
Action Taken, Decisions, Recommendations, Time Line
AggieAccess is not up until Feb but the first payroll will be
before that. We won’t have online access for paystubs. We can
use the generic paystub for one or two months. We shouldn’t
try to recreate our current paystub for that short of time.
We’ll need to add the email package to FormFusion. The idea
will be so when purchasing prints the PO, its emailed to the
person who sent it and then they can get it to the vendor.
Student changed their workflow to letter training and will do
their workflow in January.
Luminis: Carlos ran into internal issues and has not completed
to production test load.
Kurt has the library script ready and will be adding it to the cron
soon.
Directory labels has a view ready but it is pointing to
production. It needs to be pointed to ODS. Updates to directory
information will be done in Banner now.
Insurance extract is done and resolved.
Ken Rickard installed Cognos.
Complete
Julie spoke to Greg last Monday about changes regarding SSB as
the norms and customizations are different for it.
As they come along, we would like to have more examples.
Page 3
Topics
Cameron University Banner Project
Meeting Agenda and Notes
Discussion, Information
Upgrade process easier. That way if mods are made to
existing files in $BANNER_HOME we can identify the mod
easily in Cameron's Banner Code tree
($CAMERON_HOME).
May 29, 2016
Action Taken, Decisions, Recommendations, Time Line
Chase suggested that all scripts be kept on the unix box.
Anything that has already been created needs conformed to the
standards and then moved to the unix box.
What about naming of new files? How about keeping this
similar to the standard of what we have for IFAS except
change the module name so that they match Banners?
Where will files be stored?
Ex. rim = student
alumni
arsys
finaid
finance
general
payroll
posnctl
Chase and Greg have come up with some CU Banner naming
conventions.
They have been added to the UNIX/Banner doc (chapter 13).
W:\Workgrps\its\Banner\unix_banner_systems.pdf pages 144 to
148.
12. Is it okay to stop running the Name and Address Clean Up
script on Legacy? This script fixes names and addresses and
also sends an email to users to fix invalid names and
addresses.
Yes. Data needs fixed so that bad addresses don’t get back in
Banner and then CleanAddress has to fix them again. Kelly is
going to run a program to find out why some of the address
changes like South changing to S are not being automatically
changed.
This data is being rolled into Banner and fixed with Clean
Address in batch mode.
13. PROD access for financial aid. They need to add scholarship
funds and tuition waiver funds. They also need to enter
changes from their pre go-live support. The following is a
result from Chase and Laurene’s phone conversation: After
talking with Laurene we will continue as planned with creating
all users accounts/security in PROD that currently exist in
TEST. So everyone will have access come Monday.
FinAid can get into PROD so everything is good.
Page 4
Topics
Cameron University Banner Project
Meeting Agenda and Notes
Discussion, Information
May 29, 2016
Action Taken, Decisions, Recommendations, Time Line
Also during the interim time she had these recommendations
for limiting/tracking GP changes:
Limiting access to all %IDEN forms and FTVVEND (Basically
any form you can delete or generate an ID).
She also mentioned auditing the SPRIDEN table for changes...I
think this will help. I will get something like this setup in cron:
- We could write some sql to audit SPRIDEN each day by looking
at the spriden_activity_date column which gets updated when
changes are made.
There is also a spriden_user column as well that will tell us who
performed the last change.
PROD> select * from spriden where
trunc(spriden_activity_date) = trunc(sysdate);
Discussion?
14. There are people who have multiple campus emails because
they are both student and staff which are formatted differently
(julied@cameron.edu vs julie.duncan@cameron.edu). In our
current system, we used whatever was on primary_mst and
required that faculty/staff have their fac/staff campus email in
that spot. In the new system, we can and have brought over
both campus emails. I have verified that only one campus
email is marked as preferred when both exist. HOWEVER,
there is nothing keeping someone in INB from saying their
personal email is the preferred one. If that is done, the
workflow below will just return whichever campus email is
latest which currently would be whichever loaded last in
conversion.
I think it would be good to have a written policy on the campus
email which will also have to be incorporated into user
management when the email entries are created/deleted. There
are more than one way we can approach it.
1. Only one campus email should be active. If a fac/staff
campus email exists for a *regular* employee, any
student campus email entries are marked as inactive. If
the employee is terminated, the fac/staff email is
Add a directory email type.
Debbie feels fairly sure that an email was sent that all official
information would be sent to a student’s campus email and will
look for this.
Cascade would be directory, campus, then personal on both
luminis and ods and also the preferred indicator.
Directory and campus emails would be displayed only and not be
allowed to change on the internet.
Page 5
Topics
Cameron University Banner Project
Meeting Agenda and Notes
Discussion, Information
inactivated and the student email activated. Must decide if
fac/staff email is deleted or just inactivated. This might
have to be a manual decision as I believe that some
student workers end up with a fac/staff email address but
it should still be their student campus address that
remains active. In this case, to choose the campus email
we would want to use “where goremal_status_ind = ‘A’
and goremal_emal_code = ‘CAMP’” Inactive addresses do
not display in SSB and are only seen on the INB screen.
Campus email is currently marked as display only on
SSB. So if it’s marked preferred in INB, the person would
not be able to change that in SSB. This works well for
fac/staff but unless there is a policy stating that student’s
campus email is the email Cameron sends information to,
it doesn’t work well for students wanting to change their
preferred to be the personal email.
2. Add a directory email type, move all fac/staff emails to this
type and mark them preferred. Directory address would be
marked as display only and marked preferred. Fac/staff
could not change it to be another preferred address unless
they have access in INB. Having a separate email type for
fac/staff email though requires that a cascade be used
almost everywhere or only use the preferred address.
Using the directory email type would mean that most
fac/staff would not also have a CAMP address.
3. Other ideas??
Considerations: how does either decision affect ODS/Cognos,
luminis, workflow, directory system, etc.? Luminis can do a
cascade or choose preferred email but it can select only one email
and the rule applies for everyone. I send email to Aubrey/Jamie on
this a few weeks ago but haven’t heard. My assumption is that
luminis will use the one marked preferred and not try to develop a
cascade.
Whatever we decide should go to ILT as a recommendation and
then included in the data standards doc.
This will require E.C. approval
May 29, 2016
Action Taken, Decisions, Recommendations, Time Line
Page 6
Topics
Cameron University Banner Project
Meeting Agenda and Notes
Discussion, Information
Action Taken, Decisions, Recommendations, Time Line
15. Our understanding is that Admissions is under the assumption
No decisions have been made yet. They are contacting different
schools to see what they are doing and might possibly do a
workflow for part of it. Debbie sent an email to Jamie, Linda, Chris,
Brenda, Ninette and Donald 12/3/09 to hopefully get a working
group formed to discuss. Cc: Sherry, Dawne, Rick, Kelly and
Angela
that AID will continue to process awards in Banner as they do
in our current system. AID says Admissions will be putting on
their own exemptions in Banner. The Business Office needs
to let everyone know what they need to do. IT needs to know
if the non-resident tuition status is being converted to a field
that can be used for awards. From Brenda’s email below, it
sounds like no one has discussed how this process is going to
work. How should we handle this?
Duplicates
16. Will anyone be available to go to Summit?
17. Kelly is going to run duplicate checks every afternoon and will
delete them out of insight. They will receive the data and by
close of business the next day the data needs merged. The
hope is to keep the duplicates out of banner. Debbie sent a
strong email to Jamie regarding duplicates. She will send
another email and bring it to ILT. Users are going to have to
have some consequences for putting in duplicates.
Task Lists
?
Tech Team & ITL
Tech Team
Tech Team
Debbie
Tech Team
May 29, 2016
Linda requested the self-service transcript kiosk be available in
Banner.
Continue to update:
W:\workgrps\its_share\Banner\BANNER Data handling.docx –
OSRHE info needs to be added and which DBs it will be reported
from
Decision re: no mods to Baseline Banner: possibly w/ the
exception of fed & state mandates??
Research best practices for keeping 3rd party software in sync with
Banner upgrades and patches
Update Milestone Certification & keep up-to-date
Julie started a Go-Live Checklist document at
w:\workgrps\its\banner
Please add to it so that we remember to do everything after each
conversion. This should be our checklist of things that must be
done after the conversion scripts but before we let the users in for
testing.
Jamie Glover is responsible for setting a meeting up and getting
answers. Debbie will send another email as we need to get this
decided ASAP.
Nope
Page 7
Cameron University Banner Project
Meeting Agenda and Notes
Greg, Chase & Debbie
Patch management procedures documented and request form.
ILT
Reviewing critical programs for go live and all programs required
@ go live
Identify what needs to be setup through FormFusion and
Intellecheck
Actionline support procedure
ILT & Tech
Debbie
May 29, 2016