Developing Electronic Resources for SACS Reaffirmation of Accreditation SACS Leadership Team Meeting September 1, 2010.

Slides:



Advertisements
Similar presentations
By: Edith Leticia Cerda
Advertisements

Follow-up Reporting Expectations MSCHE Annual Conference 2009 Mary Ellen Petrisko.
National Database Templates for the Biosafety Clearing-House Application (NDT-nBCH) Overview of the US nBCH Applications.
The Electronic Office Some supplementary information Corporate websites Office automation Company intranet.
© NHS Institute for Innovation and Improvement, 2012 Baseline Data Collection Guide for Project Managers and Facilitators updated Feb 2012.
Updating Web Sites for Western Engineering August, 2011.
How to Document A Business Management System
Laura Noll Research Compliance Manager Radford University.
Objective Understand web-based digital media production methods, software, and hardware. Course Weight : 10%
Compliance Assist! Refresher Instruction Guide Accreditation Module.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Confidential property of Belkin International. Unlawful to copy or reproduce in any manner without the express written consent of Belkin International.
Course Outline Process Overview for Course Convenors.
Technical Writing II Acknowledgement: –This lecture notes are based on many on-line documents. –I would like to thank these authors who make the documents.
DoW text: Task and WP leaders will prepare syntheses reports of the project progress, its results and its implications. These synthesis reports will be.
THE BUSINESS OF IT PRODUCT FOCUS 7/7/14 – 7/18/14.
IWebFolio Using a Template Tutorial Images in this tutorial:
PM Summit Overview Daniel Vitek MBA, PMP – Consultant to CDC.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
Software Development, Programming, Testing & Implementation.
Submitting Book Chapters via Manuscript Central A Short Guide for Wiley-VCH Authors.
Facilitator Guide Template
Website Content, Forms and Dynamic Web Pages. Electronic Portfolios Portfolio: – A collection of work that clearly illustrates effort, progress, knowledge,
COPYRIGHT © 2008 – APEX SOFTWARE LTD. ALL RIGHTS RESERVED Human Resources COPYRIGHT © 2008 – APEX SOFTWARE LTD. ALL RIGHTS RESERVED CATEGORY FUNCTION Why.
Welcome to the Southeastern Louisiana University’s Online Employment Site Applicant Tutorial!
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Making Web Content Accessible to Everyone Web Accessibility Team June 9, 2015.
XHTML Introductory1 Linking and Publishing Basic Web Pages Chapter 3.
SACS Reaffirmation Project Compliance Certification Team Leaders Meeting Friday, August 27, – 11:00AM 107 Main Building Jennifer Skaggs, Ph.D. SACS.
Dreamweaver Domain 3 KellerAdobe CS5 ACA Certification Prep Dreamweaver Domain 6 KellerAdobe CS5 ACA Certification Prep Dreamweaver Domain 6: Evaluating.
SACS Reaffirmation Project Compliance Certification Team Orientation Compliance Certification Report Thursday, September 30, – 11:00AM 209 Main Building.
1 © Netskills Quality Internet Training, University of Newcastle Web Page Design © Netskills, Quality Internet Training University.
Henrietta O’Connor Online Questionnaires and Technical Guide.
Surviving SACS The Librarian’s Role in Reaccreditation North Carolina Library Association October 17, 2007.
Web Page Design. Some Terms Cascading Style Sheet, (CSS) –a style sheet language used to describe the look and formatting of a document written in html;
Hunter Valley Amateur Beekeepers Forum User Guide Guide shows sample screenshots with most relevant actions. Website is at
CCHD Grant Application Using the Online System. Sign In to the Online System Enter you complete address If this is your first time using CCHD’s.
Instructional Plan | Slide 1 AET/515 Instructional Plan December 17, 2012 Kevin Houser.
Institutional Considerations
User Documentation. User documentation  Is needed to help people (the users) understand how to use a computer system or software application, such as.
Submitting Course Outlines for C-ID Designation Training for Articulation Officers Summer 2012.
SACS Compliance Certification Orientation Meeting June 23, 2008.
RDA Toolkit Demonstration. Overview Accessing the Toolkit Navigating the Toolkit Understanding the functionality of the Toolkit Searching the Toolkit.
SACS Reaffirmation Project Compliance Certification Team Orientation Overview Thursday, September 30, – 11:00AM 209 Main Building – Lexmark Public.
Branding E-learning Innovations Project Outputs. Purpose of this session This session will provide E-learning Innovations Teams with guidelines around.
2013 Quality Systems Assessment Using the web-based self assessment application.
March 7, 2008 Web Advisory Committee. Overview of Presentation Completed Activities –Campus Survey of Web administrators –Assessment of the current Common.
1 PRINCIPAL INVESTIGATOR USE OF THE ST ScI ELECTRONIC GRANTS MANAGEMENT SYSTEM January, 2001.
User Documentation. Documentation Guidelines  Break the documentation down by tasks  Plan for an audience  State the purpose of the document  Organize.
The Good, the Bad & the Ugly: Style and design in Website creation Chris Webster: Information Officer and Website Manager at the EARL Consortium for Public.
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
“Are We Missing the Mark?” WELCOME Bill Lefevers Western Piedmont Community College.
Understanding Web-Based Digital Media Production Methods, Software, and Hardware Objective
Session 6: Data Flow, Data Management, and Data Quality.
GMAP Grant Management, Application, and Planning Consolidate Application Training.
SurveyDIG 2.1 Tutorial. Tutorial Contents Introduction Introduction Item Groups Item Groups –Creating new Groups –Naming Convention –Searching/Editing.
ICAD3218A Create User Documentation.  Before starting to create any user documentation ask ‘What is the documentation going to be used for?’.  When.
MODULE 6 Use of Web-based Programmatic Information 1 CAPTE: On-site Reviewer Training This module will cover the special issues related to handling electronic.
FINAL PRESENTATION 25% of Your Total Grade. PRESENTATION INSTRUCTIONS Give a short presentation based on one of the main topics from the text (the topics.
BE ABLE TO SELECT AND APPLY FAULT REMEDIES TO IT SYSTEMS.
Open Math Module Welcome Welcome to the “Open Math – Open Resources: Engage Adult Learners for 21 st Century Skills” course! Use the navigation buttons.
Presentation Graphics
Core Competencies: Summative Self-Assessment
Lippincott Procedures Training Tour for HealthStream Users
USER AND TECHNICAL DOCUMENTATION
Objective Understand web-based digital media production methods, software, and hardware. Course Weight : 10%
Lippincott Procedures Training Tour for General Users
Academic Presentations
Accessible Design Top 10 List
Training Tour for General Users
Presentation transcript:

Developing Electronic Resources for SACS Reaffirmation of Accreditation SACS Leadership Team Meeting September 1, 2010

SACS Guidelines  It is important to consider:  What type of electronic formatting will be used  Flow of information – electronically  Assurance of user-friendly access for the off-site reviewers  Dedicated electronic materials submitted for reaffirmation may not be altered after the institution submits its Compliance Certification Report. 2 SACS Leadership Team Meeting 9/1/10

Choosing a Format  Access  A web-based version is most easily accessed by a wide variety of people.  Various techniques may be used to limit what information is accessible for different audiences (e.g., password protection, separate servers, etc.).  Currency  While websites provide current information, link addresses may change. It is necessary to “freeze” the presentation website after submission (e.g., alternative website, CD/DVD). 3 SACS Leadership Team Meeting 9/1/10

Review of Institution’s Technical Capabilities  Resources  The goal is to have simple and effective access for the reviewers that does not distract from the materials submitted.  Institutions should use widely available software packages  Electronic versions should be.html or.pdf formats  Web-based solutions should be browser-independent An alternative medium must be provided in case the technology does not work at the time of the review. 4 SACS Leadership Team Meeting 9/1/10

Review of Institution’s Technical Capabilities (continued)  Personnel and Expertise  Must have individuals able to:  Program web-sites  Format (and debug) documents and final reports  Provide appropriate and current links  Generally ensure information appears and functions properly 5 SACS Leadership Team Meeting 9/1/10

Review of Institution’s Technical Capabilities (continued)  Training  All persons involved in the development of compliance materials should be trained in the software skills needed – this allows for integration of technology into normal institutional processes.  Training and support staff need to be in place to facilitate this process – the earlier this is implemented, the sooner electronic formats, documents, and links can be effectively put into practice.  Volume  Due to the immense amount of materials needed to present the information, all materials should be produced using the same medium. The institution should not have links to documents not on the same medium. 6 SACS Leadership Team Meeting 9/1/10

Electronic Design Recommendations These recommendations have been found by SACS to be common, accessible, useful and least likely to lead to problems.  Navigation  Reviewers should encounter a user-friendly introduction that guides them through the process.  A reviewer should initially see a short description of the process, followed by a step-by-step guide to using the materials.  It should be easy for the reviewer to navigate forward or return to previous locations without needing to learn any other computer techniques.  A simple point and click menu should make it apparent to any user exactly what to do at each step of the process. 7 SACS Leadership Team Meeting 9/1/10

Electronic Design Recommendations (continued)  General Design  Keep it simple  Keep the number of levels to a minimum.  Be consistent  Keep all the organization and style the same – don’t worry about trying to “spice it up”.  Maintain specificity and relevancy of documents and narratives.  State clearly and obviously which judgment of compliance your institution has identified for each requirement and standard and be sure the text addresses only that particular standard.  Know that cross references to compliance narratives for other requirements or standards may be used if applicable.  Always consider the use of simple navigation. 8 SACS Leadership Team Meeting 9/1/10

Electronic Design Recommendations (continued)  Organization  The flow of information is an important consideration, and the heart of the presentation is the compliance narrative.  Main page should provide an overview and basic arrangement of information available.  SACS recommended guidelines would be to have links to the following three categories:  The Institution and Instructions  Resist the temptation to provide public relations materials.  SACS Template Example SACS Template Example  Compliance Reports  This is the entry to convincing compliance narratives arranged by requirements and standards.  SACS Compliance Certification example SACS Compliance Certification example  Document Directory  Allows for reviewers to directly access the full referenced documents and databases without having to go to each report.  SACS Index of documents example SACS Index of documents example 9 SACS Leadership Team Meeting 9/1/10

Best Practice Examples  Southeastern Louisiana  Combined SACS Campus Website with Compliance Certification Report   Prairie View A & M  Separate SACS Campus Website and Compliance Certification Report    Albany State  Compliance Certification Report with use of CD for protected information  SACS Leadership Team Meeting 9/1/10

Action(s) Needed:  Identify technical resources  Determine and implement technical strategy 11 SACS Leadership Team Meeting 9/1/10