Windows Server

Guest

I'm looking for a general solution for managing multiple instances of
a document in the portal library in a way that there is only one
physical copy that has to be maintained.

The best solution I can come up with involve using shortcuts (.url
files). Here's some of the issues that I've found with working with
shortcuts in sps2003:
(Note: Shortcuts are not allowed in doc library by default. Easy to
reconfigure to allow)

Shortcuts cannot be uploaded with the html interface. Instead of
uploading the shortcut, the page pointed to is uploaded. Shortcuts must
be uploaded with the web folder.

The author could put the shortcut in a folder so that a reader has
access to the shortcut but not to the page pointed to. (this is tricky
to fix in general, since security could even change over time but the
problem could be managed given the business logic of specific
implementations)

Change alerts on shortcuts don't trigger if the page pointed to is
changed.
Strangely, even if the short cut is modified, there is no change alert.
The discovery alert works and can be triggered again if the shortcut
name is changed.

There is nothing stopping somebody from removing or renaming the page
pointed to by shortcuts and breaking it.

--------------------------------------------------------------------------------

Here's the best development solution I can come up with to help
automate the solution:

A custom web part helps the user create and maintain the short cuts.
In the webpart interface the user would select the source document and
the doc libraries where the short cut would be copied. (Business logic
could be applied here to be sure to limit the list of places the
shortcut is copied so that any reader could have access to the page
pointed to) When the shortcuts are created by the web part it would
write to a database where the source document is and where the short
cuts were put. (This might not be necessary, the information could come
from the document database that sps keeps) At night a scheduled task
would run that would look at the original document and if it changed
since the last time the task ran, it would change the shortcuts in a
way that the alert system would pick it up. Also, the task would
check if any shortcuts were broken and email the authors of the
problem.

general solution for managing multiple instances of a docume

	Windows Server Forum Index -> Portal Server Development	All times are GMT
Page 1 of 1