Question

I have a few ISO 9000 items on my twiki customisation wishlist. Any help would be most appreciated:

1. I would love to be able to watermark a topic's history pages so that they are easily identified as out of currency (an ISO 9000 sensitivity).
2. I would also like to be able to insert an include that defines the watermark to be featured on a topic page (eg. 'draft' or 'pending').
3. Finally I would like to be able to table the pages which have been assigned a 'draft' or 'pending' watermark.

Environment

-- PaulAnderson - 18 Apr 2006

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

Hm, sounds like a task for a combination of a TWikiForm containing a field 'watermark' (drop-down for 'draft', 'pending' etc.) attached to your topics and an parametrized INCLUDE that implements the watermark depending on the value of the watermark field. This also would allow to design SEARCH queries that list the topics of a certain watermark type.

-- FranzJosefSilli - 18 Apr 2006

What I did was a simple little plugin that changes the html body css class depending on the ISO state. similarly an addition of the state table. And extra, the ISO state was not stored in the topic, rather as an rcs file tag - so that changing the ISO state does not require modifying the topic.

One day I'll find some spare time to publish this work, but right now, i've got to get some food on the table

-- SvenDowideit - 18 Apr 2006

in fact, that's what i've always envisioned PageTypes to mean

-- WillNorris - 18 Apr 2006

I guess there are two issues here. The first is behaviours based on an include, which would be handled well in the vein of Franz's "TWikiForm containing a field 'watermark' attached to topics and a parametrized INCLUDE that implements the watermark depending on the value". Sven's ISO state table sounds exciting also - once the food is on the table I look forward to your publication!

The second issue, however, is item '1' of the question: Can history pages recognise themselves as superseded and be watermarked accordingly? Could the operative that removes editing capabilities also invoke a watermark whether by CSS or whatever?

-- PaulAnderson - 19 Apr 2006

Oh, now I understand your problem. Don't think that TWiki can do this kind of stuff (yet). Watermarking historic topics sounds like a strange concept to me by the way. Maybe this can be done by 'refactoring' outdated content to static html by using e.g. the PublishContrib.

-- FranzJosefSilli - 19 Apr 2006

Interesting idea; I can see how it would enhance usability. See TWiki:Codev.HowToWatermarkOldRevisions for the answer.

-- CrawfordCurrie - 20 Apr 2006

Crawford at his best! Remark to myself: brush up knowledge about context ids!

-- FranzJosefSilli - 20 Apr 2006