On 1/30/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > Andreas Hartmann wrote: > > Thinking about this, I think that the navigation visibility property is > > obsolete. With the 1:1 mapping from documents to site structure nodes it > > wasn't possible to decide if a content item should appear in the > > navigation. But if we allow to arbitrarily assign content items to > > navigation nodes, the visibility property won't be necessary anymore. > Sorry, let me undo this. > > There are two levels of visibility: > > 1. visibility in terms of accessibility through the URL space > 2. visibility in terms of appearance in navigation widgets > > I generalized these two options in my former mails, which is incorrect. > Referencing a content item from a site node means to generate visibility > according to option (1). Option (2) should in fact be handled by > specific navigations, so you're perfectly correct suggesting that the > property should belong to the site node.
Adding to this: 1. visibility in terms of accessibility through the URL space (Published) 2. visibility in terms of appearance in navigation widgets (In an Index) 3. other widgets (A Website Map should be able to show documents that are not in the menus. Does it use another Index, or are there levels of visibility?) 4. Security (even if it is "visible" in a menu, it only appears if you have access to it.) How will #2 be implemented? A. Does an Index use a formula for selection (View)? B. Must the documents be manually added to the Index (Folder)? View Indexes are updated when used. Visibility is determined by whether a Document meets the Selection Formula, which could use a "Visibility" property: "if doctype is XHTML and visibility = true". They can be updated "every request", "every request if last update was over an hour ago", "serve request from current index, but update in background if needed", "scheduled updates in background". Views can rebuild themselves from the Document store, but the indexing can be intensive when there are many Documents. Folder Indexes are updated when Documents are added. It is the developers' job to add the Document to all relevant Indexes. Folders store the list of Document UNIDs; a second list stores information such as access lists to each entry for performance. Visibility is determined based on the first list; if a document does not belong, it does not appear. Folders are difficult for developers. Every document save must decide in which indexes this document belongs. The only real world use is email, where the user decides what belongs in each Folder. (And GMail avoids this by replacing Folders with Views that select on a multi-value "Label" field.) solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
