Data Republic’s Senate Platform revolutionises data sharing between organisations by providing comprehensive legal, governance and licensing workflows for companies when sharing data. Data Republic’s technology suite helps data owners to unlock the benefits of data sharing while protecting information security and data privacy.
This article covers key topics to get started on Senate.
- Setting up and participating in a data exchange project
- Tokenize PI for data matching
- Control how your data is accessed and shared in Senate
- Improve internal and external data discoverability using Data Listings
***Note: Organizations using Senate must first execute required legal agreements to access Senate and conduct an exchange. See Data Republic's legal framework.***
Setting up and participating in a data exchange project
- A project is created to govern your data exchange in Senate. Organizations requesting access to data will usually set up the project and invite users from data owner organization(s) to discuss a data sharing opportunity and participate in an exchange. Within a project, users can access 'conversations', create and negotiate data licenses, or connect to a workspace to access data if invited. Learn more about: Working with data custodians and how to define your data requirements for a project.
- A package referencing any data for exchange (i..e files, database tables / views) must be created by the data owner and added to the project to negotiate an exchange; a package contains references to where the meta data sits in Senate and does not contain the data itself. A data contributor term sheet must then be completed for any databases created as part of this process, to control how their data may be shared by Data Republic. For e.g. data sharing can automatically be approved for a,b,c organizations under a certain vertical, or alternatively, all data exchanges must require data license approval by the data owner organization within a project. A data license is different to the term sheet, as a data license specifies the exact permitted use for any projects requesting access to this data (see step 4 below).
- Note: Any data uploaded to Senate must be identified, or if data matching is required, PI must first be tokenized using a Contributor Node and tokens attached to relevant tables in the data package to request matching. See requirements to 'Tokenize PI for matching' below.
- A data license must be submitted and approved by the data governance manager from each organization before access to data can be provided. A data license contains agreed terms for permitted use of data, whether matching is allowed, pricing and data access terms.
- Depending on data sensitivity and the level of governance selected, data owners may require for analysis and/or token matching to take place in secure Discovery Workspaces (quarantined virtual machines) on Senate; whereby, any query run against the database is audited, and workspace access is controlled.
- Alternatively, a license may permit the data recipient to download raw data from Senate without the requirement of a workspace for analytics or any output checks.
Other useful information:
How to tokenize PI for matching
Data Republic’s Senate Matching technology provides an opportunity for organizations to match customer row data between data tables and unlock new insights about their customers without revealing or compromising PI. Organizations can install Contributor Node to tokenize PI and submit a data license request to complete a data match on Senate. Approval of the data license and match request is required by data governance managers from contributing organizations. Note: Tokenization is only required if you intend to request a data match in your project.
Controlling access to your data and how it is shared
There are two types of agreements in Senate, used to control how your data can be shared upon upload and creating a database (term sheet), and within a project for data exchange (data license).
Using Term sheets for databases: A term sheet describes expected data characteristics and conditions for access for any database you create as a data owner. A term sheet requires approval in Senate by your data governance manager as well as Data Republic before it can be effective. Note: No PII can be uploaded to the Senate Platform. Specific terms relating to exchange with particular organizations are included in a project's data license.
- Creating databases
- Creating and approving term sheets (for databases)
- Approval workflow for term sheets
Using Data Licenses: A data license is an agreement between an organization requesting access to data (i.e. data recipient / data licensee) and data owner organizations (i.e. data custodians). Terms such as permitted use of data, extraction rules, pricing and access must be agreed to, and approved by data governance managers from each organization, as well as Data Republic for the license to be effective.
- Creating and approving data licenses
- Approval workflow for data licenses
- What is a 'permitted use'?
- Working with data custodians
Improving data discoverability using Data Listings
Commercialize datasets by publishing your Data Listing to the 'Data Republic Open Catalog'. A Data Listing contains a description of the dataset as well as meta data to help analysts decide whether the dataset might be useful for their project.
Improving internal data discoverability: If your organization has licensed the Senate Platform, use the 'Closed Catalog' feature to improve internal data discoverability and innovation by allowing Senate users within your own organization to discover new datasets. Users within your organization can request access to datasets to collaborate in a project and solve insight problems.