Here's a list of answers to some of the most frequently asked questions about Data Studio.
| Question | Answer | More info |
|---|---|---|
| What hardware is required to run Aperture Data Studio? | This depends on the number of users and volume of data. We have minimum recommendations based on some common use cases. | Technical recommendations |
| What volumes of data can be processed? | We test complex Workflows with millions of records. Ultimately, it depends on your hardware and setup. | Large workload recommendations |
| Question | Answer | More info |
|---|---|---|
| Does Data Studio protect against unauthorized access and modification of individual columns and rows? | Yes. Using Views, the same data can be presented to specific users differently without needing to modify the underlying data. Each View can have columns hidden or included with the sensitive values obfuscated. Advanced filters can also be applied to limit the rows included in a View. Users are automatically warned before sharing data that could contain sensitive/PII-type values. | Users and roles/ Create Views |
| Does Data Studio allow partitioning of data sets and user groups? | Yes, each Dataset is associated with a Space and an Environment. Access is controlled by assigning users/groups specific roles within a given Environment and permissions to Spaces within that Environment. | Users and roles/ Manage Spaces |
| Does Data Studio provide easy access via User Interface (UI) to timestamped history of configuration changes? | Partially. Data processing Workflows and Functions are versioned with the version history visible in the UI. Versions can also be reverted as needed. The application configuration is not versioned, only the current state is retained. Access to change these settings is restricted by role, and it's expected that users creates backups of configuration before making changes. | N/A |
| Can access to software configuration settings be limited? | Yes, granular access controls can be defined and roles created to restrict access to administrators/different levels of administrator. The lowest level of server settings requires physical access to the server to make changes. | Users and roles/ Install and configure |
| Does Data Studio log information of who did what and when? | Yes. Audit information is generated, allowing you to track information such as:
|
Audit usage |
| What logging/audit information is available? | You can customize the levels of logging and audit the usage depending on your requirements. | Audit usage/ Configure logging |
| Do objects have a version history/can changes be reversed? | Yes. You can revert Workflows, Views and Functions to a previously published version. This also allows you to test changes in your own Space without affecting the published objects. | Manage versions |
| What user authentication options are visible? | In addition to an internal authentication mechanism, Data Studio can be configured to authenticate using an LDAP server or an identity provider like Okta or Azure Active Directory using SAML v2.0. | Choose authentication/ Set password policy |
| Can different users have different levels of access? | Yes. Data Studio provides a lot of flexibility in defining users, roles and access permissions that work for you. | Users and roles |
| Can users have different levels of access to the same data? | Yes. This can be achieved using Views | Create Views/ Share data selectively |
| Does Data Studio use HTTPS to transmit data securely? | Yes. The administrator should change the port and apply an SSL security certificate on installation. | Add SSL certificate |
| Can data stored on disk be encrypted? | Yes. Enable the encryption option in Security settings. Note that there may be performance degradation associated with encrypting on-disk resources. | N/A |
| Question | Answer | More info |
|---|---|---|
| How can changes be synched between different environments? | Data Studio uses lightweight .dmx files to easily transfer objects such as Workflows between different Environments. These files (typically only kilobytes in size) can be "checked in and out" of your version management system (e.g. Git, VSTS, TFS). | Migrate metadata/ Manage Environments |
| Can changes be made in a test environment before being pushed to a different production installation? | Yes. | Manage Environments |
| What's the product upgrade process? | Upgrades are typically undertaken when a customer identifies a compelling reason, such as new functionality, significant performance improvement or fix. Version upgrades are low-impact and designed to avoid breaking changes. Downloading the latest installer opens a wizard to guide the user through the upgrade process which will pick up any configurations from the previous version. | N/A |
| How frequently is the product updated? | Data Studio is being continually developed and improved. Generally, weekly releases introduce enhancements and bug fixes with quarterly major releases with additional features and functionality. | Community site (requires sign up/in) |
| Where can I view release notes? | See previous release details and download the latest version from our community site (requires sign up/in). | N/A |
| How do I request feature enhancements? | You can make suggestions through your Experian contact, within Data Studio using the feedback option or via our community site. Use the community to see existing requests or to gather additional support for your suggestion. | N/A |
| How are feature enhancements prioritized? | Requests are aligned with the focus and intent that we have in mind for the product in core markets and then prioritized regularly using the RICE scoring methodology. Your Experian contact can provide an updated roadmap of planned enhancements (with the caveat that longer term items are subject to change). | Product roadmap |
| Does Data Studio have any AI/machine learning capabilities? | Yes, for both out-of-the-box data tagging (which is customizable) and as part of the training for Find duplicates functionality and matching rule optimization. | N/A |
