I am evaluating EagleFiler and I like it very much so far.
One of the ways I would like to try using it is as a replacement for a bookmarking tool. Although EagleFiler accels at archiving, I believe Michael Tsai advocates - and I would tend to agree - that memory is cheap now, so why not archive your web page that you're bookmarking. I can't count the number of times I've gone back to find broken URL's or one's where the content has been completely changed - and in my experience that doesn't always mean the old content was irrelevant or poor. The point is, as I capture items from the web, I don't want to have to think about what should be captured as a bookmark versus an archive.
My Concern: Lock-In
Tools come and go. Work flows evolve. If I begin to capture all of my bookmarks in EagleFiler, then I want/have to get my bookmark info (at least) into another tool, do I have a lock-in problem? In other words, is there no way to get my URL's into another tool?
Is there a way to export bookmark related information from EagleFiler?
What Type of information can be exported (url, tags, date, description, etc)?
I think at the bare minimum the user would need EF to locate every Webarchive, extract the source URL, and write it to a html file which a browser could import as bookmarks.
Can this already be done with EagleFiler? Maybe I just don't see it.
Can this already be done with a (simple?) Applescript?
I took a quick look at EF's Applescript dictionary and I don't think I see the commands that would support this.
Beyond the bare minimum ...
I. It would seem criminal to lose the tag data. (and any other "easily" exported metadata eg description/note). Should probably be exported in a format compatible with delicious.
2. A "Nice to Have" : An option to maintain folder hierarchies.