Populating core data in Slate is an important task to ensure that record information is accurately recorded and displayed, however, currently enrolled student records can already exist in a shared database since those records flowed through the admissions process and ultimately enrolled. How long an institution has been using Slate and how long they retain certain data are key points of information to know. Consult your admissions team prior to moving forward.

Before becoming operational, the person record dataset must be populated with data from a legacy system (or other Slate database). The Upload Dataset tool will be used to import records to this dataset.  

As part of a comprehensive data migration strategy, the initial import to this dataset should be segmented into a hierarchy of data priority. The initial data import should only include core data elements such as:

• Unique Field (Colleague ID, EMPLID, Banner ID, etc.)

• Name

• Date of Birth

• Email

• Address(es)

• Phone

The first upload will establish the records in Slate. By including the unique field, subsequent imports will match directly on these existing records. Importing Current Person Data describes the complete process of importing core data.

Up next:

Stage 3: Build the Record and Process Architecture