Document Library Browser Web Part
Background
My task is to show a process map image in SharePoint, which should be clickable. Think about imagemap in html. In some areas, you are taken to other process map images, while others trigger a popup.
"Connected" to each process map is a collection of documents. These documents are stored in the document library. There is one process map for each folder in the document library. Documents must be shown next to the image. A person clicking on an image or folder to navigate the hierarchy should also be able to upload, download and delete documents.
Question
What would be the simplest solution for this?
My thoughts
... for now, create a custom web part that I add above the document library browser (default in MOSS 2007). This web part reads some xml file that specifies the image to display and the areas to click. It listens for some events from the document library, such as clicks on folders in the browser, or reads the current URL to find out where in the folder hierarchy we are now, and it displays the correct process map image. When the image is clicked, the web part updates the image and reports to the appropriate document library.
Is it possible? Am I wrong? How do I interact with the document library?
Thanks Martin
source to share
Ever since I was here ... Actually solved this one.
We've created two web parts, one for navigating processes and one for filtering documents in a document library.
The Process Navigation Web Part is actually a Web Part that looks for a specific request URL and adds ".html" to it. Then it searches the document library for that document. If found, this document is rendered inside an iframe. Plain!
html documents are created by Visio and exported to html and then loaded into SharePoint. Links in a Visio drawing drive the application with requests.
The web part that renders matching documents also looks for a specific request in the URL, then sends filter parameters to the document library through the IfilterProvider interface. I plucked this IFilterProvider example on MSDN and ran it in the parameters url and then made the controls invisible to the user.
Really simple solution, although the customer has to work hard to incorporate their company processes into it. And it is somewhat prone to errors and is probably a sucker for making changes to the data.
source to share
My thoughts are that you are creating a web part that renders your imagemap and outputs (provider) matching criteria of another web part that consumes it and renders the files in a document library.
You can achieve this by creating your own website that displays a document library based on a CAML query. Each image sends a different CAML request to the document library web page.
Hope this helps. Please provide information on how you resolved this issue if you have already done so.
thank
source to share