I'm kinda confused... what is it you are trying to do?
Are you trying to do high level design? If so the best approach would likely be
to:
1. research what is currently implemented
2. document all you would like to content stuff do and where the current model
doesn't match up
3. fill in the gaps in the design
As for #2, why would multi-page content even be split into different content
records? For most cases I think it would make more sense for things to be
organized in other ways. Do you have a requirement you're looking at that needs
to track the pages separately in the system, ie in different templates or
binary documents? Especially for templates these usually just tend to flow and
you often don't even know what the page divisions will look like in advance.
-David
Al Byers wrote:
I think it would be helpful to agree on how content management should be
used. I am thinking primarily of things like news articles, blogs, forums,
etc. They all have a lot of similarities and if there were patterns for
designing them, it would allow for more reuse.
Often with website content there is content and then there is a summary
piece that may go on a front page and then points to the main content. In
the past I have used "SUB_CONTENT" as the
ContentAssoc.contentAssocTypeIdvalue from the publish point to the
main content. Then I associate the
summary content to the main content with a
ContentAssoc.contentAssocTypeIdvalue = "SUMMARY". But I can see that
there will be situations in which
things get more complicated, where there will be comments and surveys
attached to the main content. Also, I recently made the main content
hang on
the summary because at the time it made more sense.
Question #1: Should ContentAssoc.contentAssocTypeId be used to link the
other types of content to the main content (ie. "COMMENTS", "SURVEYS",
etc.)
or should ContentAssoc.contentAssocPredicateId be used (ex. "summarizes",
"comments", etc.) and the contentAssocTypeId always be SUB_CONTENT?
Question #2: How should multiple page content of the same article be
structured? All content associated to the publish point as main content
with incremented ContentAssoc.sequenceNums or should they come off of the
main content and each page extend from the preceding page?
Question #3: Should we do away with the idea of "main content" and make an
"article" a complex, virtual content (sort of a placeholder) off of which
all data content hangs (main, summary, comment, etc.)?
-Al
