Showing posts with label Dropbox. Show all posts
Showing posts with label Dropbox. Show all posts

Friday, February 27, 2026

A Tech Lesson Learned The Hard Way

 

AI Image

Oh, technology. You love it when it works and you despise it when it fails.

I recently had a failure that stopped me cold, even though I was absolutely certain I had done everything right. I’m sharing what happened so you can avoid making the same mistake.

My number one rule has always been to back up. And I do. Religiously. But sometimes, even that isn’t enough.

I was working on Volume 5 of Echoes of Britannia when I realized it had grown too large and really needed to be split. I saved Volume 5, made a copy on my desktop, and renamed that copy Volume 6. Then I opened Volume 5, deleted the material that would live in Volume 6, saved, and closed it. Next, I opened Volume 6, deleted the material that belonged in Volume 5, saved, and closed that file as well.

That evening, I saved both files to Dropbox and to a standalone external hard drive.

All seemed right with the world. Sure.

Three weeks later, while working on Volume 8, I became confused about a pedigree and reopened Volume 6 to double-check a spouse. That’s when I noticed something was wrong. The footnote I was looking for was gone. In fact, nearly three-quarters of the footnotes in Volume 6 were missing.

I refused to panic. Surely it was just the way Word had loaded the document. I closed it without saving and reopened it.

Nope. Still gone.

No worries, I told myself. I’ll just open the Dropbox version.

The footnotes were gone there, too.

That actually made sense, every night I saved over the same files. But Dropbox keeps deleted versions for thirty days, right? Except…there was nothing to restore. Why? Because I hadn’t deleted the file. I had saved over it using the same filename. The old version was overwritten, not archived.

At this point, panic started to creep in but I reminded myself I also saved everything to a standalone hard drive. Surely that would save me.

It didn’t.

About a week and a half earlier, I had uploaded the entire folder to the drive, overwriting those files as well.

Now I was panicking and I knew I wasn’t thinking clearly. So I did the sensible thing: I turned to Geni, my trusty ChatGPT research assistant.

After I explained the situation, he calmly told me the truth: there was no way to recover what was lost.

Then, cheerfully, he added that it wasn’t so bad. I’d written it once, so I could write it again.

OMG. No. That was the last thing I wanted to hear.

Let’s just say you were lucky you weren’t at my house at that moment. I railed against the universe. How dare this happen when I had been so careful, so diligent, so responsible?

And then, right in the middle of that fury, it hit me.

Geni might have the footnotes.

Here’s something I didn’t fully appreciate until that moment: he did. Almost all of them.

As I wrote these volumes, I frequently turned to Geni with a skeleton narrative and uploaded my research finds. My prompt was always the same: “Write a short, tight, engaging narrative with Chicago-style footnotes from the information I provide, with no subheadings or conclusions.”

Using the chat search feature, I was able to locate most of those narratives. Rebuilding the footnotes wasn’t instant but it was possible. It took three full days to reattach everything, but that was infinitely better than starting from scratch.

Eight narratives were missing footnotes. Geni explained that saved chats can sometimes be lost during system upgrades, which may account for those gaps. He also gently pointed out something else I shouldn’t be doing: I tend to write very long chats. The longer the chat, the more likely parts of it may become difficult to retrieve later.

Lesson learned.

I now know that when I save files to Dropbox or to an external drive, I must rename them every time so they don’t overwrite earlier versions. Backups only work if the history survives.

AI has been a wonderful partner in my genealogy work over the past two years, but it never occurred to me that it might become the one place where my work still existed when everything else failed.

Add this to the list of reasons why I love AI.

Friday, October 3, 2025

Fall Genealogy Tasks

 


AI Graphic

The weather hasn't yet cooled and I'm not complaining but it is officially fall.

Before I get back to writing my next and final (hooray!) family genealogy book on our Great British lines I decided I had to practice what I preach and take care of some pressing tech tasks that I have put off for way too long. The first was really bothering me as it was boring and there are so many more interesting things to do in genealogy then preserve photos.

Long ago, in 2002, a world that was radically different then today, my cell phone saved all of my photos to a desktop program called Picassa that Google later purchased. I used that product until 2018 when Google rolled it into Google Photos. That's when my problems began.

When Picassa ceased to exist it lost some of my photos, years 2002, 2007, 2010, and 2019. I wasn't worried about 2002 & 2007 as my kids were still in school and I was still scrapbooking so I have those photos. I digitized the scrapbooks so we were good. 2010 & 2019, not so much. Sure, other family members probably have some of the photos but I always was the main photographer so much of that is lost. I know, it could be a lot worse but still, not happy about it.

The next issue was with the rollover, some of my photos were doubled and even tripled. New photos were created from group shots - just the heads of whatever the tech decided to select. Then it began creating memory albums. Now that doesn't sound bad but it became a problem because it used up space and Google, tying all their products together, kept reminding me I needed to purchase additional space from them or I could no longer have a functioning email.

Occassionally, I'd go into photos and delete some of the duplicates and albums but they just would pop back up. On my to-do list was to remove ALL of my Google photos, store them in Dropbox, and back them up to a standalone hard drive. BORING. but. necessary.

For Valentine's Day, one of my kids gave me a picture frame where you can store and see changing photos. This gave me the impetus to get the photos out of Google. Next week I'll print the detailed directions on how you can do that fairly quickly and easily, meaning not saving one photo at a time which I initially was doing.

I also realized that I needed to synch my Ancestry.com tree as it's been awhile since I did that. I no longer use RootsMagic and since I last synched, I got a new desktop so I didn't have Family Tree Maker downloaded to it. Now FTM has come out with their update (in May 2025 but it's called 2024, go figure). I somehow missed the promotions but they have one remaining, half price for current license members so I took advantage of it ($40 instead of $80). I decided if I was going to save Dropbox to the stand alone drive I might was well include my Ancestry tree since I've just blogged about how I was working at updating it. Yes, it's still a work in progress but I'd rather save what I have as I'll never be done with it.

Next up was to delete everything on my stand alone drive as it was all old and not relevant so I turned it back to factory settings. Took hours!

Meanwhile, one of our adult kids had their credit card stolen and the thieves, being really stupid - (Jose Lopez - I am calling you stupid!) bought items in their own name and then had it sent to our kids' address. (Now you see why I am calling Jose stupid - really, does he want to get caught? Don't even need a forensic genealogist for that one.)

Jose or whoever was the original thief, was fairly smart at the beginning. Only purchased from stores the kid always uses so for the first two weeks the scam wasn't noticed. Then, boldness hit and the thief began using it for large sums at stores never used by the kid. By the time it was noticed thousands of dollars of items had been purchased but thankfully, some get to be returned to the companies since they arrived at the kid's house. (Jose, did you think you were then going to be a porch pirate, too?) Kid called the credit card company for a dispute and the police to file a report in case Jose was local and was going to be paying a home visit. Cop informed us that a local woman got taken for $499,000 the previous week because they also stole her social security number and took out loans. What a nightmare!

That made me realize it was time for me to update some of my own financial practices.

  1. You may have some items on recurring charges. We've decided to use a separate card for those because it's a major pain to have to contact those vendors to change an account if your card is shut down.
  2. Since the card was stolen locally (we know this for reasons I'm not disclosing so the guilty can get their due, too bad, Jose, that bed you bought won't get you a good night's sleep in jail because it's already been returned) we decided to use one card just for local purchases. It's a card with a good reputation to notice fraud quickly so we won't have to dispute lots of charges when (not if) it get's compromised.
  3. We'll use another reputable card for online only purchases.

If you're thinking, that's a back up for a back up and yes it is, just like we do to save our genealogy data. This led me to realize it's been awhile since I updated my passwords so I spent time doing that as well.

Last task I haven't completed but is equally important, albeit BORING, is saving many of my emails. Lots of them contain genealogical info and I want to make sure the info is saved to the correct ancestor's file in Dropbox. That's my next project and by then, well, it'll probably be time to redo the cycle.

With the colder weather u perhaps coming next week this is a gentle reminder, dear reader, to take a look at your items to do and start plugging away at them.

3. Building Your Genealogy AI Assistant

  For the past two weeks I’ve been blogging about the importance of personalizing your AI. Last week I wrote how to accomplish that wit...