First Learning Outcome: How to identify what information you need for each type of document.
Second Learning Outcome: The steps involved in getting data to your SIS and response data back from it.
Third Learning Outcome: Issues to look out for, and ways to handle unexpected outcomes.
Intended Audience: Some experience in the profession
Presenter(s):
Chris LeBlanc University of Oregon
From PDF to SIS to Document Imaging: Getting Partner Documents into Your Systems
Category
Technology > Session
Description
This session will be looking at how the University of Oregon went from merely downloading PDF documents from Parchment and the Common App, to updating application checklist information in Banner SIS, and uploading documents into their Document Imaging system with metadata/index values included.
This will review the process used to identify what information will be needed and how to get that information from each source. For Parchment, this involves their SFTP download offering and the index file that is included with it, and for Common App this was the information included in the file names of each document of their "Support Documents" download.
We will look at the overall process, including:
1. How documents are retrieved and how it differs for each source.
2. Getting the data needed for matching documents with students.
3. The process that takes the data and both updates the application checklist, and returns our student ID for the student.
4. Sending the document into our Document Imaging system with student ID, document type, and other metadata values included.
5. What issues can arise, and how we designed around them.
We will also explore some alternatives to our process, mostly focused on what a Document Imaging system could do that our process does right now.
Submission ID:
5232
Day:
Tuesday, July 16, 2019
Time:
8:00 AM - 9:00 AM
Room:
Milano VI