October 2022
Canopy is defining a new term called Personally Unique Identifier, or PUID, for short. Personally Unique Identifiers are single or combined elements that are unique to a person, or likely to be unique to a person. One obvious example of a PUID is a Social Security Number. Another example is the combination of first name, last name, and date of birth. These elements are singled out in Canopy because their uniqueness is used for entity consolidation, as well as for propagating raw entity data entry. You will begin to hear us use this term and see it appear in our interface.
For those approved for our Beta program, we have added a new feature! Please contact Customer Success to have this feature added to your project.
Click here to read more about this Beta Feature.
In this release, we’ve included several improvements that will help you manage uploads better. You may now upload data straight from your AWS S3 Bucket, or directly from a MS Office 365 Mailbox.
We’ve improved the upload wizard to help you maintain consistency. Going forward, we will require all upload names to be unique. To help drive consistency, you may now choose from the list of previously created custodians, or create a new custodian.
Using AWS Pre-Signed URLs, you can transfer data directly from your AWS S3 bucket to your Canopy project. This is an AWS-to-AWS transfer of data that, once initiated, will continue to transfer data, even if you close your browser and turn off your computer.
You can read more about AWS S3 Pre-Signed URLs here: https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html
We will screen the URL for inconsistencies, or expiration, before initiating the transfer. If we detect that the Pre-Sign URL has expired, we will let you know immediately. Likewise, if we detect an issue with the bucket name, file name, or date, we will let you know that the URL is invalid.
By authenticating directly with Microsoft, you can initiate a cloud Azure-to-Amazon transfer that will continue to transfer data, even after you close your browser.
You can select one or more email boxes to upload directly from MS Office 365.
We have enhanced the Upload Dashboard to group files by upload, so you can more easily track upload progress.
What Does Processing Status Mean?
You may have noticed that when Processing Status is equal to Done, files queued for processing are not done. What Processing Status means on the Upload Dashboard is that the uploaded file has been opened. For example, if you upload a PST and the Processing Status equals Done, this means that all the EMLs are extracted. If you upload a zipped PST, however, then a Processing Status equal to Done means that the PST has been uncompressed from the Zip. We are working to improve the clarity and ease of use of this status in future releases.
You can also choose to display new fields, including S3 Bucket, Uploaded By, Upload Start Datetime, Upload End Datetime, and SHA256 Hash.
The de-duplication process should not miss duplicate files now. Previously, it was possible that some documents did not get de-duplicated when processing large volumes of data simultaneously, processing zips, or embedded objects.
Uploaded “transport” containers will always be extracted, even when “Extract Contents From Archive Files Such As Zips” is not selected.
Documents that are embedded objects indicate so in the document information panel. Documents that have embedded objects indicate so in the document information panel.
You will notice that the column selector for adding fields has been replaced with the new standard multi-select search component. Additionally, the column selector in the Master Entity has been replaced with the new standard multi-select search component.
When merging entities, only fields that are populated are displayed and require the user to make a decision. Previously, every entity field was displayed and required a decision, even if all fields were empty.
Now, the Entity Mapping validation notification specifies the correct fields with validation errors. Previously, the error message was hard coded to DOB, SSN, State, and Email.
For those of you who access multiple tenants in the same region, the tenant login page has been updated.