This must be covered somewhere but I can’t readily put my finger on it. I’m keen to move to DT3 for lots of reasons – it looks just amazing – but I am wary to trust my entire research library to it while the app is still in beta. (Are people experiencing stability issues? Database corruption problems? (I’m following Bluefrog’s advice not to trust ‘mission critical’ material to a beta).
So I wonder, is there an ETA for the beta to end, moving to DT3 v. 1? I recall seeing ‘summer 2019’ somewhere, but depending on your location that’s rather flexible…
Are people experiencing stability issues? Database corruption problems?
I agree completely that it is very foolish to place thousands of PDFs etc., built up slowly into a series of DBs that enables its user to find everything needed in their research, within mere seconds, into a Beta-version information manager.
Especially if one were to think of all the hundreds of hours spent tinkering to get those DBs to work & function exactly as needed.
Not to mention the hundreds and hundreds of hours spent annotating those PDFs, and building links between them etc. etc.
And yet, despite that agreement, and the absolute knowledge of the horror that would ensue were things to go, well, horribly wrong with that Beta-version information manager, here I sit, with all of my DBs, and thousands of PDFs, and their annotations, inside that very same Beta-version information manager…
And so far, so good. For several months already.
I actually felt uncomfortable typing that.
I also realise that I am clearly too impatient
But, well, yes. No stability issues or corruption or the like this side. But, as always, YMMV! So think long and hard of the costs of something going wrong!
But, as always, YMMV! So think long and hard of the costs of something going wrong!
I absolutely agree with this.
Yeah, I’m the broken record around here, but…
After almost 20 years of beta-testing and having lost data, etc. due to unruly apps, it’s just the wise course of action. Real beta testing is fun, but also can be dangerous and it’s often inconvenient.
It’s my job to safeguard people’s databases, so I am always going to suggest the conservative approach with their data.
But at the end of the day, it’s your data, your choice - but I always err on the side of caution for you all.