« SLA Conference: Copyright Roundtable | Main | SLA Notes: Monday's General Session »
June 12, 2005
SLA Notes: News Division Vendors' Roundtable
News Division Vendor's Roundtable
Monday -- June 6, 2005
7:30 a.m. - 9:00 a.m.
Convention Centre 104-C
Moderated by Leigh Poitinger
Panelists:
Bill Bear, Director of Marketing for ChoicePoint PRG [CP]
Chuck Backus, VP of Product Management for LexisNexis [LN/A]
Doug Roesemann, President of the ReferenceUSA Division of InfoUSA [LN/R]
Q&A: Items in italics are comments and questions from the audience and moderator
What kinds of sources are used for data and how is it verified/be corrected?
LN/R: Started with white pages in the 1970s, now includes credit records, voter reg, student lists, active bank cards, mail order buyers, redeemers of warranty cards, magazine subscribers, and in-house business surveys; news libraries can
CP: There can be issues with the frequency of updates of government-derived information; errors can be reported to the company
LN/A: You can report errors to the company AND it will try to find out the source of the error to correct upstream
LN/R: There has been issues of being able to keep up with cell phone #s
I've heard that public records won't be updated on Nexis.com and updates are only available on Accurint.
LN/A - No ... there will be an integration of public records between the Nexis and Accurint platforms, so the most current records will be available in both sets of products, but the updating will take place within Accurint modules.
Is journalistic use of public record products in danger of evaporating due to changing definitions of appropriate use?
CP: There will continue to be public records products for journalists to use
LN/A: However, there might be less data available if the customer doesn't fit the "permissible use" definition (law enforcement, credit verification)
We don't use SSNs/DLs, but we really need the SSNs/DLs to use as unique identifiers.
LN/R: We're also starting to provide cell phone #s to our "Fine" module for RefUSA
We have been burned by rapidly changing rate structure and vanishing product functionality/features; also, there's has been uneven support and there has been a lack of risk assessment in some instances of sales reps assisting customers in the area of permissible use.
LN/A: We realize that the law is locking down the definitions of acceptable use, and we're trying to work with our
Is there any hope of getting a specific "journalistic use" category?/
LN/A: It would take lobbying on Capitol Hill to add to federal legislation
Can you help us keep track of federal and state legislation in this area, perhaps with a newsletter?
CP: We'll look into it
We've lost some economical features, which has resulted in a price increase for our usage.
LN/A: The restrictions are likely to get tighter
LN/R: What features would you like to see?
Vendors have been very tight-lipped about their products; also, what kind of tweakings may be done behind the scenes that can affect what information is available, because we're seeing there's less harder-to-find info (like cell phone #) and we're not sure why ...
CP: We're working on providing more information
LN/R: As people are using less landlines, telephone numbers are getting lost, but the Fine module of RefUSA
LN/A: The phone number issue will get harder, not only because of the landline/cell transition, but also because people are now able to port their numbers to new providers, new locations, etc.
Why are there missing or wrong area codes?
CP: Wholesale changes/redistribution of area codes, lack of updating by the source agencies.
The currency of information is very unreliable; why can't you add a 'last-updated' tag to all modules/products?
CP: We're working on it
LN/R: We're NOT going to be updating our products with such a tag
We had to re-credential and provide bank account info on the application, which doesn't fly for some orgs; also, media was missing as an acceptable use.
CP: There should be an updated application available.
What other changes should we anticipate regarding public-records legislation?
CP: We're keeping on top of that and we don't expect anything immediately to come to the fore.
In California, there's spotty court coverage; plus, courts are starting to put up their own gateways for online court info -- how does that effect public records gathering?
CP: It's very tough to get info, especially at the sub-state (county, municipal court) level; currency/updating is a big issue
LN/A: Similarly, it's difficult to provide "last updated" metadata for composite products; at the individual file level, it's easier; but for irregular sources or "dirty" data, it'll take a while to clean it up for use/access within the products
You're fairly upfront about mistakes in the database; however, we're being pushed onto web interfaces or new product interfaces that are "less" than what we're already using and are proficient with.
How often do you do audits? Do you see a time when customers will have been be licensed/vetted to get access to the products?
CP: We do random and periodic audits; the security of passwords and IDs are likely to get tighter
LN/A: We're doing more audits than we used to, which is actually problematic -- some customers don't want to tell us what they're doing; also, the refreshing of IDs and passwords are going to get tougher.
Posted by misseli at June 12, 2005 02:43 PM