Answers.Body: <p>I'm not sure you'll find the email only contacts will really be noticed with day to day operations.  We have some, granted less then 5%, and I rarely come across them.</p>
  
  <p>Think about the kind of queries your users do with contacts, like using the quick search box in the upper left hand corner and what situations they would likely pull up a bunch of email only contacts.  You have to be searching for a name or email that matches an email only contact's email.  (When it does, I often find a matching contact.  The contact is fully in civi but they gave a different email address when getting on an email list.)</p>
  
  <p>I don't think there is a way to by default exclude them.  However, there are a number of ways you can make it easier to isolate them in queries.</p>
  
  <ol>
  <li>You can create a smart group of everyone else.  (query builder, individual, last name not null).  Then use that group for queries.</li>
  <li>You could usurp one of the privacy options if you aren't using it, like "Do not Phone" or "Do not trade" or "Do Not SMS" and exclude that option in advance query.</li>
  <li>You could create a new contact type for the email only; though, since it will be a child of individual, there might not be too useful.</li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-10T17:27:41.230Z
Answers.LastActivityDate: 2017-03-10T17:27:41.230Z
Answers.UserDisplayName: Paul-Tahoe
Body: <p>Does anyone have advice for how to run several mailing lists via Civicrm such that 'email only' contact records don't pollute the various search/reports/etc view?</p>
  
  <p>We've been debating moving our old lists to what is otherwise a great Civi/Drupal combination, but have been hesitant since many thousands of the contact records would be imported with only an email address. Unless I am missing a setting or something obvious, having these records would make things a tad awkward for users when navigating through various contact interfaces.</p>
  
  <p>Is there any way to set a default 'exclude email only' contact records or similar system wide setting?</p>
  
Tags: <contacts><email><mailing>
Title: How to Deal With Email Only Contact Records
ThreadText: # How to Deal With Email Only Contact Records
  
  (Asked by: username_0 on 2017-03-10)
  
  Does anyone have advice for how to run several mailing lists via Civicrm such that 'email only' contact records don't pollute the various search/reports/etc view?
  
  We've been debating moving our old lists to what is otherwise a great Civi/Drupal combination, but have been hesitant since many thousands of the contact records would be imported with only an email address. Unless I am missing a setting or something obvious, having these records would make things a tad awkward for users when navigating through various contact interfaces.
  
  Is there any way to set a default 'exclude email only' contact records or similar system wide setting?
  
  **Tags:** contacts, email, mailing
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-03-10. Score: 1 | Accepted answer
  
  I'm not sure you'll find the email only contacts will really be noticed with day to day operations. We have some, granted less then 5%, and I rarely come across them.
  
  Think about the kind of queries your users do with contacts, like using the quick search box in the upper left hand corner and what situations they would likely pull up a bunch of email only contacts. You have to be searching for a name or email that matches an email only contact's email. (When it does, I often find a matching contact. The contact is fully in civi but they gave a different email address when getting on an email list.)
  
  I don't think there is a way to by default exclude them. However, there are a number of ways you can make it easier to isolate them in queries.
  
  1. You can create a smart group of everyone else. (query builder, individual, last name not null). Then use that group for queries.
  2. You could usurp one of the privacy options if you aren't using it, like "Do not Phone" or "Do not trade" or "Do Not SMS" and exclude that option in advance query.
  3. You could create a new contact type for the email only; though, since it will be a child of individual, there might not be too useful.
  
  
  ---
  
  