Change is in the air


Over the past few months we have been hard at work on updating the keying tool.  The keying tool 2.0 will be available in the coming weeks – likely end of October.

Due to backend changes occurring at Ancestry the keying tool will be down starting the 30th until the new tool is ready.  Unfortunately, this means a forced vacation from indexing.  We will be blogging throughout the time we are down to keep you up to date on progress.

It has been ten years since we went into open beta on the first version of the keying tool.  We have seen quite a few changes since that first version and we have accomplished a lot…50,000+ contributors have indexed millions and millions of records from 16,253,102 images and as a result there are currently 340 live databases on Ancestry.  Amazing!!

Whether you have just started indexing or have been with us for the last 10 years we appreciate your contributions!

Information and Links

Join the fray by commenting, tracking what others have to say, or linking to it from your blog.


Other Posts

Write a Comment

Take a moment to comment and tell us what you think. Some basic HTML is allowed for formatting.

Reader Comments

What will happen to the files we are currently working on? Will we be able to continue with them once the keying tool is back up and running?

We have about 4 hours to submit image sets. After this time image sets will not submit properly. When the keying tool is back up we will be indexing the same projects.

I am happy that updates will be coming to WAP, but also saddened, as I am obsessed with arbitrating and I loved keying the GAR and Delaware Land Records. I live in New Bern NC, where Hurricane Florence has certainly left her mark; so I am selfishly happy WAP will be on “recess” for a few weeks! Can’t wait for the updates!!

Sad to take a vacation–keying is my vacation!–but good to know about updates. Fingers crossed they work on Macs.

I was just able to “review and submit” Alabama Surname Files without any problem. Also downloaded a new batch of files for review. Can I assume that the “review” process is still active and only the “keying of new files” is down?

Connie, and all,
I also have been testing – apparently not all of the backend changes have been made. We will not be able to index beyond the 30th.

If you need Beta testers, I would love to be included. Working on these records is my activity to winddown. Will miss it.

Thank you all for offers of testing.

As of today we are still able to download and submit but I am told that soon we will not be able to – no specific date yet.

We appreciate your contributions and patience.

Still able to submit and download sets 🙂

I’m happy to help with testing the new keying tool if needed.

Also happy to help testing if that’s useful.

Will we all be notified when the new keying tool is up and running?

If so, how?

Well I didn’t know this was happening. Maybe you folks should put a message inside the tool saying as such. Spent 40 minutes trying to get the keying tool to work to find out it was on your folks end after finding this post.

Thomas

Thomas, The blog posts should appear on the keying tool when you log in, it is also worth keeping an eye on the World Archive Project message board as announcements are copied there

Sandrra, maybe when the tool was active but not now since one cannot get into it since the login feature has been disabled (trust me I know!) And thus if you didn’t login between Sept 26 and 30th, you wouldn’t have known. Thus perhaps in the future to have more lead time should another shutdown happen. And of course some people sadly have to do other things non-genealogy (yeah, sadly!) before doing genealogy work too. Just some thoughts.

I wish you had told me about this being updated and going offline when I told you I was unable to get in to do some keying on 11 October. All the program told me was that my password was not recognised and to get a new one,and gave me a long, unintelligible error message. I was able to get into Ancestry.com for lookups, so it obviously was not a wrong password. I have been trying to get in to do some keying most nights since then to no avail. The programe was soooo slow to open (which I told you in my email) and tonight I finally gave up and deleted it from my computer. I will download it again when you email us to let us know you are back online again. Pity your reply email was not an answer to m y query, but only told me to change my password. See my email to you below 2018-10-11 I have been transcribing for the World Archiv es project for at least 2 years or more. Never had this problem before. The program takes 50 seconds to load and 45 seconds for my username & password to try to log in . Then my password is not accepted. II get an error message “System.Web.Services.Protocols.SoapException. Server was unable to process request. A network related or instance-specific error occurred whilst establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correctand that the SQL Server is configured to allow remote connections. (provider. TCP Provider. error. 0 – A connection attempt failed because the connected party did not properly respond after a period of time, or established co0nnection failed because connected host has failed to respond.) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at System.Web.Services.Protocols.SoapHttpClientProtocol.
There is a lot more to this error message.

Please keep us, your loyal contributors, informed as you are improving the keying tools. We are all anxious to return to our keying of image sets. Thank you for your time and consideration.

I was unaware of the updates and called Ancestry. They do not know this either. I usually do this while I am on vacation and was saddened that I couldn’t, but understand changes have to be made. I did keying the week before and did not see the message, my bad. I’m glad I finally found this.