New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsDocumentsDocumentsIdeas for the module...Ideas for the module...
Previous
 
Next
New Post
6/24/2005 2:11 PM
 
cfrankland wrote
  • Pull Word, Excel, Powerpoint, Text, and PDF file contents into the DNN search provider

And wouldn't it be great if the summary/tag fields were pulled into the item data grid....instead of having to re-key that stuff...  The Offcie docs and other XML files should be normalized.  TIFFs and other image formats might require more research.

 
New Post
6/24/2005 6:37 PM
 

Visual

  • Configurable fields: you should be able to define which fields should be displayed for the module and the title for each field. This would allow to have custom and specialized information on each documents module.

Content

  • Secure documents: add option to secure documents. Uploaded documents could be renamed (adding .resources for example) so they cannot be downloaded directly via url. Only users with right permissions should be able to download.

Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
New Post
7/6/2005 9:45 PM
 

 

  1. Subscriptions that notify the user when a document changes.
  2. Subscriptions that notify the user when a new document is added to a specific category.
  3. The capability to work as a repository/library of documents and select wether to show the whole library or only certain categories in an instance of a module
  4. Restrict the type or types of documents a certain category can hold.

Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
7/8/2005 9:32 AM
 

Try to create a document control, that can easily be integrated in other modules, but provides security, calculation of size and meta data, upload, ...

A control will leverage the needed effort for adding download functionality to any module and improve usability due to consistency.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/15/2005 9:46 AM
 
vmasanas wrote
Visual
Configurable fields: you should be able to define which fields should be displayed for the module and the title for each field. This would allow to have custom and specialized information on each documents module.

Perhaps this should use a repeater and switch templates based upon the type of content.  As cfrankland pointed out many filetypes have tagged headers which could be read for properties to be displayed....so different templates would be needed.  Something like:  http://www.codeproject.com/aspnet/ObjectRepeater.asp

I'd want to index these properties for searching, but I'm not sure that I'd want to index the entire document contents.  For one reason, image types (or embeded images) could suck up a lot of db--and never be a search "hit."  For another reason, if I wanted the content in HTML, or some central CMS, wouldn't I put it there instead of leaving it in loose files to begin with?  (Not clearly stated, I'll go get some coffee...)  My point is I can see both sides on importing the content--give me a module setting to pick the indexing level: None, FileSystemProperties, DocumentProperties, or FullContent.

vmasanas wrote
Content
Secure documents: add option to secure documents. Uploaded documents could be renamed (adding .resources for example) so they cannot be downloaded directly via url. Only users with right permissions should be able to download.

That's my point above, there are many ways to secure documents.  Some of these are considered because of the MediumTrust issues, some are chosen because of a desire to link to an existing CMS, some are chosen because of DOD requirements to isolate content storage on boxes other than the webserver... 

I'm not sure how widespread Bo thinks a FileSystemProvider would be used throughout DNN.  To me DNN is a MS ASP.Net product, and so it does assume Windows for the filesystem, and I'm ok with that for the general system.  But for document content, security requires that I MUST target other providers, I cannot leave content anywhere under the IIS site....thus I've written my own documents modules.  Although I cannot release that specific code, I'd love to see this module be able to choose between various mechanisms for retrieving content.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsDocumentsDocumentsIdeas for the module...Ideas for the module...


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.