I don’t doubt that this has been discussed before but I can’t seem to find anything on the subject. I was talking to a librarian friend today and he asked me how I planned to make sure that my files will be available after I’ve passed. I told him I had no idea. Are the *.dtBase2 files an industry standard so that they can be read by a program other than DT? How do I ensure that an archive will be able to make my work accessible in the year 2050?
2 Likes
Look here…
1 Like
uimike:
I’m not so concerned about DT “going away” as I am about doing the best I know how to make my files available to future researchers. All archives and librarians, from the National Archive down, are doing their best to address this issue. I’m not about to export all of my files and print them on paper. I do appreciate your contribution to the discussion, though. Thank you.
I should have been more explicit. Read through the thread, you’ll find out your questions addressed.
The short answer is that your files are stored in whatever their original format was, and can be extracted from the database “package” without using DT.
The thread @uimike linked has a more detailed discussion.
2 Likes
Our files are stored in original format, in a folder buried within the .dtBase2 package
As part of my backups, I maintain an external export of my files
It includes my files, the group/folder structure, and file tags
3 Likes
umike:
I did read the entire thread and my question about whether the *.dtBase2 files is an industry standard was not answered. However, I see that several others have joined the discussion so perhaps I will find the answer I’m looking for. Thanks!
Since that is your question I’ll answer specifically. AFAIK, .dtBase2 is not an industry standard. Maybe someday ANSI or someone will adopt it, but I seriously doubt it.
These are macOS “packages” holding your files in their native format (PDF, DOCX, MD, …) along with DEVONthink’s “metadata” (information about* those files).
The risk of you losing your files in 20 years depends more on computers still existing than an industry standard.
1 Like
It makes no sense. dtBase2 is a folder like any other folder with a special attribute that makes it look like a package.
This folder contains another folder noindex which is the parent of all your documents.
I’d worry more about a reliable backup strategy than about getting files out of DT.
6 Likes
DTLow:
Would you kindly provide more detail? I am aware that files and folders can be exported from DT in their native format but that requires using DT. The future scenario I am trying to avoid is one in which the *.dtBase2 files cannot be read by any program 30 to 40 years from now. DT is a superb program and I certainly don’t expect the files to be in a condition that can be used as DT does such a wonderful job of doing. An analogy which might be helpful, if you are familiar with geneaolgical research: there is a “standard,” of a sort (which is really not so great) called GEDCOM, which can be read by most genealogical programs. The “standard” is not perfect because the parameters are not followed by all software developers but it does exist and it does go a long way towards preserving data. I just can’t grasp the idea that thousands of people worldwide (DT’s customer base) haven’t come up with a method to ensure their work remains available for future researchers. Backups are esssential but if the data can’t be “seen” by other programs, what good is it?
rmschne:
Thank you!!
chrillek:
I have what I consider a reliable backup strategy: a cloud backup plus 3 rotating external hard drives. The only missing piece is that the external hard drives are all in one place but the cloud backup helps with that issue. The issue isn’t about “getting files out of DT,” it’s about others being able to access the many thousands of hours I’ve spent in accumulating the data if they don’t have DT. DT is a superb program and I wish I had known about it years ago. I have no complaints about DT or any idea of leaving. This is about future-proofing, as best as I can.
All files will be forever available, as other have been explaining, the database is just a type of Mac folder, can be opened (if needed, one day, years from now) with a right click to “show package contents” - and everything is there, individually accessible, with their file names. DT is brilliant, many other solutions used boxes, where you needed the app to recover a file. The dt2 thing is immaterial to you. And you can even export the entire folder structure as Mac finder folders from time to time and store it locally or in the cloud if you wish so.
3 Likes
Not how it works. Files are not exported “from” DEVONthink. They exist in DEVONthink in their native format (PDF, DOCX, MD, …). Re-read the material we gave you. Yes, the term “export” is used, but it’s really more like a “copy”.
Without making changes, inspect for yourself the DEVONthink database packages using the tools available in Finder.
Your biggest risk in losing access to your files is that there are no computers anymore that can handle PDF’s, DOCX’s, MD’s, …. The US Library of Congress has thought long and hard about that and has published their thoughts on what they are doing to retain information for the ages. Check their web site.
1 Like
Accumulating the data is a pretty vague description. If you are doing lots of smart rules, custom metadata, etc., etc., then yes, you will not have that without the app.
But if it’s really about the files, including notes that are, whatever, text, rtf, md, then all will be there. Now links between any items, that’s another conversation.
2 Likes
Aside from the excellent answers you have gotten from others - you will surely be able to buy a working used Mac 40 years from now, just as today you can easily go to Ebay and buy a TRS–80 or Apple 2 from the early 1980s.
Devonthink will still work 40 years from now on a 2025-vintage computer.
4 Likes
More detail on what?
As I said, my backups include my files stored externally to the .dtbase2 package
btw I have .gedcom files stored in my DT data
1 Like
I want to +1 Show Package Contents. It’s a first-class Finder feature. It’s an archive/package which is a macOS standard feature, even if the organization inside is specific to DEVONthink. Because it’s a macOS standard feature I think you could consider it an industry-wide standard.
macOS actually considers them to be folders. The reason they don’t open as folders in Finder so so the application will open them instead. Show Package Contents is how macOS lets you open them as folders while still letting double-click open them in the right application.
Hopefully this provides some assurance. It’s a reasonable question.
3 Likes
Excellent point.
1 Like
However, we do caution people they shouldn’t mess about in the internals of a database except in emergency situations and ideally after talking to us first 
1 Like