<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-5512311610334754148.post2808690614772921743..comments</id><updated>2009-01-15T09:55:50.338-07:00</updated><title type='text'>Comments on The Ancestry Insider: Content is King!</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://ancestryinsider.blogspot.com/feeds/2808690614772921743/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default'/><link rel='alternate' type='text/html' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html'/><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>AncestryInsider@gmail.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>5</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-5512311610334754148.post-3457823184237661112</id><published>2009-01-15T09:55:00.000-07:00</published><updated>2009-01-15T09:55:00.000-07:00</updated><title type='text'>Dearest AI,Ol' Myrt here commends you on the faith...</title><content type='html'>Dearest AI,&lt;BR/&gt;Ol' Myrt here commends you on the faithful report of Tim Sullivan's speech at the TGN banquet on Saturday night.&lt;BR/&gt;&lt;BR/&gt;And as to the inflamatory comments from MikeF about international content, may I say that except for those with 100% Native American ancestry, current US researchers will become increasingly concerned with online availability of overseas record groups as their research progresses.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/3457823184237661112'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/3457823184237661112'/><link rel='alternate' type='text/html' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html?showComment=1232038500000#c3457823184237661112' title=''/><author><name>Myrt</name><uri>http://www.blogger.com/profile/15684472865240981715</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html' ref='tag:blogger.com,1999:blog-5512311610334754148.post-2808690614772921743' source='http://www.blogger.com/feeds/5512311610334754148/posts/default/2808690614772921743' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-5512311610334754148.post-5770206990770247315</id><published>2009-01-13T20:08:00.000-07:00</published><updated>2009-01-13T20:08:00.000-07:00</updated><title type='text'>Way to go MikeF. I really liked  your comment and ...</title><content type='html'>Way to go MikeF. I really liked  your comment and this is basically what I put in every ancestry.com survey that pops up on my computer: stick with US records; more southern USA records; More primary records and especially prior to 1850..... Great Comment.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/5770206990770247315'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/5770206990770247315'/><link rel='alternate' type='text/html' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html?showComment=1231902480000#c5770206990770247315' title=''/><author><name>GeneaDiva</name><uri>http://www.blogger.com/profile/11139846486409117017</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html' ref='tag:blogger.com,1999:blog-5512311610334754148.post-2808690614772921743' source='http://www.blogger.com/feeds/5512311610334754148/posts/default/2808690614772921743' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-5512311610334754148.post-8332369544767387878</id><published>2009-01-13T01:17:00.000-07:00</published><updated>2009-01-13T01:17:00.000-07:00</updated><title type='text'>User Pillar A: watch what they do, not what they s...</title><content type='html'>User Pillar A: watch what they do, not what they say.&lt;BR/&gt;&lt;BR/&gt;A TGN employee was on my tail about comments regarding some database deficiencies.  He claimed that Ancestry tells people when database images are missing (wrong; they are simply omitted from the index, or linked to the generic Ancestry error-processing-image page that essentially says 'go away and try again later').  He claimed that the swath of missing records from a database (2/3 of one of my roots Counties) was not so consequential because it constituted fewer than 1% of the total database.  He quit the exchange and did not reply when I pointed out that Ancestry has known about these missing records more than 2.5 years, and asked him *when* the missing images would be provided by scanning the original documents.&lt;BR/&gt;&lt;BR/&gt;Mike F.'s note re: Pillar 1.d) is quite right.  One of the noted requests from TGN during Saturday was volunteers to add 'Places', such as in a wiki-type page.  Hahahahahah heeheeheeheehee hohohohohoh.  I have put appreciable time into editing a 'Places' database on another site, and can say that Tree People generally have no inclination toward consistent place descriptions, that existing map-linking programs have more serious platform issues than simply place-names, and that it is awesomely ludicrous for Ancestry first to roll out a Tree-map linking effort and then ask for ***volunteers*** to fix the place-names issues???????  I can't think of any secular commercial enterprise that relies on *volunteers* for functions such as correcting indexes, much less having the idea that people will volunteer to fix unsuitable databases such as the linked-mapping ones (I figure a full-time team of 10 people could make good progress in 3 years).  &lt;BR/&gt;&lt;BR/&gt;Mike F.'s Pillar #4, fixing what is wrong, should be seriously undertaken by TGN.  Strange, piecemeal and inconsistent indexing of databases are part of the reason  the Search Engine so often retrieves ridiculously inapplicable results, for example.&lt;BR/&gt;&lt;BR/&gt;Weird keyword indexing is also a factor in Mike F.'s #6d.  When I tried New Fuzzy Search Interface, no matter what I did I could not get it to stop including Ohio land records, NY 19th century passenger-ship pictures, Natchez, Mississippi records, Manitoba newspapers and an odd Tennessee settlement compilation from results for a search regarding a person b. in DE in 1760, d. in WV in 1816.&lt;BR/&gt;&lt;BR/&gt;So I am watching.  If Old Search is made inaccessible and supplanted by even a slightly less loony/buggy version of New Fuzzy Search Interface, I am outtathere.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/8332369544767387878'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/8332369544767387878'/><link rel='alternate' type='text/html' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html?showComment=1231834620000#c8332369544767387878' title=''/><author><name>Geolover</name><uri>http://www.blogger.com/profile/12050268303916428230</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html' ref='tag:blogger.com,1999:blog-5512311610334754148.post-2808690614772921743' source='http://www.blogger.com/feeds/5512311610334754148/posts/default/2808690614772921743' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-5512311610334754148.post-9117606842328118510</id><published>2009-01-12T16:17:00.000-07:00</published><updated>2009-01-12T16:17:00.000-07:00</updated><title type='text'>Insider,Let's look at the 3 pillars in more detail...</title><content type='html'>Insider,&lt;BR/&gt;&lt;BR/&gt;Let&amp;#39;s look at the 3 pillars in more detail, and examine whether that covers it all or some other things are missing.&lt;BR/&gt;&lt;BR/&gt;PIllar #1: Ancestry will spend more on content than any company ever has before.  Aside from your analysis that the LDS Church spends more (and I imagine Ancestry will play semantics and distinguish between what it means by a &amp;quot;company&amp;quot; and an &amp;quot;organization&amp;quot;), some things are missing in this PR blurb about more than ever before.&lt;BR/&gt;&lt;BR/&gt;a) a comparison with last year&amp;#39;s spending on data;&lt;BR/&gt;b) a commitment to keep spending at that level or content;&lt;BR/&gt;c) most importantly, a definition of &amp;quot;content&amp;quot; - we want more original data acquisition, not more *customer provided content* like family trees, photo etc that costs something to host and could be said to be &amp;quot;content investment&amp;quot;.&lt;BR/&gt;&lt;BR/&gt;&lt;BR/&gt;Pillar #2: Technology&lt;BR/&gt;&lt;BR/&gt;a) Screw international websites.  Most of us Americans don&amp;#39;t care, and most citizens of other nations as in the UK or Germany don&amp;#39;t care about our genealogical records.    This international stuff sounds good when Ancestry goes for an IPO (if the general economic situation is ever again favorable), but does not mean squat to most users.   &lt;BR/&gt;&lt;BR/&gt;b) Follow through on statements made by Anne Mitchell in the Ancestry blog that one size does not fit all.  This means stop trying to find the perfect search algorithm to impose on all, and instead implement technology that allows *the user* to determine whether he/she gets an exact/fuzzy/ranked or whatever search.  *The user knows best* NOT Ancestry.  And part of this is leaving Old Search in place for those who prefer it and returning some intentionally gutted functionality like advanced family tree search.&lt;BR/&gt;&lt;BR/&gt;c) Pillar #3: Marketing vs. Data Acquisition Spending - You are only stating what is obviously true, and are also giving a false dichotomy in posing the situation as too much or not enough.  I doubt it is 4 to 1 on marketing vs. data acquisition spending or the firm goes under.  And you don&amp;#39;t discuss, and I believe you never have, customer turnover numbers.  Better customer service + increased commitment to data acquisition + commitment to fixing database errors and programming bugs = less turnover.  And it isn&amp;#39;t a matter of just putting a better PR face on things, but on the underlying realities.  If Ancestry did things better they wouldn&amp;#39;t turnover customers as much and wouldn&amp;#39;t need to spend as much on marketing.&lt;BR/&gt;&lt;BR/&gt;&lt;BR/&gt;Things left out (unless you were getting to them in later posts):&lt;BR/&gt;&lt;BR/&gt;SHOULD BE PILLAR #4: Commitment to better quality control and fixing previous errors.&lt;BR/&gt;&lt;BR/&gt;Mr. Sullivan and his underlings need to read a book on Kaizen.  Don&amp;#39;t make the errors and you won&amp;#39;t have to fix the errors.  And if you have made some, *then fix them now or by a date certain*.&lt;BR/&gt;&lt;BR/&gt;&lt;BR/&gt;SHOULD BE PILLAR #5: Have a *public* strategy for data (original or printed record and not user provided content) acquisition that follows a reasonable plan and won&amp;#39;t take 50 years.&lt;BR/&gt;&lt;BR/&gt;a) An emphasis on the original 13 colonies plus gateway/migration states like Tennessee and Kentucky, Missouri, etc. + California and Texas.&lt;BR/&gt;b) Equal emphasis on pre-Civil War records as post-Civil War because even if a majority of customers say now they they prefer late 1800s and 1900s records (when genealogy is easier), they will eventually run into many brick walls in the predictable time period of the Revolution to 1840.&lt;BR/&gt;c) Give the original records *as they come on the microfilm*, instead of trying to group them and messing up the grouping as Ancestry has done in so many census enumerations.&lt;BR/&gt;d) *IMPORTANT*: Better explain the &amp;quot;about this database&amp;quot; explanations, including all missing subsets and why and *when they will be added*.&lt;BR/&gt;e) Update yearly/bi-yearly databases such as vital records indexes and image collections - these should be evergreen databases.&lt;BR/&gt;f) Serve up *unindexed* county records - better to have access now by reading page by page than no access for years/decades until they are indexed (by FS).  Note too that many county level records like deeds actually are already indexed which indexes could be transcribed as is to start.  People simply cannot break through many/most brick walls without county level land and court records.&lt;BR/&gt;&lt;BR/&gt;&lt;BR/&gt;SHOULD BE PILLAR #6: Excellence in Customer Service&lt;BR/&gt;&lt;BR/&gt;a) Responding *fast and publicly* to concerns expressed in the message boards if that is the customer&amp;#39;s preferred method of communication instead of phones calls and knowledge bases.  And implement multiple blogs for different sections of Ancestry.  It is hard to keep conversations on the search going when other employees dump blog posts about publishing and trees and other stuff.  Those functionalities should have their own blogs, or *better yet* dedicated message boards where customers can initiate topics of conversation (instead of the general &amp;quot;comments&amp;quot; and &amp;quot;improvements&amp;quot; boards now).&lt;BR/&gt;&lt;BR/&gt;b) Involve customers in the concept phase of development and not just in tweaking the interfaces once it is a done deal (and possibly flawed in principle).&lt;BR/&gt;&lt;BR/&gt;c) Stop predatory subscription practices like auto renewals if the customer does not set such a preference, and the same for trial subscriptions.&lt;BR/&gt;&lt;BR/&gt;d) Fix immediately all misrepresentations in holdings.  This means click on a state&amp;#39;s data like for Wyoming, and *get rid of* stuff like American Wills Proved in London, Virginia Estates or whatever.  While this might have been auto-generated at some point or something, it only serves now to falsely bloat the supposed data available for many states that have little true coverage.  This is a matter of INTEGRITY.&lt;BR/&gt;&lt;BR/&gt;&lt;BR/&gt;SHOULD BE PILLAR #7: Easier navigation of the website&amp;#39;s holdings than the card catalog.  &lt;BR/&gt;&lt;BR/&gt;&amp;quot;Stories, Memories &amp;amp; Histories&amp;quot; in particular is a total mess.   It is a giant haystack and it is hard to find needles in the glut of surname works.  State and county histories and data extracts should be separate, and in fact under each state should be a collapsible list of counties so one can find databases and books by county.&lt;BR/&gt;&lt;BR/&gt;&lt;BR/&gt;&lt;BR/&gt;Mike</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/9117606842328118510'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/9117606842328118510'/><link rel='alternate' type='text/html' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html?showComment=1231802220000#c9117606842328118510' title=''/><author><name>MikeF</name><uri>http://www.blogger.com/profile/16587230319820652536</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html' ref='tag:blogger.com,1999:blog-5512311610334754148.post-2808690614772921743' source='http://www.blogger.com/feeds/5512311610334754148/posts/default/2808690614772921743' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-5512311610334754148.post-7991268054642074224</id><published>2009-01-12T10:31:00.000-07:00</published><updated>2009-01-12T10:31:00.000-07:00</updated><title type='text'>Thanks for the informative update! It is nice to k...</title><content type='html'>Thanks for the informative update! It is nice to know what is coming down the pike and what the rationale is for each of these companys.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/7991268054642074224'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5512311610334754148/2808690614772921743/comments/default/7991268054642074224'/><link rel='alternate' type='text/html' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html?showComment=1231781460000#c7991268054642074224' title=''/><author><name>Andrea Christman</name><uri>http://www.blogger.com/profile/04708535087949160210</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='14507629334938380818'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://ancestryinsider.blogspot.com/2009/01/content-is-king.html' ref='tag:blogger.com,1999:blog-5512311610334754148.post-2808690614772921743' source='http://www.blogger.com/feeds/5512311610334754148/posts/default/2808690614772921743' type='text/html'/></entry></feed>