The info source field is missing when adding/editing addresses. This field is useful for letting us know where the address information came from. In turn, tracking this can give us insight about both the reliability of the address information and the reliability of the source.
This field is really needed and I hope added to the webview soon.
As is the COUNTY and I know there is a voteable option for that topic so please all, vote for that one as well! Thanks
So important!
totally agree with JohnDeMarce
Make all the Database View fields available in Web View. It's really that simple.
Documentation and transparency are critical when it comes to making data updates, and this is a piece of data that should be structured into a picklist. Omission of this field forces users to add notes and other unstructured data that is more time consuming and causes more challenges to isolate.
As we use DBV less and less to prepare for its retirement, this is important for working through mailing issues and conflicting data. Right now, our workaround is to clutter Actions or Notes with address update notes since these critical backend fields can not be viewed or added/edited in Unified View. Using this workaround is not a long-term solution and is subpar to the functionality that is in DBV.
This is key info for where address came from and reliability.
If address is from registrar at graduation, is likely now parents'. If address came from a dev staff it is more reliable than one from an online source. Want to know when it's from an NCOA update.
Needs this for effect use of address info.
This is big for us. It helps us in many ways, including integration with other databases/applications.
This is critical information and lets me know when to dig deeper on finding accurate contact information.
No “Info Source” on Addresses should be a critical issue and should be added. We need this information to understand how an address is entered into the system. This is standard good data management practices and essential for evaluating data quality. Thank you!!
Also, the fields populated NCOA are useful for additional research on the property itself.
We use this as one of the metrics to track engagement. If a constituent takes the initiative to provide this information, that's valuable information. Please add a place for this in the address section.
This is necessary for us. We have received returned mail before where the address is correct, but it is still retuned for some reason. Also NCOA isn't always right. A person stays on NCOA for 48 months. If they move again without alerting the post office, but we get a direct address update from the constituent, we need to know that the direct address is correct, not what NCOA is pulling.
WHY ON EARTH DOES BLACKBAUD THINK THIS FIELD IS UNIMPORTANT?
We use this field to send follow-up emails or phone calls to constituent's that we have marked with particular reasons for why we cant mail to that address anymore. For example: if the info source field says the address has received return to sender mail then we email the constituent asking for a new address, but if the info source field says the address is an old address but know we already have a new address then we don't email them. This entire process won't work if you remove this vital functionality.
I feel that privacy laws are heading in the direction that means this will be one of the valuable fields in the data we have. Please make this happen!
This is vital information. We use Address Info Source to track WHY an address is no longer valid. This matches our country's postal service reasons and includes: returned mail received, address incorrect, refused by receiver, constituent advised old/new address etc.
As we move closer to "Unified View" this does not seem to be any closer to happening as is still marked as "Reviewed: Need Further Info".
Info source is a field found on the Address tab in database view. This is an Address Field and is connected to a table under configurations (in Webview it is the 'Address Info Sources' table under the category 'Biographical').
The entries in the table are determined at the organization level as well as by the system when applications such as 'Address Finder' or 'AddressAccelerator' are utilized.
The why of having this information available in the "Unified View" is to determine the source of an address. By having the source documented in an easy to view, queryable, and exportable manner we are able to quickly see where we obtained the address from.
There are times when an address comes under scrutiny and the first question is "Where did we get the address from?"
As privacy rules get stricter, we need to have documentation of the sources for the contact information on the records in our system.
Without a place to easily track and match this information, we would have a hard time backing up the validity of our data.
By having the 'Info Source' field available to us in "Unified View" Blackbaud would be helping to do its part in making sure we, the Blackbaud clients, have a place to easily and properly document our sources.
As we move closer to "Unified View" this does not seem to be any closer to happening as is still marked as "Reviewed: Need Further Info".
Info source is a field found on the Address tab in database view. This field is connected to a table. The entries in the table are determined
Yes, this would be very useful.