I’ve found two apps that tag items which use openMeta. However, Tags and Tagit only add actual tags and nothing else. However, I know that DT is adding the URL to the file, as I can import it to another database and it brings the tags and the URL and comments, etc.
All that to say— is DT using openMeta to store the URL, or is it something else?
Ultimately the reason I want to know is I want to know how to assign a URL to a PDF that will be brought in to DT.
Well they are exported, that’s why I’m trying to figure this all out. If you put a url on a pdf in your database then export it using file>export, then import it into a different database, the URL has come along for the ride, along with any tags and comments.
Ultimately I really want to know this because this could be another level of integration with DT and bibliographic managers. If a program like sente could tag their attached pdf’s with the local Sente URL, it would bring a tight level of integration between the two programs (by being able to jump from DT right to the Sente entry).
Ah, that’s a horse of another color, not OpenMeta. Item Links as well as file URLs show promise.
Over the past two or three months there have been several threads about ways to get cooperation between citation managers and DEVONthink. My impression is that Sente is looking at modes of working with DEVONthink databases, and Eric has provided a smart template for BookEnds.
Eric’s template obviously adds to the interoperability of DEVONthink and BookEnds.
I don’t have anything special to say about URLs. URLs (like Paths and Item Links) are one of several means to pass information between applications about the location of files. That’s important in setting up interoperability between applications.
As DEVONthink stores files in the Finder inside the database package, every file has a URL describing its location on the hard drive. But that’s probably not the best location descriptor to use, as Christian has noted that the URL of a file might change in the dynamic database structure. And of course as one might move files around among to different databases, the URL would change although the file itself and some others of its properties remain constant.
A better location descriptor — at least for exchanging file information among Cocoa applications — would seem to be the Item Link.
When DEVONthink exports a file it doesn’t automatically include information such as the file’s URL in the database file storage or the Item Link. I suppose one could devise a script to add desired information to the Comment field, so as to tie that to the exported file.
I can always use kludges based on file names or selected content, of course. If from any other application I might want to check to see if the same or a closely related file is in one of my DEVONthink databases, I can do a Lookup search. Crude, simpleminded, but often useful.
Sorry, I was being obtuse, because obviously DEVONthink doesn’t ‘attach’ a URL or other metadata to the PDF itself in a way that’s understandable by other applications — unless it is placed in the Comment field for transfer to Spotlight Comments in the exported PDF.
The DEVONtech_storage file is intended for use by DEVONthink if exported material is imported back into a DEVONthink database, and is the vessel used to hold metadata about the exported file(s). Export a PDF that has URL information in the URL field of the Info panel and that information will be held in the DEVONtech_storage file. What about a PDF that has been assigned a red label? That information, too, will be in the DEVONtech_storage file, and if that PDF is imported to a different DT database it will have a red label.
I suppose that would have potentials for conveying information among applications, if they used a common standard for writing and reading such information. But developing standards and getting them accepted in general use is the hard part.
I’ll admit that there were times when I had blank stares from my grad students.
Ahh, okay. So importing the PDF must cause DT to look for the storage file in the same directory. The riddle is solved.
It’s too bad there wasn’t something more robust than openMeta, which is only for tags.
I also wonder— would DT be able to parse tags? Like what if a tag like “URL:www.devon-technologies.com” could be recognized and parsed so that the tag actually ends up in the DT URL field? Perhaps there could be a parsable “ALIAS:” tag, etc?
I’d say that’s called Applescript. If you weren’t using (buggy) Sente, or (well-done, but doesn’t talk to the world) Bookends, you’d be home by now.
I regularly share DTPO data and links between application like OmniOutliner, Tinderbox, Skim and BibDesk. Further, through YAML (my choice: you could use JSON or other formats), I can create and store attributed data in DTPO that these some of these programs are designed to process.