Division Technology Meeting

1
Division of
Student Affairs

• Division Technology Meeting
• September 16, 2003

2
Agenda

• Everyone
• Mouse pads
• Future meetings
• Tech Staff Assessment
• All Staff Listserv
• Wireless update
• Division Logo
• Feedback on new Division Website
• LANTech Stuff
• GroupWise Expiration
• GroupWise 6.5
• LANTech Standard Duties
• Webmaster Stuff
• Administration Regulation on Web Accessibility
  Website
• .../student_affairs PHP enabled
• SACS Compliance
• PRR Compliance for Websites

3
Mousepads
4
Future Meetings Training

• Meetings
• Guest Speakers
• ACS
• Dates
• Monday, November 17, 2003
• Tuesday, January 20 , 2004
• Tuesday, March 16 , 2004
• Tuesday, May 18 , 2004
• Trainings
• Topics to be determined soon
• Dates
• Thursday, October 16, 2003
• Tuesday, February 24, 2004
• Tuesday, April 14, 2004

5
Tech Staff Assessment

• EAC 583 Needs Assessment in Training
  Development
• Student Project for Fall 2003
• Assessing training needs of Webmasters and
  LANTechs
• Develop an instrument for measuring skills needed
  to perform standard duties
• Develop a training plan for achieving those
  skills

6
All Staff Listserv

• Listserv for all Division staff
• Should be up by December
• To be determined
• Moderated or not
• Membership maintenance
• Standards for appropriate use
• Monitoring for appropriate use
• What would a good email address be?
• studentaffairs_at_lists.ncsu.edu
• stuaff-all_at_lists.ncsu.edu (Large Staff Listserve
  address is stuaff-l_at_lists.ncsu.edu)
• dsa-all_at_lists.ncsu.edu
• Other ideas?

7
Wireless Update

• Fully Covered Buildings
• Daniels
• Hillsborough Building
• Talley Student Center and North Plaza
• Witherspoon Student Center
• Partial Coverage
• Avent Ferry Complex
• Broughton
• Cox
• DH Hill
• Harrellson
• Jordan
• Leazar
• Mann
• Page

• Park Shops
• Patterson
• Poe
• Riddick Labs
• Withers
• Weaver
• Venture II
• Venture III

8
Wireless Update

• Deployment Plan
• Access Points (small hubs one or more per
  building)
• Vivato (large screens only 4-5 for entire
  campus)
• More information
• http//www.ncsu.edu/it/cd2003/cd_content/get_conne
  cted/wireless/
• Connect via http//nomad.ncsu.edu/ with unity ID
  and password

9
GroupWise Expiration Archiving

• What is Expiration?
• Email items (both received and sent items) will
  be deleted after 180 days if not archived by the
  individual customer.
• Calendar items (appointments, tasks, and notes)
  will be deleted after 2 years (730 days) if not
  archived by the individual customer.
• Items automatically deleted will not be placed in
  the trash and as the trash is already emptied
  based on a 7-day expiration, this procedure will
  have no impact on the trash folder.
• The process is a continual background application
  such that messages older than the limit are
  continually acted upon, not a batch process
  occurring only every 180 days.
• When will it begin?
• December 20th is the target date for
  implementation however this is tentative,
  pending approval by EOM.
• Expiration will be immediate upon implementation
  (no gradual phase in).

10
GroupWise Expiration Archiving

• What is archiving?
• Archiving is a process that removes the item(s)
  and any attachments from the post office database
  and stores them in an individual database (per
  person).
• How do I archive?
• This action is performed by selecting items,
  right clicking, and choosing "archive". The
  cabinet structure of the mailbox is maintained in
  the archive.
• If a message from a folder is archived, the
  folder is automatically created in the archive if
  it doesn't already exist.
• Due to the processing required to archive items,
  no more than 200 items should be selected to
  archive in a single transaction.

11
GroupWise Expiration Archiving

• Training
• LANTechs Review at October 16 Training
• LANTechs Share with your area
• All Division Staff
• 10 sessions total in October November
• Open enrollment
• 30 minutes long
• Handouts on the web soon

12
GroupWise 6.5

• To be implemented in the next few months
• New features
• Checklist folder (use as a To Do List)
• Junk Mail Handling (Block or Junk Trust List)
• Categories (Follow-Up, Low Priority, Personal,
  and Urgent plus edit/add others)
• Sent Items (can be filed pending items are bold)
• Much more
• Training offered through McKimmon Center
• 75 fee
• Day-long session
• LANTechs encouraged to attend
• Open to anyone

13
LANTech Standard Duties

• Draft completed by Nicholl Simpson and Martha
  Pierce (thanks!)
• NCS committee on LANTech Responsibilities

14
Administrative Regulation Web Accessibility

• Administration Regulation Policy Statement on
  Web Accessibility
• http//www.ncsu.edu/it/uitc/pending/webaccessibili
  tyregulation-v11.doc
• Draft to be voted on by University IT Committee
  in November
• Standards provided by Assistive Technology
• http//www.ncsu.edu/it/dss/webaccess/standards.htm
  l
• Compliance required by January 2006
• Non-compliant pages removed from service

15
New Division Website Design

• Feedback/Corrections
• Departments Listing
• Links
• Re-directs
• Online Form
• Announcements
• Home page announcements
• Time and space constraints
• Online Request Form

16
(No Transcript)
17
Division Logo

• Division Logo can now be downloaded from the web
• Two formats available .gif and .png
• Two versions available with text and without
  text
• Two colors available Black White, and Black
  Red (CC0000)
• Feel free to use other colors

18
(No Transcript)
19
Division Website PHP Enabled

• Everything within ../student_affairs is now PHP
  enabled
• Includes
• Campus Activities
• Career Center
• Carmichael
• Chaplains
• Counseling Center
• CSLEPS
• DETS
• Health Services (moving soon)
• Student Conduct
• Project SAFE
• Talent Search / Upward Bound

20
SACS Report Keep Web Updated!

• The university is going through re-accreditation
  with SACS
• Our report has been sent to SACS, and contains
  many links
• Use re-directs for any URL changes
• Basic instructions for re-directs
• http//www.devon-worldwide.com/html/redirect.html
• Link checker
• http//validator.w3.org/checklink

21
PRR Compliance

• Policies, Rules Regulations (PRR)
• Web Compliance requires
• Disclaimer on Unit Home Page
• Disclaimer on any page containing and PRR
  information
• Avoid replicating PRR info send user directly to
  PRR site instead
• If necessary, you can paraphrase a PRR but
  official version must be linked
• Compliance all Division Websites by September
  30, 2003
• Help available contact Leslie

22
Thank You!