Download
the faculty activity information reporting project n.
Skip this Video
Loading SlideShow in 5 Seconds..
The Faculty Activity Information Reporting Project PowerPoint Presentation
Download Presentation
The Faculty Activity Information Reporting Project

The Faculty Activity Information Reporting Project

118 Vues Download Presentation
Télécharger la présentation

The Faculty Activity Information Reporting Project

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. The Faculty Activity Information Reporting Project

  2. Objectives • Provide faculty with easy to use tool to document academic activities and generate digital CVs • Provide administrators with web-based reporting for P&T, faculty review, accreditation

  3. University of Missouri’s Current Faculty Accomplishment System (a.k.a. FAS) “Front Page” Courses Publications

  4. What’s been done (Step 1) • Consulted with campus provosts (UMAOs) & the Intercampus Faculty Council (IFC) • Directed environmental scan of industry

  5. Environmental Scan Results • Institutional status • We are not alone in this need • Examples of commercial apps • Activity Insight by Digital Measures • Faculty 180 by Data 180 • Research in View by Thomson Reuters • Pricing structures vary • By FTE or by unit

  6. What’s been done (Step 2) • Conducted focus groups & generated common themes • Presented findings of needs requested by faculty & administrators to the UMAOs & IFC

  7. Focus Groups • Conducted two per campus • faculty and administrative • Discussed current state of FAS • likes and dislikes • Generated common themes • FAS Focus Group Themes • Moving forward • wants, needs and concerns

  8. Themes

  9. Accountability • What is the purpose? • Our department has not accessed FAS in five or six years. • College looks at data but faculty get little feedback. • What are my incentives other than I won’t get my raise?

  10. Customization & the User Interface • Doesn’t fit faculty who do clinical teaching and community service. • Our faculty experience frustrationfrom having to choose from fields that are not intuitive and/or applicable. • We have someone in our office who does the data entry for our CVs because the user interface is so unfriendly. • Data entry was time consuming and slow. • There would be a value to have a system that could be customized to fit each department/division/unit.

  11. Functionality • The system should be able to import from internal/external databases • Musts haves include assessment, customizable, align with P&T process, annual reviews/reports, accreditation, etc. • Output to faculty web profiles. • It must generate a variety of CVs and bio-sketches. i.e. for NIH, NSF, full CV. • It should be able to function as a repository for file storage i.e. pdf, mp3, wav, doc, etc.

  12. Desired Features Identified

  13. Needs for Faculty • Generate Digital CVs • Follow P&T workflow steps • Generate Bio Sketches • Import Bibliographic Data • Import from External Databases • Direct feeds from UM Data • Maintain Document Repository • Auto-generate Web Profiles • NSF, NIH, USDA • EndNote, Ref Manager, Zotero • Scopus, PubMed, etc. • SIS, Grants, etc. • Syllabi, Recordings, etc.

  14. Digital Curriculum Vitae Example • Set CV reporting range for courses or select all • Output in Word, HTML or PDF • Hyperlinks to take you back to your profile • Use a template or select sections desired for CV

  15. Needs for Administrators • Customizable Reporting • Generate & Save Ad Hoc Reports • Accrediting Reports • P&T and Annual Faculty Reviews • Course Data Reporting • Grants & Publication Information

  16. What’s been done • Assembled a four-campus committee that: • drafted an Request for Proposals (RFP) • reviewed the proposals and vendor demonstrations • made a recommendation • Vetted recommendation with the IFC, UMAOs and general officers • Identified an IT project manager • Identified a project “champion” for each campus

  17. What’s left to do • Phase-In Implementation – Fall 2013 & Spring 2014 • Full Implementation – Summer 2014 & Fall 2014 (timeline subject to change)