Presentation on theme: "THE CONCEPTION AND GROWTH OF KMDATA. WHY – AT UNIVERSITY LEVEL Cross collection search Data about data queries Who used which books to teach across."— Presentation transcript:
WHY – AT UNIVERSITY LEVEL Cross collection search Data about data queries Who used which books to teach across campus Projects by county, congressional districts Age Impact Partners OSU faculty involved Search for building type built by, owed to OSU faculty, students, past or present. Unified, coherent, sanitized, contexualized result Sources include-KSA, OSU:pro(RiV), Alumni Data
WHY- SOME INTERNAL QUESTIONS. Enhance teaching Connect to carmen to provide cross collection search capacity for resources to educators Allow students to maintain tagged portfolio’s which becomes a source for longitudinal analytics Student advancements Allows students to be discoverable Allows outside companies to search for interns
CURRENT PLANS (GAPS) On launch of RiV, the external profile used by a vocal percentage of the OSU:pro users was gone. It had been planned from the outset to use KmData to provide this same profile. The XML feed of OSU:pro used by numerous sites around OSU will also not be supported by RiV. It had been planned from the outset to replace this with a similar, enhanced cross domain search powered service from KmData. This is in place now, and is being used by College of Engineering with VetMed and ASC communications following very close.
CHALLENGES Institutional buy-in Conveying discreteness of purpose DW vs KmData Vivo vs KmData RiV vs KmData Keeping a common purpose despite growth in stakeholders
STATUS ASC maintaining front end OCIO, LT managing the database OCIO-CETI creating the analytics engine Responding to challenges Focus on Academic data Vs ERP data 4 years of institutional data storage via OSU:pro Campus relationships resulting in rich data
CALL TO ACTION Need more developers Need use cases Need champions Need data sources