here's the definitive answer ...
it depends on what you mean by "directly to the individual document".
That can be intepreted 2 ways.
1) when a user clicks on a link, they should be redirected to the page with the repository module that contains the document and that document should be displayed, at which point they can download the file by clicking on the DOWNLOAD link associated with that item.
2 ) when a user clicks on the link, they should see the File Save Dialog box popup and they should be able to open or save the document without them being redirected to another page.
You CAN do #1 right now. By including a [PERMALINK] tag in your repository template.html file. The tag will generate a URL that use can then use on any page or other module. So, to use the [PERMALINK] feature you would do the following...
1. add a [PERMALINK] tag to your template.html file in the location where you want the hyperlink generated
2. upload item(s) to your repository module
3. for each item displayed you will see a hyperlink titled 'Permalink'. Right-click on the hyperlink and select "Copy Shortcut" .. or just click on the Permalink hyperlink and then when the repository page is displayed, copy the URL from the Address bar.
4. now, on another page, you can insert a link in an HTML/Text module or any other type of module and paste the Permalink URL.
When a user clicks on that hyperlink, they will be redirected to the page with the repository module and ONLY that specific file will be displayed, they do NOT have to search for it. The Permalink will filter the repository module to only display that one item. The user can then download the file associated with the item by clicking on the DOWNLOAD link.
if you are looking for #2 ... then no, you cannot craft a link ( and by link I mean a standard URL that could be used in an HTML/Text module or any other moduel ) that will result in a repository document being directly downloaded without redirecting to the page where the repository module resides.
So, the obvious question is ... why the hell not???
answer: the current version of the repository module ( and I am only referring to the current version, all of this will be thrown out the window when 4.00.00 is release which is a complete re-design of the module ) there are a couple of features that the module adds above and beyond a simple documents module. The first is security. Security is enforced at runtime when the repository page is displayed. The current user's security roles are compared to the module's settings to see if the user should be able to download items from that particular repository. Since the code to do this validation is part of the repository module, having a URL link on another page that attempts to access a physical file stored within the portal's folder structure will not execute that code so there is no way to enforce any security restrictions. Secondly is counting the number of downloads. Again, the logic to increment the number of times a file is downloaded is implemented within the repository module's code. So if the repository module itself is not being displayed, then it's code is not being executed, and the code that updates the number of downloads is not being executed, so you lose that basic functionality with a direct link.
I hope that's clear and you understand the issue, and hopefully, option #1 will suffice for now. And as I said, with 4.00.00 it will be a whole new ballgame, but that's not going to help you today.