Last Exported Date: the date when the record was last exported.Once a record has been exported, the following information on each record can be used to searching for previously exported items: Then, you can head to the Azure File Share, as configured by your application administrator, where you can find the exported data alongside a file called exportSummary.csv containing a summary of the export results. When the export is finished, you will receive an email notification confirming it has been completed. For CSV exports, select the fields to be included in the export, for VEO exports all the mandatory information required for the VERS standard is to be supplied. Complete the Additional Details section for your export.All Records: All records returned from your search.Selected Records Only: The records you manually selected from the search results.Select the format type that the records will be exported to, either CSV or VEO.That’s where you will need to provide the required information for your export: Click the Export button, you will see the slide bar.Note that you will be able to export all search results, even if all are not selected. Perform a search for the records you would like to export.The export feature is available from the Records365’s Advanced Search feature. For more information on security profiles and permissions, see Security Profiles. Alternatively, Record Visitors can be given the permission to Export Records through the use of Security Profiles. To Export Records you need to be assigned to the Application Administrator or the Records Manager role. Within the Export section, provide a Share Access Signature URL: a valid SAS for your Azure File Share.Under Configuration, click on General in the left hand navigation pane.With a user assigned the Application Administrator role click the Settings icon in the top right hand corner of Records365.To set the export location perform the following Please note, users with the Record Manager role can view the set value, but cannot set it. To prevent this risk, Records365 allows only those users with the Application Administrator role to govern the destination for all exported data. This can pose a risk, in that record metadata and content can be easily downloaded from Records365 en masse.

The act of performing an export can be carried out by all Records365 users.

Select Copy next to the URI field to copy to the clipboard as the URI will be required at time of export from Records365.

Permissions contains at least: Read, Create and Write.

Start time and Expiry Time are valid for time of export.

When generating the SAS please ensure the following:.

Download Azure Storage Explorer to generate a SAS (Share Access Signature) URL for the File Share.Create a File Share in the newly created Storage Account.Here are the steps to create a SAS link for an Azure File Share: As once written to the secured Azure file share, you can then issue a subsequent read-only SAS URL to the third party, eliminating the need to double handle the exported content in order for it to reach its final destination. For more information on SAS based access click here.Īzure file shares, when used with SAS based access allow you to easily transfer the exported content to other parties, like the National Archives. This allows for the greatest control and flexibility on securing the file share.

SAS is known as the best practice for externally accessing content in an Azure file share.

To access an Azure File Share, Records365 requires a Service based Share Access Signature (SAS) URL. As the customer you will be required to bring your own Azure Storage account for the exported content, to give you total control over the retention and access of the exported dataset. The type of storage supported is Azure file share, which is recommended for high performance scale application. The Records365 Export feature integrates with an Azure Storage account to provide the data in a secure, scalable and highly available manner. In order for Binaries to be exported as a VEO export, the tenant must have Content Protection turned on and the Binary needs to exist in Records365.

Teamsid export records