All data sharing and matching on Senate is governed by approval workflows in projects.
This article provides an overview of the end-to-end process for getting your data onto Senate through to making it available for matching and analysis in a project.
Click on any of the links below for an in-depth overview of each topic and relevant how-to guides.
Prior kicking off a data sharing and matching project on Senate, it is important to understand the legal, technical and team setup requirements for a project.
- Legal requirements: organizations involved in a data sharing project must have signed software-use terms (for use of Senate and Senate Matching services) and have a legal framework in place to govern the rights and responsibilities of each organization participating in a data share.
- Technical requirements: your organization is required install a Contributor Node to receive tokens and may need a SFTP client for data upload to Senate.
- Team setup requirements: projects will require delegation of tasks to one or more users to prepare data, project manage and approve data license terms on behalf of your organization.
- Data Republic does not allow any personally identifiable information (PII) on the Senate Platform. Therefore, any PII belonging to an individual must first be replaced with a random token.
- Using a Contributor Node, Data Custodians can upload PII to receive tokens so that each unique individual will be represented by a random token.
- Since data matching can be performed on a range of PI fields available, data matching rules must first be determined by organizations before PII can be prepared for upload and tokenization by the Contributor Node.
- Once tokens are received, data preparation on Senate typically involves uploading tokens and attribute data to Senate, creating database tables so that your data can be queried later, and packaging files and/or tables together for projects.
All data sharing and matching on Senate is managed via Projects, where one or more organization may be invited to collaborate.
- Projects enable organizations to discuss, draft and agree on data sharing and matching terms.
- Data sharing and matching terms are reflected in an online Data License (a legally binding contract between organizations once executed). A Data License outlines how data can be used and accessed on platform. It also provides rules around what is matched and what may be extracted off platform.
- Subject to data license approval, access to match results and datasets is typically granted via secure analytical Workspaces (with rigid controls in place for access, audit and governance).
- Once matching is complete, a token-pair match table is available. The table will display which two tokens have matched, and which fields they have matched on. For example, token A and token B matched on full name and mobile number, whereas token C and token D matched only on full name.
- Senate Matching Project Guide - an overview of project work streams for data preparation and project creation / management
- Senate Matching Technical User Guide - a detailed end-to-end guide covering Contributor node installing, through to getting your data onto Senate, setting up your project and requesting a data match.
- How does Senate Matching work - a 3 minute video on tokenization and hashing