A-Z glossary of PageSeeder concepts


Use Cases

Computer science has long discussed the issue of redundancy vs dependency and this article will not advance the argument. It may help to explain how the PageSeeder link model can address use cases that may otherwise require data duplication. However, by avoiding redundancy, dependencies may be created instead.  Consider the following scenarios:

  • using the PageSeeder permission model and cross references (xrefs) to resolve different views of the same document to members of different groups. Think of teacher and student views of the same textbook,
  • multiple parties that want to review the same document at the same time can share instead of duplicate,
  • using transclusions to display the same “live” content in multiple locations (documents).

By avoiding duplication, dependencies have been created. Which is worse can only be determined by someone with the appropriate level of experience and familiarity with the specific use case.

That person may find the following patterns of value. 

Publish duplicate

(also known as a Filter duplicate)

This pattern is the safest and easiest way to manage duplicated content. Editing and review uses a single copy of the data only. Markup is used to identify the content unique to each deliverable. Developers use that markup to process out duplicated, specialized content to different audiences (teachers, students), formats (PDF, web) or states (draft, final).

If a Publish duplicate is “additive” – information is added for different audiences, a Filter duplicate is “subtractive” – the view is created by filtering out information not relevant to a particular view.

Shallow Duplicate

This is the pattern available through the Documents Explorerfor copying a single file. With a shallow duplicate, links that terminate outside the document are copied but not their destination. This means links in both the original and the copy refer to the same destination.  

Collection Duplicate

This pattern replicates an entire collection of content and then updates the path references to reflect the new location. It must be coded for each circumstance but this tutorial may provide some guidance for developers – Creating document collections

Created on , last edited on