It sounds like you are talking about integration with some kind of external content fileserver. That's definitely out of scope for Koha presently. <br><br>Rewrite rules can be used to make koha local addresses map to remote ones. This would be advisable to keep the data free from the particular implementation, domainname or address of your fileserver. Koha itself can't do this automatically, of course, since it doesn't know anything about your fileserver. <br>
<br>What you might want to work on would be a process where the file is loaded into the fileserver along with the biblionumber. Then you can work on a report from the fileserver to mechanically generate 856$u fields paired with the biblionumber for loading back into Koha. Or if the destination filepath are deterministically based on the biblionumber, then you can map the target mechanically using Apache rules, and all you'd need was an 856 plugin for cataloging.<br>
<br>-- <br>Joe Atzberger<br>LibLime - Open Source Library Solutions<br>
<br><br><div class="gmail_quote">On Wed, Jun 24, 2009 at 11:22 AM, Sébastien Hinderer <span dir="ltr"><<a href="mailto:Sebastien.Hinderer@snv.jussieu.fr" target="_blank">Sebastien.Hinderer@snv.jussieu.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Doug and all,<br>
<div><br>
> That is where the Rewrite command comes in. Check the Apache doc.<br>
<br>
</div>I think there is a misunderstanding between us.<br>
I perfectly understand what apache rewrite rules can do, but I do also<br>
believe that, for the problem we are discussing, they can not help.<br>
<br>
Assume a bibliographic record present in Koha with no physical copy<br>
attached to it. Then, you, as a librarian, want to attach a file to the<br>
bibliographic record. So you select a format, a filename which is stored<br>
on your hard drive and ready to be uploaded, and you submit all this<br>
information to koha. The file will be stored somewhere on a file server.<br>
The question is: which part of code should be modified so that Koha<br>
generates atomatically a URL and stores it in a 856$u UNIMARC field of<br>
the bibliographic record.<br>
This URL should be a valid URL which gives the user an access to the<br>
file, perhaps by means of apache rewrite rules.<br>
The question is really: how to do to have KOha modifying the MARC<br>
records to store the right URLs. Moreover, I don't think this can be<br>
done with Koha so the real question is which script or module should I<br>
modify to achieve such a result.<br></blockquote></div><br>