A fact is a piece of information gathered during research while building a story. Facts must be verified. Note: should be able to 'discuss and annotate a fact' You may even want to journal dates and times so that it is evident later how this fact was gathered, researched, and verified.
create date (1)
fact data (1)
verified by (1)
Content Package (Composite Content)
Almost no content items are individual 'documents' or 'files' consider the following examples:
Article: An article is made up of copy, source documents, facts, references, images, video, audio etc.
Image: An image is not generally just an lone image file. Images are generally a group of High Resolution, color corrected, black and white, low resolution, and thumbnails.
Video: Videos are generally a collection of raw footage, various encodings, and a 'Still'
There are composite types that contain other composite types: Article (consider that image is composite), a series (a collection of articles).
Under the current model it is valuable to represent these relationships as folders. For example, the image is the folder and it contains it's renditions. This organization has the benefit of being 'browse-able' in most, if not all of Alfresco's folder based adapters (CIFS, WEBDAV, FTP, Web Client.) --Rivet
Source Documents Folder
Images Pkg Folder
Video Pkg Folder
Audio Pkg Folder
Stills and encodings
A Publishing event is an event that is generated every time the content is published. Publishing events can be classed, web events vs print events etc. The publishing event is meant to act as an extension point for metadata that can change on a per publish basis.
Question: is auditing enough to replace the need for a publishing event?
A syndication outlet is a partner which can consume your content. Does this belong in the publishing package or does it belong in a rights management package on which the publish package should rely. We'll finish the notes here then decide; probably the later.
The basic Alfresco effectivity is pretty limited. First, it considers only time and second it does not allow for embargos and blackouts. The concept of an effectivity should be based on assigning a policy to the effectiveness of the document. This allows us to extend policies to meet our needs as they arise. Are the time based or are the based on some other trigger -- it doesn't matter, the question is, 'is the policy satisfied?'
Time Window Policy
The time window policy assumes there is a start and stop date for which the content is effective. The user also has the ability to assign the policy to a 0 or more timezones. A group of these policies could be used to allow content to be time-released.
Start Date Time (1)
End Date Time (1)
Limit to Time Zones (0-n)
Time Delayed Policy
The time delayed policy assumes the content is not available for some period of time but is then available forever after that point.
Refers to an image or graphic that is placed in a layout without context in a layout.
Spiking content is pulling it out of the publication.
A Sidebar is a short piece of text, rarely longer than a single column or page, that is presented outside the narrative flow of the main text. Sidebars are often used for digressions or interesting observations that are related, but not directly relevant, to the main text. (http://www.docbook.org/tdg/en/html/sidebar.html)
A backgrounder is a specialization of sidebar that gives details on the main-text.
A cutline is the caption (text) near a photograph in a newspaper. It informs the reader of who, what, when, where, and why or how about the photograph. Because photographs depict events frozen in time, the first sentence of a cutline is written in the present tense. Additional sentences can be written in present or past tense depending on the publicationâ€™s style preferences. (http://markhancockgloss.blogspot.com/2004/09/cutline.html)
A kicker is a short enticement to direct the reader to a topic/section or a particular story.
A jump is a print term which means that the story continues on another page. Jumps are implemented in two ways in publishing systems: One mechanism is to use a copy component that wraps the copy from a single document on to two or more layouts. The second mechanism is to break the story in to multiple copy documents. The second mechanism has the downside of having to combine the documents later when trying to use the copy outside the system.
Another term for headline
Variants are branches in the life of a copy document. A variant is useful when the workflow for the copy must take different paths. For example: Copy must go to copy-fit for print. In this case the copy will be cut down an in some cases rewritten which is useful for print. However, you may wish to publish the 'full' article on-line. In this case you would cut a variant just prior to initiating the print copy workflow.
Convergence is the process of bringing the on-line and print branches of an organization together.
An embargo is a hold on the publication of content for some period of time.