Wonde is a third party service for storing data elements from a school's Student Administration System (SAS). If your student administration system is supported by Wonde and your school's IT support engages the services of Wonde, then the Concord DataOps API can be enabled to retrieve data from Wonde and translate it into Infiniti and LibPaths profile data. Once set up, updates will run according to the schedule implemented by your IT Manager.

Limitations

Note: Current limitations in DataOps retrieve/import API are:

• student images cannot be imported (use autoSync in conjunction with DataOps)
• additional student email contacts cannot be imported (use autoSync in conjunction with DataOps)
• student study groups cannot be imported (use autoSync in conjunction with DataOps)

Basic Workflow

Data Source (e.g., SAS) --> Intermediate Data Broker (e.g., Wonde) --> Concord DataOps

Testing And Trouble Shooting

Best practice is to test, test, and test again prior to doing a live data transfer. A number of configuration options and tools are available to assist with checking data, mapping data, and testing the outcome of data transferred from SAS--> Intermediate Data Broker --> DataOps:

• manual import mode - test without saving
• subgroups to process - test data for selected subgroups of users
• barcode - set correct barcode mapping
• username mapping options
• SSO mapping
• email mapping options
• form class mapping options
• data inspection tools - Examine School and Download Raw
• Outcome Reporting

Wonde - Matching ILP and Wonde Data

Warning: The Wonde {matching field you select} is matched to ILP Username. This means that every record in Wonde must have a value for the selected data element and this value must match the Username in ILP for a successful transfer or update. Failure to check and confirm this prior to retrieving any data from Wonde will cause unexpected outcomes in the ILP records.

Before Getting Started

We recommend you read the DataOps Basic Mapping of Wonde Data To Infiniti and LibPaths and the Wonde-Infiniti Barcode Data Element Mapping in conjunction with these instructions and the instructions on Settings> Users > Import > Intermediation > before retrieving any data from Wonde. Note: The Intermediation instructions can only be accessed after Wonde has been authenticated.

DataOps Online Getting Started Guide

There are three (3) phases to step through when configuring DataOps to retrieve data from Wonde. We recommend you step through the DataOps online Getting Started Guide which is available on in the DataOps interface in Phase 2 and Phase 3. Note: The Intermediation instructions can only be accessed after Wonde has been authenticated.

There are four (4) separate sets of data elements that can make up a patron profile in ILP. The following will help your local IT Team to determine if the all the data elements required for the level of functionality you expect from ILP can be retrieved via Wonde.

The minimum data elements for each patron profile required by Infiniti to function effectively as a library management system are:

• unique patron username.
• patron first name or given name.
• patron last name or family name.
• patron email address (if you plan to email student notices). Note: This value can also be used to authenticate for single sign (SSO) on access to Infiniti.
• unique library barcode or a unique library loan identifier (if you want a patron to borrow items from your library):
  
  • use the barcode currently stored in Infiniti, or
  • a unique barcode value transferred from Wonde, or
  • the person's MIS ID stored in Wonde.
    Note: If you have printed barcode labels associated with each patron's account the value mapped as the unique library barcode must match the Infiniti patron account barcode to avoid reprinting barcode labels.
• academic level or cohort for students (to establish collection access and borrower rights and privileges for students).
• form class for students and group membership for teachers (to establish collection access and borrower rights and privileges for students and to prepare many circulation reports and emails, e.g., overdue loan reports).

Note: These data elements should be transferred from your single source of truth (SAS) to Wonde and then mapped to ILP using the DataOps Mapping Panel.

Warning: If your school uses physical barcode labels and the barcode data element you map does not match the physical barcode label for a patron, then physical barcode labels will have to be replaced.

The minimum data elements for each patron profile required by LibPaths to function effectively as a digital portal delivery system to support online delivery of digital resources to students studying, and teachers teaching, different subjects at different year levels are:

• unique patron username.
• patron first name or given name.
• patron last name or family name.
• patron email address. Note: This value can also be used to authenticate for single sign on access to Infiniti.
• academic level or cohort for students (to establish portal access and timetable synchronisation).
• form class for students and group membership for students and teachers (to establish portal access and timetable synchronisation).

If some of these data elements are not stored in or cannot be retrieved from Wonde and you want them in ILP, then they will have to be retrieved from another data source as a separate CSV import process. This can be done using the Concord autoSync functionality.

As part of a patron's extended library profile, Infiniti also stores:

• patron photos for circulation (.jpg and .png formats supported). Note: Wonde does not yet support image mime type identifiers to assist in transferring photos.
• student parent and guardian email addresses for communication. Note: Messages sent from Infiniti require specific configuration that cannot be delivered via Wonde. This can be done using the Concord autoSync functionality.
• library groups for determining Infiniti collection access and LibPaths portal access. This can be done using the Concord autoSync functionality. Note: You SAS and Wonde may not contain library group information. ILP may require library groups for management purposes.
  Note: These data elements are currently not available in Wonde and must be retrieved separately as CSV files if required using the Concord autoSync functionality.

Note: Data not available from Wonde can be recorded manually or imported automatically using the integrated Concord autoSync functionality.

Data Mapping For Wonde

As determined by your school Library Team and IT Team, data elements from your preferred data source, usually a SAS, will transfer to Wonde. At this point in the process the DataOps Module is unaware of these data elements and only becomes aware of the data source after the DataOps Module is activated.

Getting Started

1. Follow the instruction to submit a ticket for Concord support to commence the process.
2. Concord will respond using the support ticket.
3. Reply to pre-configuration questions sent from Concord.

Pre-Wonde Configuration - Phase 1

1. Go to: Settings> Users > Import > Intermediation
2. to access the DataOps online Getting Started Guide.
3. Wait to receive communication from Wonde and respond accordingly.
4. Reply to the Concord Import Questionnaire.
5. After receiving confirmation and account details from Wonde, Concord Support Team will:
   1. Configure your Wonde connection with information supplied directly by Wonde.
   2. Send further information for you to review before proceeding.

Retrieving Data From Wonde - Phase 2

1. School IT Team navigates to Settings > Users > Import > Intermediation.
2. - to open DataOps for Wonde configuration.
3. - for overview and instructions and configuration options.
4. Match This Wonde Field - select the Wonde data element that will match the ILP Username.
5. Barcode Treatment:
   1. Use Wonde Barcode Field - each borrower record in Wonde must include a borrower barcode. Note: Choosing this option means borrower barcodes must be recorded for all students and teachers in your SAS and must be correctly mapped from your SAS to Wonde.
   2. Derive From MIS ID - each borrower barcode will be changed or updated to be the same as their Wonde MIS ID. Note: Choosing this option means any barcodes printed on lists, on borrower ID cards, or stored on electronic ID cards will have to be reprinted or reloaded.
   3. Ignore Barcodes - no changes will be made to the borrower barcodes currently in Infiniti. Note: Choosing this option means the library manager must manually create and add barcodes for new borrowers before they can borrow. This will be a tedious and repetitive exercise.
6. Email Source Priority (Students) - choose from the available options.
7. Email Source Priority (Staff) - choose from the available options.
8. Form Class Source - choose from the available options.
9. Examine School:
   1. Wonde Data Examination - data tagged for retrieval if it is available in Wonde.
   2. Patron Samples - a random sample of three students (first row) and three staff (second row) will provide a guide as to the consistency of matching keys available in the Wonde data set. Note: The data element selected in Step 3 above Match This Wonde Field must be consistently populated for every record for it to be a suitable matching key between Wonde and ILP.
10. Download Raw - download raw data directly from Wonde as a Json file. Note: Raw data can be inspected to determine what data elements and values have been transferred from your SAS to Wonde.
    
11. Academic Levels - choose which academic levels will be processed.
12. Import Staff:
    1. - import staff
       1. Attach Staff Library Groups - attach staff to one or more library groups.
    2. - do not import staff.
13. Retrieve option Phase 2:
    1. Manual Test - school IT Team manually test data from Wonde. Note: Test Import will not make any changes to ILP data.
14. Retrieve options Phase 3:
    1. Manual Test/Import - school IT Team manually test or import data from Wonde. Note: Recommended best practice is to run a Test Import without making any changes prior to making live imports. 
    2. Auto - school IT Team will configure the DataOps scheduler to process data as per the chosen schedule Settings > Users > Import > Intermediation
       Note: Once transfers have been checked manually this option may be useful especially in schools with high student churn rate.
       

Manual Import

A manual importprovides the opportunity to test data retrieval results from Wonde to ILP without making any changes. A report is generated that predicts what changes will be made when a "live import" is run. Under some circumstances, a manual import can also be used to bulk change some data values in ILS.

1. Go to: Settings > Users > Import > Intermediation.
2. .
3.  .
4. Go to: Settings > Tasks > Completed to see review the recent history of manual Wonde imports (normal or simulated).

Outcome Analysis

A manual report is recommended for identifying inconsistencies in your data and correcting these prior to "live import" or scheduling Auto Import. A sample report after a test import will look similar to:

Report Legend

The numbers in each of the coloured dots represent:

• created - new records added. Note: The number of new records that will be added to ILP. This number should coincide with your expectations.
• updated - existing records modified. Note: The number of exiting records that will be modified in ILP during the import. This number should coincide with your expectations.
• skipped - records ignored. Note: The number of existing records that will be skipped or ignored during the import. You should inspect records that will be skipped and correct data accordingly.
• rejected - records rejected. Note: The number of records that will be rejected during the import. This number should always be 0. You should inspect each rejected record to see why it will be be rejected and correct if necessary. In Auto Import mode you will not be advised if records have been rejected.
• newly disable - existing records disabled. Note: The number of existing records in ILP that will be disabled during the import. This number should coincide with your expectations.

The resultant report will display a count of the number of records for each category with further information available for specific records by reviewing the list. Review message/s associated with the report and/or investigate records in individual categories to determine how/why a set of records have been categorised. Correct data in Wonde and/or ILP as required.

Post Auto Import Reports

Reports on the outcome of the last 100 automatic imports are logged. You can access and review these at Reports > Users > User Import Log.