Hi,

You guys have done an awesome job with the repository!! Many thanks to the team!!

I have a few feature requests for the next build, mostly from my users of the repository.

ENH: More paging conrols - When you have more than 3 or 4 pages in a category or when viewing all entrys, its difficult to page your way through the repository. I would suggest something like this:
<<  Prev 1 2 3 4 5 of 13 Next >>
Clicking the << or >> would take you to the 1st or last page in your current view of the repository, with the numbers being clickable to jump that particular page, Prev and Next work as normal. The numbers would change as you page through, allowing you to jump around a little bit. Another option would be to have a drop down box of the pages in your current view of the repository to jump to that page.

ENH: User selectable template to view the repository - The admin could have 2 or more templates checked in the settings for the user to select from when viewing the repository. Best usage scenario i can forsee is a Full Template or Simple Template that the user can select from while they are browsing the repository.

ENH: User selectable number of entrys to view per page - Allow the admin to set a Minimum and Maximum value per Template of entrys to show on a page. As an example, the Simple View Template is a one line listing of entrys in the repository, so as admin, i would set a min of 25 and a max of 100 entrys to show per page, and the user can select a value from a drop down box when viewing entrys using that template. Now the Full View Template is a more detialed listing of entrys in the repository, so as admin, i would set a min of 10 and a max of 25 entrys to show per page, and the user can select a value from a drop down box when viewing entrys using the Full View template.

Thanks for listening (reading) !!

If you would like a more detailed description, or don't understand something, i will be glad to post more info or even a link to something similar as i have described.

Thanks again,

Gary

I'd like to re-iterate the mega-kudo's to everyone involved in core DotNetNuke development and also the development of modules like the repository.  I was just talking with one of the members of my IT department and he came up with a great feature addition.  We have had problems for years with providing large data sets to researchers and other people who have no idea how to use an FTP client, and since I refuse to send more than 5 megabytes through e-mail we commonly place temporary downloads onto hidden parts of our website.  Repository can take over this function, but what would be great is an expiration property that would wipe a file from the system after the file has expired, similar to the entrance and expiration properties we see on pages, modules, and other DNN content.

May I add a request here?

In contrast to the expiration date for a file, I'd like to have a 'valid from' or 'downloadable from' date so that I could upload a document and specify a date from which it becomes available to download.  This would allow me to go on holiday having uploaded items which then would only become available while I'm away.

Barry