experian_consumer_view 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: a2f9bc4cb3b7210d1974ad2558dbdfcd2ef74bb34b3fd4a493be72e1fae473dd
+  data.tar.gz: e31c691987efd36d8233ee176de48c6e588e91e5b2f47c273d250eb5c7a384dc
+SHA512:
+  metadata.gz: 03200c8c322988ad29fddaa6cf0a478e7831dcf282724cfa1da129dee8887c67b9b4d6a33dde1d72b9a7909a6c139bf7346eda67cf218d40f996835cfd874e53
+  data.tar.gz: 68cc86a3af3b91be3d74e845e654a632afc1629345b6f506dc72986af24fc290a94748be2174bf7f028edaa2c05a61b96710b59efb2dc0889c812eab62dac887

data/.gitignore

@@ -0,0 +1,11 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,28 @@
+# The behavior of RuboCop can be controlled via the .rubocop.yml
+# configuration file. It makes it possible to enable/disable
+# certain cops (checks) and to alter their behavior if they accept
+# any parameters. The file can be placed either in your home
+# directory or in some project directory.
+#
+# RuboCop will start looking for the configuration file in the directory
+# where the inspected file is and continue its way up to the root directory.
+#
+# See https://docs.rubocop.org/rubocop/configuration
+
+AllCops:
+  NewCops: enable
+
+Metrics/AbcSize:
+  Max: 34 # double the default
+
+Metrics/BlockLength:
+  Exclude:
+    - 'spec/**/*_spec.rb'
+    - '*.gemspec'
+
+Metrics/CyclomaticComplexity:
+  Max: 14 # double the default
+
+Metrics/MethodLength:
+  Max: 20 # double the default
+  CountAsOne: ['array', 'hash', 'heredoc']

data/.travis.yml

@@ -0,0 +1,6 @@
+---
+language: ruby
+cache: bundler
+rvm:
+  - 2.5.3
+before_install: gem install bundler -v 2.1.4

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at TODO: Write your email address. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [https://contributor-covenant.org/version/1/4][version]
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,6 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in experian_consumer_view.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,103 @@
+PATH
+  remote: .
+  specs:
+    experian_consumer_view (1.0.0)
+      activesupport (>= 5.2)
+      faraday (~> 1.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (6.0.3.3)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 0.7, < 2)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+      zeitwerk (~> 2.2, >= 2.2.2)
+    addressable (2.7.0)
+      public_suffix (>= 2.0.2, < 5.0)
+    ast (2.4.1)
+    codecov (0.2.11)
+      json
+      simplecov
+    coderay (1.1.3)
+    concurrent-ruby (1.1.7)
+    crack (0.4.4)
+    diff-lcs (1.4.4)
+    docile (1.3.2)
+    faraday (1.0.1)
+      multipart-post (>= 1.2, < 3)
+    hashdiff (1.0.1)
+    i18n (1.8.5)
+      concurrent-ruby (~> 1.0)
+    json (2.3.1)
+    method_source (1.0.0)
+    minitest (5.14.2)
+    multipart-post (2.1.1)
+    parallel (1.19.2)
+    parser (2.7.1.4)
+      ast (~> 2.4.1)
+    pry (0.13.1)
+      coderay (~> 1.1)
+      method_source (~> 1.0)
+    public_suffix (4.0.6)
+    rainbow (3.0.0)
+    rake (13.0.1)
+    regexp_parser (1.8.0)
+    rexml (3.2.4)
+    rspec (3.9.0)
+      rspec-core (~> 3.9.0)
+      rspec-expectations (~> 3.9.0)
+      rspec-mocks (~> 3.9.0)
+    rspec-core (3.9.2)
+      rspec-support (~> 3.9.3)
+    rspec-expectations (3.9.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.9.0)
+    rspec-mocks (3.9.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.9.0)
+    rspec-support (3.9.3)
+    rubocop (0.91.0)
+      parallel (~> 1.10)
+      parser (>= 2.7.1.1)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.7)
+      rexml
+      rubocop-ast (>= 0.4.0, < 1.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 2.0)
+    rubocop-ast (0.4.2)
+      parser (>= 2.7.1.4)
+    ruby-progressbar (1.10.1)
+    simplecov (0.19.0)
+      docile (~> 1.1)
+      simplecov-html (~> 0.11)
+    simplecov-html (0.12.2)
+    thread_safe (0.3.6)
+    tzinfo (1.2.7)
+      thread_safe (~> 0.1)
+    unicode-display_width (1.7.0)
+    webmock (3.9.1)
+      addressable (>= 2.3.6)
+      crack (>= 0.3.2)
+      hashdiff (>= 0.4.0, < 2.0.0)
+    yard (0.9.25)
+    zeitwerk (2.4.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 2.1)
+  codecov (>= 0.2)
+  experian_consumer_view!
+  pry (>= 0.12)
+  rake (>= 12.0)
+  rspec (~> 3.0)
+  rubocop (~> 0.91.0)
+  webmock (~> 3.9)
+  yard (~> 0.9.25)
+
+BUNDLED WITH
+   2.1.4

data/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020, 38 Degrees Ltd
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,319 @@
+# ExperianConsumerView
+
+ExperianConsumerView is a Ruby Gem client for the [Experian](https://www.experian.co.uk/) ConsumerView API. This is a product licensed by Experian, and as such this client is only useful if you have a license key for the ConsumerView API product.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'experian_consumer_view'
+```
+
+And then execute:
+
+    $ bundle install
+
+Or install it yourself as:
+
+    $ gem install experian_consumer_view
+
+## Usage
+
+### Basic example
+
+```ruby
+# Create the client
+# Experian will send your user_id, password, client_id, & asset_id when you purchase a license
+client = ExperianConsumerView::Client.new(
+  user_id: 'YOUR_USER_ID',
+  password: 'YOUR_PASSWORD',
+  client_id: 'YOUR_CLIENT_ID',
+  asset_id: 'YOUR_ASSET_ID'
+)
+
+# Lookup a single item from the API:
+result = client.lookup(search_items: { "MyPostcode" => { "postcode" => "SW1A 0AA" } })
+# result will be something like:
+# {
+#   "MyPostcode" => {
+#     "pc_mosaic_uk_7_group" => { api_code: 'A', group: 'A', description: 'City Prosperity' },
+#     "pc_mosaic_uk_7_type" => { api_code: '03', type: 'A03', description: 'Penthouse Chic' },
+#     "Match" => { api_code: 'PC', match_level: 'postcode' }
+#   }
+# }
+
+# Lookup a batch of items from the API:
+batch_result = client.lookup(search_items: {
+  "Postcode1" => { "postcode" => "SW1A 0AA" },
+  "Address2" => { "addressline" => "10 Downing Street", "postcode" => "SW1A 2AA" },
+  "Person3" => { "email" => "example@example.com" }
+})
+# batch_result will be something like:
+# {
+#   "Postcode1" => {
+#     "pc_mosaic_uk_7_group" => { api_code: 'A', group: 'A', description: 'City Prosperity' },
+#     "pc_mosaic_uk_7_type" => { api_code: '03', type: 'A03', description: 'Penthouse Chic' },
+#     "Match" => { api_code: 'PC', match_level: 'postcode' }
+#   },
+#   "Address2" => {
+#     "pc_mosaic_uk_7_group" => { api_code: 'A', group: 'A', description: 'City Prosperity' },
+#     "pc_mosaic_uk_7_type" => { api_code: '02', type: 'A02', description: 'Uptown Elite' },
+#     "Match" => { api_code: 'H', match_level: 'household' }
+#   },
+#   "Person3" => {
+#     "pc_mosaic_uk_7_group" => { api_code: 'O', group: 'O', description: 'Rental Hubs' },
+#     "pc_mosaic_uk_7_type" => { api_code: '66', type: 'O66', description: 'Student Scene' },
+#     "Match" => { api_code: 'P', match_level: 'person' }
+#   }
+# }
+```
+
+### Understanding what to pass to the lookup method
+
+Calls to `lookup` require the `search_items` named parameter - this is a hash of items to lookup in the API. Eg. as per the example above:
+
+```ruby
+client.lookup(search_items: {
+  "Postcode1" => { "postcode" => "SW1A 0AA" },
+  "Address2" => { "addressline" => "10 Downing Street", "postcode" => "SW1A 2AA" },
+  "Person3" => { "email" => "example@example.com" }
+})
+```
+
+The keys are arbitrary names you assign to each search item for reference. For example they could be the ID of a postcode or person in your application database. The example above uses "Postcode1", "Address2", etc.
+
+The values are the items you wish to search for in the API, in order to get demographic data about them. The ConsumerView API allows searching for demographic data at various levels, such as postcode, household, or an individual person. Each value must itself be a hash, as you can see in the examples above. They must contain a valid combination of search keys which the ConsumerView API supports. Eg:
+
+- Providing just a `postcode` would search for data at the postcode level.
+- Providing an `addressline` and a `postcode` would search for data at the household level.
+- Providing an `email` would search for data at the person level.
+
+There are other valid combinations of search keys - refer to the ConsumerView API Developer Guide. Note, search keys may change over time as the ConsumerView API changes.
+
+### Understanding what is returned from the lookup method
+
+Each successful call to `lookup` will return a hash containing the same keys as were provided in the `search_items` argument, as well as the results returned by the ConsumerView API for each search item.
+
+For example:
+
+```ruby
+client.lookup(search_items: {
+  "Postcode1" => { "postcode" => "SW1A 0AA" },
+  "Address2" => { "addressline" => "10 Downing Street", "postcode" => "SW1A 2AA" },
+  "Person3" => { "email" => "example@example.com" }
+})
+
+# Outputs something like:
+{
+  "Postcode1" => {
+    "pc_mosaic_uk_7_group" => { api_code: 'A', group: 'A', description: 'City Prosperity' },
+    "pc_mosaic_uk_7_type" => { api_code: '03', type: 'A03', description: 'Penthouse Chic' },
+    "Match" => { api_code: 'PC', match_level: 'postcode' }
+  },
+  "Address2" => {
+    "pc_mosaic_uk_7_group" => { api_code: 'A', group: 'A', description: 'City Prosperity' },
+    "pc_mosaic_uk_7_type" => { api_code: '02', type: 'A02', description: 'Uptown Elite' },
+    "Match" => { api_code: 'H', match_level: 'household' }
+  },
+  "Person3" => {
+    "pc_mosaic_uk_7_group" => { api_code: 'O', group: 'O', description: 'Rental Hubs' },
+    "pc_mosaic_uk_7_type" => { api_code: '66', type: 'O66', description: 'Student Scene' },
+    "Match" => { api_code: 'P', match_level: 'person' }
+  }
+}
+```
+
+In this example, the keys "Postcode1", "Address2" & "Person3" were provided in the `search_items`, so these are also be used as the keys in the result hash.
+
+Each search item has a hash containing all the data returned by the ConsumerView API for that search item. For example, here we can see each search item has the mosaic group (`pc_mosaic_uk_7_group`) & type (`pc_mosaic_uk_7_type`), as well as the match level (`Match`).
+
+If a search item is not successfully looked up in the Experian API, that search item will have an empty hash.
+
+Note, your license with Experian will determine the exact attributes the ConsumerView API will return. Refer to the ConsumerView API Variables and Propensities Reference Guide for details on what is available, and all possible values.
+
+#### Mapping attributes
+
+By default, some attributes are automatically transformed from single values into richer objects.
+
+In the example above, the ConsumerView API returned `pc_mosaic_uk_7_group`, `pc_mosaic_uk_7_type`, and `Match` attributes. For the "Postcode1" search item, the raw values from the API would have been `A`, `03`, and `PC` respectively - these are not very informative.
+
+Instead, they have been automatically transformed into richer hashes containing more meaningful information - eg. we can see from the richer hashes that the mosaic group `A` means "City Prosperity", and the mosaic type `03` means "Penthouse Chic".
+
+See the [Transformers::Attributes classes](lib/experian_consumer_view/transformers/attributes) to see exactly which attributes are transformed, and how.
+
+Attributes without transformers will still be returned, but they will just have the raw value from the API.
+
+_You can also apply custom transformations to the data returned by the ConsumerView API, in order to automatically transform the data into a richer or more useable format for consumption by your application. This is described further in the advanced useage section of this documentation._
+
+#### The Match attribute
+
+Note that `Match` is a special attribute which is always returned if the search was successful, and indicates at what level a match was found.
+
+For example, if searching for a household, it may be that demographic data for the specific household could not be found, but demographic data for the postcode was found, in which case the `Match` attribute would be 'PC' (postcode) rather than 'H' (household).
+
+## Advanced Useage
+
+### Providing a token cache
+
+If you are using this code in a multi-server / cloud-based setup, then it is recommended that you override the default in-memory token cache. A distributed cache, eg. Redis, is recommended.
+
+Using the in-memory token cache in such environments may lead to multiple servers logging into the ConsumerView API with the same credentials, invalidating the others' API tokens.
+
+You may override the default by initializing the `Client` with the `token_cache` option. This must be an `ActiveSupport::Cache` object.
+
+For example, in a Rails app, if the default Rails cache has already been configured to use a distributed cache like Redis, you may use:
+
+```ruby
+client = ExperianConsumerView::Client.new(
+  user_id: 'YOUR_USER_ID',
+  password: 'YOUR_PASSWORD',
+  client_id: 'YOUR_CLIENT_ID',
+  asset_id: 'YOUR_ASSET_ID',
+  options: { token_cache: Rails.cache }
+)
+```
+
+### Using a non-standard API URL
+
+This can be useful if you need to test your code, eg. against Experians Staging server. Override the default URL by initializing the `Client` with the `api_base_url` option:
+
+```ruby
+client = ExperianConsumerView::Client.new(
+  user_id: 'YOUR_USER_ID',
+  password: 'YOUR_PASSWORD',
+  client_id: 'YOUR_CLIENT_ID',
+  asset_id: 'YOUR_ASSET_ID',
+  options: { api_base_url: ExperianConsumerView::Api::STAGING_URL }
+)
+```
+
+### Mapping / transforming the returned data
+
+By default, this gem maps _some_ of the raw attributes returned by the ConsumerView API into richer objects for ease of use by other applications.
+
+However, you can provide your own transformer by initializing the `Client` with the `result_transformer` option.
+
+#### Turning off result transforming
+
+Transforming will have some performance impact. If you just want the raw data provided by the API, then use the provided `NoOpTransformer`.
+
+```ruby
+client = ExperianConsumerView::Client.new(
+  user_id: 'YOUR_USER_ID',
+  password: 'YOUR_PASSWORD',
+  client_id: 'YOUR_CLIENT_ID',
+  asset_id: 'YOUR_ASSET_ID',
+  options: { result_transformer: ExperianConsumerView::Transformers::NoOpTransformer.new }
+)
+
+result = client.lookup(search_items: { "MyPostcode" => { "postcode" => "SW1A 0AA" } })
+# result will be something like:
+# { "MyPostcode" => { "pc_mosaic_uk_7_group" => "A", "pc_mosaic_uk_7_type" => "03", "Match" => "PC" } }
+```
+
+Note that the results will still be parsed from a JSON String into a Ruby Hash, which will be keyed on the search item keys. If you want the _completely_ raw API results, you may use the `ExperianConsumerView::Api` class directly.
+
+#### Using your own attribute transformers
+
+If you simply want to transform more attributes, or transform them in a slightly different manner, you can use the provided `ResultTransformer` as a base, and register as many custom attribute transformers as you wish on it.
+
+Each attribute transformer must provide an `attribute_name` method, and a `transform_attribute` method, and examples can be seen in the [Transformers::Attributes module](lib/experian_consumer_view/transformers/attributes).
+
+New attribute transformers can be easily created by extending `ExperianConsumerView::Transformers::Attributes::Base`, but this is not required as long as the necessary methods are implemented.
+
+An example of creating & using a custom attribute transformer:
+
+```ruby
+class CustomAttributeTransformer
+  def attribute_name
+    "p_head_of_household"     # Transform attributes returned by the API with this name
+  end
+  def transform_attribute(value)
+    case value
+    when '0'
+      'Not head of household' # The API Code of 0 means 'Not head of household'
+    when '1'
+      'Head of household'     # The API Code of 1 means 'Head of household'
+    else
+      'Unclassified'          # Any other API Code means 'Unclassified'
+    end
+  end
+end
+
+my_result_transformer = ExperianConsumerView::Transformers::ResultTransformer.new
+my_result_transformer.register_attribute_transformer(CustomAttributeTransformer.new)
+
+client = ExperianConsumerView::Client.new(
+  user_id: 'YOUR_USER_ID',
+  password: 'YOUR_PASSWORD',
+  client_id: 'YOUR_CLIENT_ID',
+  asset_id: 'YOUR_ASSET_ID',
+  options: { result_transformer: my_result_transformer }
+)
+
+result = client.lookup(search_items: { "PersonA" => { "email" => "example@example.com" } })
+# result will be something like this (assuming your license gives access to "p_head_of_household"):
+# {
+#   "PersonA" => {
+#     "p_head_of_household" => 'Head of household',
+#     "pc_mosaic_uk_7_group" => 'G',
+#     "pc_mosaic_uk_7_type" => '28',
+#     "Match" => 'P'
+#   }
+# }
+```
+
+#### Using a completely custom result transformer
+
+If you want _complete_ control of how the result hash is transformed, you may implement your own result transformer.
+
+A result transformer has to provide the `transform` method. This must accept a hash which is the parsed JSON for a _single_ search item, and should return the transformed hash for that search item.
+
+A simple example:
+
+```ruby
+class CustomResultTranslator
+  # Exact attributes will depend on the Experian license, but input will be something like this...
+  # { "pc_mosaic_uk_7_group" => "A", "pc_mosaic_uk_7_type" => "02", "Match" => "PC" }
+  def transform(result_hash)
+    new_hash = {}
+    # Discard the Match attribute, then transform keys from Strings into symbols
+    result_hash.select { |k| k != 'Match' }.each { |k,v| new_hash[k.to_sym] = v }
+    new_hash
+  end
+end
+
+client = ExperianConsumerView::Client.new(
+  user_id: 'YOUR_USER_ID',
+  password: 'YOUR_PASSWORD',
+  client_id: 'YOUR_CLIENT_ID',
+  asset_id: 'YOUR_ASSET_ID',
+  options: { result_transformer: CustomResultTranslator.new }
+)
+
+result = client.lookup(search_items: { "MyPostcode" => { "postcode" => "SW1A 0AA" } })
+# result will be something like:
+# { "MyPostcode" => { pc_mosaic_uk_7_group: "A", pc_mosaic_uk_7_type: "03" } }
+```
+
+## License
+
+[MIT License](LICENSE.md)
+
+Copyright (c) 2020, 38 Degrees Ltd
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/38degrees/experian_consumer_view. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](CODE_OF_CONDUCT.md).
+
+
+## Code of Conduct
+
+Everyone interacting in the ExperianConsumerView project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](CODE_OF_CONDUCT.md).