Hi Ivan,
You daredevil J! Have you considered the volume and size of documents and potential performance hit? I think this might play a significant role! Cheers, Wilson From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 10 February 2009 12:36 To: [email protected] Subject: RE: Storing documents in a Pages library "I will be using metadata and grouping to create hierarchical views of the content" I'd really like to see that. From: [email protected] [mailto:[email protected]] On Behalf Of Ivan Wilson Sent: Tuesday, 10 February 2009 2:33 PM To: [email protected] Subject: RE: Storing documents in a Pages library Hi Sezi I think I may be lucky on this project. I do not want any of the Pages content to display in the navigation. I have turned off Show Pages in the Navigation settings page. I have been configuring this in my test environment today and all seems fine so far. I will be using metadata and grouping to create hierarchical views of the content for end users. I'll report back after we have tested this with end users and let you know if we ran into any issues. Thanks Ivan From: [email protected] [mailto:[email protected]] On Behalf Of sezai komur Sent: Tuesday, 10 February 2009 1:59 PM To: [email protected] Subject: Re: Storing documents in a Pages library Ivan, One problem you will face is documents appearing in your navigation. I think all items in the Pages library are added to navigation, irrespective of content type, so if you add a document content type to a Pages library and upload documents to it associated to the content type, the document is going to show up in your navigation menus, which is something you probably don't want to happen. I agree with Paul's comment re hierarchy in a site. The only standard way to create hierarchy in WCM sites is to nest sites, you can't create any real hierarchy in a single site apart from having one page as the Welcome/Default page for the site and other pages as secondary/siblings to the welcome page. Sezai. On Tue, Feb 10, 2009 at 11:42 AM, Paul Noone <[email protected]> wrote: I wish you every success and am curious to see if any technicalities arise once you start populating. As for me, I've always found the constraint of one Page library per site very restrictive. No to mention the inability to create any real hierarchy. From: [email protected] [mailto:[email protected]] On Behalf Of Ivan Wilson Sent: Tuesday, 10 February 2009 1:02 PM To: [email protected] Subject: RE: Storing documents in a Pages library Thanks Paul, I'm using different content types for the documents which should allow me to bypass the issues that you mention. I am looking to consolidate all content in each section into one library, so the fact that I can only have one Pages library is ideal for me. Ivan From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 10 February 2009 12:29 PM To: [email protected] Subject: RE: Storing documents in a Pages library The Content Types have inherent differences and functionality that would make that a very bad idea. You can store web pages (as sites) in a document library but if you're talking about storing 'documents' in a dedicated Pages library on a publishing site then I think you will run into all manner of problems. For starters, each site can only have one Pages library. Then you have the publishing features to consider. Then there might be mandatory fields which would simply make no sense for certain types of documents. On the flip side of that, Document libraries (Documents, Images, Forms etc) all have functionality which suits those document types and may not be considered appropriate for pages. I'm sure there are other good reasons I haven't considered. From: [email protected] [mailto:[email protected]] On Behalf Of Ivan Wilson Sent: Tuesday, 10 February 2009 12:22 PM To: [email protected] Subject: Storing documents in a Pages library I'm considering using the Pages library on publishing sub-sites to store both the WCM pages and the documents for that section. Apart from not being able to use folders, is there any other technical reason that might affect this? I want staff to be able to use the standard browser functionality to create their own views of their documents and pages. Their current intranet treats a web page as if it was a standard file. If I separate these into a Pages library and a Documents library then they will lose the ability to browse through their content as they do today. I don't want to go down the path of configuring Data View web parts or custom development. Ivan ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
