View Single Post
Old 12-02-2012, 07:19 PM
schferk schferk is online now
Registered User
Join Date: 11-02-2010
Posts: 151
"Let's say your UR db is in c:\data. If you put files in c:\data\files, you can then link to those and even if you move the whole c:\data directory somewhere else, the links will be maintained."

That's as you'd expect this. Of course, this doesn't resolve problems by renaming. (I, e.g., do lots of renaming, because of adding / changing multiple "tags" in filenames (I have stopped to do them as "comments" within ntfs metadata).

"Whether to link or store really depends on what you are trying to do."

That's confirming what I said. But you mention another aspect, which is backup. Since UR doesn't offer versioning (yet), even for backup reasons, it could be preferable to have these files stay external, and let your synch routine doing the rest, incl. versioning within your archive folder.

"Any file item can be linked or stored. Even imported files have the option to only be linked."

OMG! PureMoxie, I'm generally not into semantic nitpicking (cf. the reprimand I get when in outlinerswforum I dared use the terms "programming" and "scripting" as synonyms when in fact all I wrote about was scripting), and I'm grateful you try to clear things up, here, with me, but in this extreme case, please allow my asking again: "Even imported files have the option to only be linked." - huhhhhhhhh????

Meaning, I don't even understand what that could mean, besides the fact that I try to distinguish the different possibilities by their respective terminology, too.

And btw, UR seems to use "store" and "import" as synonyms, but I also discovered another term (I cannot find again, on top of all those to be found in my post above).

So there remains some semantic chaos, for the time being!
Reply With Quote