1. TIM Tools Admin Center
The Admin Center provides for management of the TIM Tools suite of applications.
- Admin Center Access
- Admin Center Dashboard
- Managing Zones (for Districts)
- Managing Zones (for Regional Service Agencies)
- Managing Zones (for Education Ministries, Consultants, Grantors, and Others)
- Managing Schools
- Uploading and Updating Members
- Profile Screen
- Changing Passwords
- Defining Roles (for Districts)
- Defining Roles (for School Licensees)
- Defining Roles (for Education Ministries, RSAs, Consultants, Grantors, and Others)
Working with Data
- Participation Overview
- Downloading ARTI Data
- Downloading TIM-LP Data
- Downloading TIM-C Data
- Downloading TIM-O Data
- Downloading TIM-R Data
- Downloading TUPS Data
The Technology Uses and Perceptions Survey provides essential information for planning technology infrastructure and support and identifying the perceptions and PD needs of teachers.
- TUPS Intro
- Opening and Closing the TUPS
- TUPS Intro and Closing Text
- Customizing TUPS Sections and Items
- Accessing School or District TUPS Data
- TUPS Report Template
3. TIM-O / TIM-LP / TIM-R
These three tools are for classroom observation, lesson plan review, and teacher reflection.
- TIM-O: Beginning an Observation
- TIM-O: Question-Based Method
- TIM-O: Matrix-Based Method
- TIM-O: Finishing an Observation
- TIM-O: Print or Share an Observation with a Teacher
- TIM-O: Editing Previous Observations
- TIM-O Report Templates
- Accessing School or District TIM-O Data
The TIM-C allows a coach and client to document the goals, activities, progress, and outcomes of a coaching cycle.
The ARTI tool provides a framework for teachers to design and conduct their own action research projects.
6. Report Tool
The Report Tool allows a school or district to create TIM-LP, TIM-O, TIM-R, or TUPS reports.
- Report Tool Intro
- Building a New Report
- View, Edit, or Delete Reports
- Interpreting TIM-O Report Data
7. Survey Tool
The Survey Tool allows a school or district to create internal or external surveys on new topics as needed.
- Survey Tool Intro
- Creating a New Internal Survey
- Creating a New Public Survey
- Adding Questions to Your Survey
- Customizing a Library Survey
- Viewing Survey Results
TIM Tools 6.1 Administration Guide
Application Programming Interface
Only Super Administrators have access to the TIM Tools API panel. In the Admin Center, select API Access and then Getting Started.
Get started by doing the following:
1. Register your instance with the TIM Tools API Interface and receive your client credentials. Your credentials will then be displayed as shown in the redacted area of Figure 1.
2. Use the Developer Registration section of the page to register your developer(s) for a key that entitles each developer to use those client credentials. If you register multiple developers, each one will have a unique developer key.
3.Click the button at the bottom of the page to the Developer Center for further instructions, demos and sample scripts.
Figure 1. Getting Started.
Developer Center Sign-In
The Developer Sign-In page will open in a new tab to facilitate copying and pasting of the client ID, client secret from your TIM Tools instance to the Developer Center. Developers use their registered email address and personal developer key to sign in here.
Figure 2. Signing in.
The developer homepage includes an overview and links to the API Inspector and Code Examples. You can also navigate (and sign out) using the links in the top menubar.
Figure 3. The developer homepage.
TIM-Tools API Inspector
The API Inspector provides an opportunity to enter client credentials and inspect the JSON returned from all endpoints. The inspector endpoint returns are limited to 5 records. Enter the API ID and API Secret into the text boxes and then click the Validate API Credentials button. The button will turn green upon validation.
Upon successful validation, the user can now click any of the six Get buttons to see what the JSON returned for sample records look like for the TIM-LP, TIM-O, TIM-R, TUPS, and Survey Tool.
Figure 4. The API Inspector.
Figure 5. Code Examples.