Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

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 ForumsRepositoryRepositoryImplications of using 100+ repository modules in a portal?Implications of using 100+ repository modules in a portal?
Previous
 
Next
New Post
10/15/2007 5:50 AM
 
Raghu Pandey


Joined: 12/13/2005
Posts: 98

Hi Steve,

i am preparing a portal for a university which has 35 departments or colleges. So i am giving them an intranet portal which has 1 main portal and 35 child portals. Now on EACH child portal i need to add around 100-110 repository modules for various purposes and each module will have its unique 6-7 categories.

This means i am looking at approx 3500 repository instances under 1 main portal.

What could be the technical implications of this structure from

1) Application stability perspective, and
2) Admin's perspective i.e. portal management.

Has this been done by any of the users before?

Any inputs shall be greatly appreciated

Raghu.

Author - 'Become an iMature Student'
Book on 'Internet Maturity' for all students.
 
New Post
10/15/2007 11:18 AM
 
Steve Fabian


Steve Fabian's Avatar

Joined: 3/4/2003
Posts: 2111

I may be wrong, but I doubt that anyone has implemented that number of repository modules within a single portal. I am not aware of any 'technical' reason it would not work.  the only comment I have is that you might think about the overhead of maintaining that many unique instances of the module versus some small changes to the code which *might* allow you to have only 1 instance of the module and have the context of the module (categories, files, etc) filtered based on security roles...

not sure if that would work, especially if each instance will have separate unique categories, roles, etc. Certainly if the roles and categories where going to be duplicated across all those instances I would not want to have to perform the multiple maintenance required.

so, in summary, I see no reason why your structure would not work the way you've laid it out, however, I think it might benefit you to think about what changes could be made to the module to allow you to meet your goals through a single instance ( or at least a dramatically reduced number of instances ) of the module.



 Steve Fabian
e: steve.fabian@gooddogs.com
w: http://www.gooddogs.com
 
New Post
10/15/2007 2:35 PM
 
Brad

Joined: 6/11/2007
Posts: 65

Doesn't the repository store the information in one directory per portal (or optionally per user)? If you're using FAT32 the maximum number of files allowed in a folder/directory is 65,534.  NTFS gives you 4,294,967,295 files per directory.  No reason anyone should be using FAT32 on a server, but just in case you WERE considering it...
 
New Post
10/15/2007 4:02 PM
 
Steve Fabian


Steve Fabian's Avatar

Joined: 3/4/2003
Posts: 2111

when logged in using the HOST account, you can set the physical folder path that each repository module will use to store it's files. So you can each have one folder per repository instance.



 Steve Fabian
e: steve.fabian@gooddogs.com
w: http://www.gooddogs.com
 
New Post
10/16/2007 7:47 AM
 
Raghu Pandey


Joined: 12/13/2005
Posts: 98

Thanks Steve!

Its valuable input. So iam taking a cue from 2 of your sentences.... "dramatically reduced number of instances" and "I am not aware of any 'technical' reason it would not work"

i'll re-look into my information architecture to reduce the number of instances and let it go Live... as it is said 'If it ain't broke don't fix it' so no tinkering of code. I'll share my experiences with the community :)

Author - 'Become an iMature Student'
Book on 'Internet Maturity' for all students.
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryImplications of using 100+ repository modules in a portal?Implications of using 100+ repository modules in a portal?


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out