I would like to try to accomplish the following:

On our school's library website, I have several repositories within an aggregator.  You can see it here. I would like to implement a suggest a link feature similar to this that would be placed in it's own module down the right side of the page so that the user sees the aggregated repository in the content section and can quickly go over to the right pane and use the suggest a link module to add a link that would then be cued for approval by the moderator.

I know in this thread Steve created a starting template that is now part of the templates that comes with the default install.  I want to extend this concept a little so that whoever is suggesting a link can not only suggest the category the link should go in but also the respective repository.  There are many folks who are part of a librarian's user group who would like to add links to our repository and I want to make it as easy for them as possible.

What would be the best way to tackle this?  Any suggestion appreciated.

Paul

Hey Paul,
Not ignoring you .. just trying to think of a way to accomplish what you're asking for ...

I can't think of any way to do it without code changes. However, if you're up to code changes, here's my thoughts.

1. take a look at the Dashboard code. It has logic to query the modules table and find all of the repository modules that are installed. It uses that to populate the dropdown list of repositories so you can associate a dashboard with a specific instance of a repository module somewhere on your site.

2. you'd have to add a new tag to the form processor to inject a combo box on the upload form and populate it with a list of repositories, similar to what the dashboard is doing. that would allow your users to select a specific repository to upload the item to

3. when submitting the item, you'd have to replace the current "ModuleID" with the module id of the selected repository from the dropdown. Again, look at the repository dashboard code, that's pretty much what it does, stores the module id of the selected repository module in the drop down list

Those changes should do it. When a user uploads an item, they could select a repository, and when the back end function is called to add the item, the module id of the selected repository will be passed as the module id and the stored item will be associated with that specific instance.

:) 

when you add the code to the form processor to create and inject the dropdown list, you can certainly filter which repositories are added to the list at that time. You could either do it by artifically enforcing some kind of naming convention of the repository modules and look at the module title only adding ones that match some criteria.

or, you could use the form.xml method and inspect a setting and use that to populate your dropdown.

for example:

Then in form.ascx.vb when you're processing a REPOSITORYPICKER tag, create your dropdown list control, call the Controller function to get a list of all the Repository modules on your site, then one by one, check to see if the module id is in the ModuleIds setting from the xml file. If it is, then add it to the dropdown.