<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: New military records on the way: WO96 &#038; 97</title>
	<atom:link href="http://blog.findmypast.co.uk/2009/02/new-military-records-on-the-way-wo96-97/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.findmypast.co.uk/2009/02/new-military-records-on-the-way-wo96-97/</link>
	<description>official blog for findmypast.co.uk</description>
	<pubDate>Thu, 29 Jul 2010 13:44:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: iantester</title>
		<link>http://blog.findmypast.co.uk/2009/02/new-military-records-on-the-way-wo96-97/comment-page-1/#comment-32</link>
		<dc:creator>iantester</dc:creator>
		<pubDate>Wed, 25 Feb 2009 10:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.findmypast.com/?p=64#comment-32</guid>
		<description>Hello Matthew: yes, these datasets were a little odd in that we didn't digitise them from fresh but rather acquired them through a licencing deal with a partner in the format they're currently  in which didn't allow for backwards engineering to make them more searchable. Where we do fresh digitisations, we have complete control over the imaging and transcriptions and therefore the search fields.</description>
		<content:encoded><![CDATA[<p>Hello Matthew: yes, these datasets were a little odd in that we didn&#8217;t digitise them from fresh but rather acquired them through a licencing deal with a partner in the format they&#8217;re currently  in which didn&#8217;t allow for backwards engineering to make them more searchable. Where we do fresh digitisations, we have complete control over the imaging and transcriptions and therefore the search fields.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Camp</title>
		<link>http://blog.findmypast.co.uk/2009/02/new-military-records-on-the-way-wo96-97/comment-page-1/#comment-30</link>
		<dc:creator>Matthew Camp</dc:creator>
		<pubDate>Thu, 19 Feb 2009 19:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.findmypast.com/?p=64#comment-30</guid>
		<description>Ian,

Thank for responding.
Hopefully you can emulate your performance on the Census with these new products then.

I'm just concerned this may be overlooked because you haven't been able to implement 'regimental' searching yet for De Ruvigny, Soldiers Died or National Roll- all datasets that really should be searchable by regiment given the information contained in them and the relative ease of transcribing printed text. 

Perhaps there was a licencing issue with these products preventing you from doing more than the minimum you have provided to date, but hopefully you won't have such an issue with WO96/97.

I look forward to seeing the end results in 2011.</description>
		<content:encoded><![CDATA[<p>Ian,</p>
<p>Thank for responding.<br />
Hopefully you can emulate your performance on the Census with these new products then.</p>
<p>I&#8217;m just concerned this may be overlooked because you haven&#8217;t been able to implement &#8216;regimental&#8217; searching yet for De Ruvigny, Soldiers Died or National Roll- all datasets that really should be searchable by regiment given the information contained in them and the relative ease of transcribing printed text. </p>
<p>Perhaps there was a licencing issue with these products preventing you from doing more than the minimum you have provided to date, but hopefully you won&#8217;t have such an issue with WO96/97.</p>
<p>I look forward to seeing the end results in 2011.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iantester</title>
		<link>http://blog.findmypast.co.uk/2009/02/new-military-records-on-the-way-wo96-97/comment-page-1/#comment-28</link>
		<dc:creator>iantester</dc:creator>
		<pubDate>Wed, 18 Feb 2009 09:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.findmypast.com/?p=64#comment-28</guid>
		<description>@Matthew: exact details of the search and indexing are still being determined but rest assured that we always transcribe fully and aim to make as many fields searchable as possible - indeed we lead the market on this on our census collection. 

Our minimum aim is to improve upon the searchability, accuracy and indexing of WO363/4.</description>
		<content:encoded><![CDATA[<p>@Matthew: exact details of the search and indexing are still being determined but rest assured that we always transcribe fully and aim to make as many fields searchable as possible - indeed we lead the market on this on our census collection. </p>
<p>Our minimum aim is to improve upon the searchability, accuracy and indexing of WO363/4.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Camp</title>
		<link>http://blog.findmypast.co.uk/2009/02/new-military-records-on-the-way-wo96-97/comment-page-1/#comment-26</link>
		<dc:creator>Matthew Camp</dc:creator>
		<pubDate>Tue, 17 Feb 2009 17:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.findmypast.com/?p=64#comment-26</guid>
		<description>I hope you'll be making these searchable by regiment and regimental number too, and not just by name. Much of the utility of these records will be lost if you don't include these key fields. 

The prime users of these records at the National Archives are medal collectors, military researchers and regimental historians rather than people searching for their ancestors (although there is obviously significant interest from that area as well). As such, it would be most useful if they were indexed properly.

As was mentioned when these series were put out to bid the "Friends of the National Archives" have been transcribing such files using Soldier's Name, Place of Birth, Regiment(s), Year of discharge, covered dates of service. 

Personally, I would think this should be a minimum requirement, and something like Ancestry's indexing of the WO363 and WO364 files should be emulated. There they include name, age, birth year, residence location, birth county, regiment, number.

Providing a search based solely on a name just won't provide much utility for many existing and potential subscribers. I pity the poor researchers who are going to have to look for "John Smith" if all they'll have is a surname search to wade through.</description>
		<content:encoded><![CDATA[<p>I hope you&#8217;ll be making these searchable by regiment and regimental number too, and not just by name. Much of the utility of these records will be lost if you don&#8217;t include these key fields. </p>
<p>The prime users of these records at the National Archives are medal collectors, military researchers and regimental historians rather than people searching for their ancestors (although there is obviously significant interest from that area as well). As such, it would be most useful if they were indexed properly.</p>
<p>As was mentioned when these series were put out to bid the &#8220;Friends of the National Archives&#8221; have been transcribing such files using Soldier&#8217;s Name, Place of Birth, Regiment(s), Year of discharge, covered dates of service. </p>
<p>Personally, I would think this should be a minimum requirement, and something like Ancestry&#8217;s indexing of the WO363 and WO364 files should be emulated. There they include name, age, birth year, residence location, birth county, regiment, number.</p>
<p>Providing a search based solely on a name just won&#8217;t provide much utility for many existing and potential subscribers. I pity the poor researchers who are going to have to look for &#8220;John Smith&#8221; if all they&#8217;ll have is a surname search to wade through.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
