This flow is primarily used by data consumers who do not require a supplier to upload data on their behalf. Usually, the consumer will already have access to the data that has been previously sent via email or SFTP by the supplier. The consumer will then use this flow to upload the data to the datastore themselves.
We have improved the data upload process in the following ways:
Separating the upload dialogue from the mapping dialogue. The upload of the file operates in the usual way by choosing a file to upload and specifying file details.
Included the option for the consumer to specify who supplied the data to assist with the data audit trail. The user can choose to skip this by specifying "No" in the radio button dialogue, thereby indicating that they are both consumer and supplier of the data. Alternatively, the user can specify a known "Supplier Group" and a "Supplier Email" to which the data belongs.
For example, if I am uploading data to the datastore and I know it came from "Axe Capital" and more specifically "email@example.com" I can enter those details in the boxes provided. By doing this, we are logging the fact that "firstname.lastname@example.org" originally supplied the data even though I (as a consumer) am the one who is uploading it.
"email@example.com" will not be invited to the platform or notified in any way when we do this, the upload will be simply tagged with the supplier information. This is useful for audit trail purposes and keeping track of data provenance.
The "Complete" stage of an upload has been removed. Once data has been successfully mapped, the user will have the option to commit it directly to the datastore.
The updated upload flow is now accessible from the shortcuts on the datastore card and home.