Fundamentally I'm with you, and your users, on this Ivan - it's just
another type of content.
Unfortunately I'm an idealist, so in practical terms you probably shouldn't
do it!
The main reason is the law of unintended consequences. Sometime you go down
a path (especially with SharePoint's complexities) and then hit a show
stopper, work around that just to create two more...
So, even after a proof of concept, make sure you have a big red RISK item
in your plan with the cost of abandoning the approach late in the project
life and the possibility of impacting currently unknown requirements.
Regards, Mike.
Ivan Wilson To
<iv...@sharepoint "[email protected]"
gurus.net> <[email protected]>
Sent by: cc
[email protected]
Subject
RE: Storing documents in a Pages
library
11/02/2009 09:41
AM
Please respond to
[email protected]
Thanks for your feedback Paul (Noone and Culmsee)
Yes, they consider HTML pages as just another type of reference document. I
can understand their point of view.
I realize that from a SharePoint perspective it sounds odd to use non-page
content types in the Pages library. However, so far it is working fine. It
is a proof-of-concept, so now is the time for us to identify issues, but so
far so good.
As Homer says, “What doesn’t kill you makes you stronger”
Ivan
From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone
Sent: Wednesday, 11 February 2009 8:47 AM
To: [email protected]
Subject: RE: Storing documents in a Pages library
Are they expecting to treat HTML pages within the site’s Pages library as
web pages, or as reference docs?
What the heck is going to happen to the navigation I wonder? I’m still
concerned about the base columns and functionality of a Pages library and
what this will mean for document content types which inherit from a
different base set.
Again, I wish you every success. Please keep us posted with screenshots and
updates (or me at least!).
From: [email protected] [mailto:[email protected]] On Behalf Of Ivan Wilson
Sent: Tuesday, 10 February 2009 4:32 PM
To: [email protected]
Subject: RE: Storing documents in a Pages library
Hi there Wilson
Yes, I do like to live on the edge :)
The volume of documents + pages for each section is not excessive. The
largest section has a little over 600 entries today. I’m not expecting to
have any performance problems.
Paul T. – in reply to your post, the client wants their staff to have a
similar experience in SharePoint to what they have today for finding
content. They currently treat a HTML content page the same as document. It
will be strange for them to have to browse two different libraries just
because one item is a web page and another item is a PDF document.
Ivan
From: [email protected] [mailto:[email protected]] On Behalf Of Wampers,
Wilson [Talent International]
Sent: Tuesday, 10 February 2009 3:01 PM
To: [email protected]
Subject: RE: Storing documents in a Pages library
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
Other lists you might want to join: 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
Other lists you might want to join: 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
Other lists you might want to join: 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
Other lists you might want to join: 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
Other lists you might want to join: 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
Other lists you might want to join: 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
Other lists you might want to join: 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
Other lists you might want to join: 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
Other lists you might want to join: 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
Other lists you might want to join: http://www.codify.com/lists
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
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
Other lists you might want to join: http://www.codify.com/lists
_______________________________________________________________________________
Unencrypted electronic mail is not secure and may not be authentic.
If you have any doubts as to the contents please telephone to confirm.
This electronic transmission including any attachments is intended only
for those to whom it is addressed. It may contain copyright material or
information that is confidential, privileged or exempt from disclosure by law.
Any claim to privilege is not waived or lost by reason of mistaken transmission
of this information. If you are not the intended recipient you must not
distribute or copy this transmission and should please notify the sender.
Your costs for doing this will be reimbursed by the sender.
We do not accept liability in connection with computer virus, data corruption,
delay, interruption, unauthorised access or unauthorised amendment.
_______________________________________________________________________________
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--------------------------------------------------------------------------------
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
