My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 13 - Funding for Two Additional Years for a Learning Management System
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2025
>
06/17/2025
>
Item 13 - Funding for Two Additional Years for a Learning Management System
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/11/2025 4:43:45 PM
Creation date
6/11/2025 3:46:03 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Human Resources
Item #
13
Date
6/17/2025
Destruction Year
P
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
71
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
8. Additional Tasks: Historical Data Migration <br />The purpose of this task is to provide a Data Migration with the standard Meridian LMS <br />implementation services as depicted herein. The Legacy Data Migration (migration of user <br />historical transcript data to Meridian LMS), Meridian will support a one-way, inbound, one-time <br />Production data migration to import historical data based on the maximum record set of up to <br />100,000 records. <br />MERIDIAN Base Data Migration template. <br />Configuration of the Meridian LMS HRIS Tool <br />based upon the completed Requirements <br />Document specified in task B.2 above. <br />One pre -production load of a subset of <br />CLIENT production ready data for CAT <br />purposes. <br />One production load of full user data into the <br />CLIENT production environment. <br />One-way inbound Data Migration into the <br />Meridian LMS application only. <br />CLIENT cannot change the format of the Data <br />Migration XLS file template. <br />Meridian will load a subset of CLIENT <br />production ready historical data in the Meridian <br />LMS CLIENT Stage environment for testing <br />purposes. <br />Content is not included in -scope. <br />MERIDIAN will conduct and support five (5) <br />days of Customer Acceptance Testing for all <br />tasks defined in section B herein. <br />Upon completion of CAT, MERIDIAN will <br />perform a one-time full data load of CLIENT <br />production data in the Meridian LMS CLIENT <br />production environment. <br />Backfill and delivery of the one (1) flat <br />file to Meridian for processing: User <br />Data, Transcripts. <br />Data Migration completed and tested per <br />the Requirements specified in task B.2 <br />above, in the Meridian LMS CLIENT <br />Stage environment. <br />One (1) final data load in Meridian LMS <br />CLIENT Production environment. <br />9. Additional Tasks: Single Sign -On <br />The purpose of this task is to provide an Active Directory or SAML integration with the Meridian LMS <br />implementation. Setup is limited to the Meridian LMS application out -of -the -box solution for the <br />integration of Microsoft Active Directory services/LDAPISAML 2.0. <br />
The URL can be used to link to this page
Your browser does not support the video tag.