A data source key is a label that can be given to a set of data so that it can be handled in a single operation rather than having each record processed individually. You can create multiple data source keys and use them to load and process data in Blackboard.
how their students were performing on key learning outcomes. Their assessment data was generated from different sources, requiring a lot of administrative resources to compile and assess results through Excel and LMS-generated reports. These processes were time- and labour-intensive and lacked accurate reporting of information in many areas.
All data objects support the ability to alter the data source key for the grouping of that data set and may be used to alter the associated data source. This is not a required field in Framework based data feeds and unless noted the following examples assume the integration is configured to use a single data source.
Introduced in SP 12 is the ability to specify the Data Source in the data feed separately from specifying a new data source. See Data Source Key Management and the section on changing a membership record's data source. Notes on field mapping. Field mapping provides the ability to alter incoming data before it is stored in Learn.
The source key is a value that uniquely identifies a specific source record. In most cases — but not all — each source record has such a unique value. Source Key Field(s) is the field or set of fields that together contain the source key value.
Data Source Definitions The data source definition must contain information about the database and the server in which it is located. Different database management systems identify the databases in different ways.
What are Data Source Types?Databases.Flat files.Web services.Other sources such as RSS feeds.
Different Sources of Data for Data AnalysisThe actual data is then further divided mainly into two types known as: Primary data. ... Interview method: ... Survey method: ... Observation method: ... Experimental method: ... Internal source: ... External source: ... Other sources:Sep 10, 2020
The data your SIS provides contains a full snapshot of the PERSON s who should have access to Learn. This data contains PERSON records to add, PERSON records to update, and records which have been removed since previous REFRESH operations which should be handled appropriately per configuration (disable or purge). Additionally, all data in this refresh is targeted using the same data source as defined in the integration and you wish for only data related to this data source key to be affected.
If other membership records are managed another integration they will NOT be disabled or purged due to their absence in the above data feed unless they have the same data source as specified by the integration. COMPLETE REFRESH BY DATA SOURCE only operates on records matching the integration data source.
Field mapping provides the ability to alter incoming data before it is stored in Learn. This allows you to have complete control over the data that is stored and enables you to meet Learn specific rules when the SIS data you are provided is insufficient, such as the creation of a suitable membership name entry. When applied to a membership object field the associated script is run per membership record, altering or providing the data before it is stored in Learn. A full explanation of Field Mapping is provided in Snapshot Flat File Custom Field Mapping.
The first is to run STORE membership information resulting in the addition or updating of records as presented in the data feed. The Second is to REFRESH membership information already present in Learn resulting in the addition of new or updating of existing records as presented in the data file while disabling existing Learn records which are not present in the membership data file.
COMPLETE REFRESH performs two operations that amount to a comparison of the data in the feed file and the records in Learn owned by the integration: storing new records, updating existing records , or disabling records in Learn that are not in the data file.
Data may be provided to Learn and then subsequently updated, removed, or amended. Thus, you may start with the simplest data set and augment as your institution's data requirements change.
The data your SIS provides contains a full snapshot of the PERSON s who should have access to Learn. This data contains PERSON records to add, PERSON records to update, and records which have been removed since previous REFRESH operations which should be handled appropriately per configuration (disable or purge). Additionally, all data in this refresh is targeted using the same data source as defined in the integration and you wish for only data related to this data source key to be affected.
The first is to run STORE membership information resulting in the addition or updating of records as presented in the data feed. The Second is to REFRESH membership information already present in Learn resulting in the addition of new or updating of existing records as presented in the data file while disabling existing Learn records which are not present in the membership data file.
Field mapping provides the ability to alter incoming data before it is stored in Learn. This allows you to have complete control over the data that is stored and enables you to meet Learn specific rules when the SIS data you are provided is insufficient, such as the creation of a suitable membership name entry. When applied to a membership object field the associated script is run per membership record, altering or providing the data before it is stored in Learn. A full explanation of Field Mapping is provided in Snapshot Flat File Custom Field Mapping.
COMPLETE REFRESH performs two operations that amount to a comparison of the data in the feed file and the records in Learn owned by the integration: storing new records, updating existing records , or disabling records in Learn that are not in the data file.
Data may be provided to Learn and then subsequently updated, removed, or amended. Thus, you may start with the simplest data set and augment as your institution's data requirements change.