The IMesh Toolkit

[ Work In Hand > Components> Annotation> Annotation Design ]

Index to Operations

Notes in Respect of Screens

Using this page as the basis for visiting the screens in the exercise will permit you to see the screen design for yourself but also consult the notes about changes or rationale which appear beneath each hypertext link. In order to return to this page one merely needs to navigate back to any annotations view page and click the "or return to index" link at the top of the page. This will lead you back to the brief index called the Contents of Operations page; from there you can select another link to any section in this page.

It is suggested that you do not take the screen navigation beyond the scope of the operation described. Given these screens do not possess a backend, they will eventually start to show false. Once the operation described is complete, return to the index.

Return to Contents of Operations

Return to Introduction to Prototyping

Index of Operations:

1.login

A simple user login and password authentication system which permits Moderator to access the system without great complexity. Should there be an incorrect entry, the user is passed to an incorrect login warning page. Clicking the 'Enter' button leads the Moderator to the page for viewing annotations received.

2.view example of annotations page

The View Annotations page contains 3 main areas. The summary table, the detailed view of a specific annotation, usually the first in the summary table and the search service.

The Summary Table

Column 1: Status of the annotation received in terms of Moderator actions as follows:

new : Not yet subjected to any Moderator action
accptd : Accepted (see below: accept first annotation on list passed by Automoderator)
edtreq : Edit Request (see below: edit first annotation on list passed by Automoderator)
rjctd : Rejected (see below: reject second annotation on list barred by Automoderator)
arjctd : Autorejected (see below: auto-reject second annotation on list barred by Automoderator);
N.B.: Meaning of autorejection

Column 2: Date yy-mm-dd

Column 3: Email address of submitting annotator

Column 4: Outcome of automoderation process:

barred : automoderation system identified sufficient items in annotation to calculate a value above risk threshold. Whilst on the annotations database, the annotation is barred from public viewing until Moderator action is taken on it.
passed: automoderation system calculated a value below the risk threshold and made the annotaion publicly viewable. It will remain so unless Moderator edits, rejects, autorejects it.

Column 5: Rating:

annotators in filling out their comments on the resource record enter marks out of 5 for approval, 5 being highest.
automoderation calculates part of the risk factor on the basis of ratings, i.e. below 3 constitutes a higher threat value

Column 6: Subject

ideally the annotation would place the record title in the subject line
thereafter the beginning of the message as a thread

Detailed View

The detailed view divides into 3 areas:

Top line : timestamp giving date and time of annotation submission; annotator email; passed/barred; rating
Second line : Record title; record url e.g. ?query=1004615393-19090&database=sosigv3
Text area : Subject; message

The View Annotations page when loaded would show the detailed view of the first annotation in the summary table until a Moderator clicks the link of any annotation in column 1. At such a point the page would reload with the detailed view of the selected annotation.

Search Service

Permits the searching of annotations database on free text basis. Results page reflects the view annotations page layout.

3.select next or previous ten annotations

Effected through use of the "Previous" and "Next" buttons. Given there are only 2 annotations on this "database", clicking the former will reload the current page. "Next" will indicate a blank table. Ideally these would grey out when they do not apply. (Note that ideally there ought to be a table of 10 annotations on each view annotations page).

4.re-order any column in the annotation view page

This screen demonstrates how each of the six columns of the View Annotations page described above can be resorted. For example, column 1 would sort ascending or descending on 'new','accptd','edtreq', etc. Sorting on the rating column would permit grouping by rating values.

5.select second annotation for viewing

The View Annotations page when loaded would show the detailed view of the first annotation in the summary table until a Moderator clicks the link of the second annotation in column 1. At such a point the page would reload with the detailed view of the selected, second annotation.

6.accept first annotation on list passed by Automoderator

From the View Annotations page, selecting the first annotation in the table will drop the page to the detailed view and the 'Accept' button beneath it. Clicking the latter takes one to the Accept Annotation Page with the option to :

send an acknowledgement
cancel the process, which returns to the previous state of the annotations viewed
exit moderation service, whereby the whole application can be left

Opting to proceed and send an acknowledgement causes the default message shown, (text in blue), to be mailed back to the annotator on the email address supplied together with the annotation subject and message. The Moderator is then returned to the View Annotations page where the status of the annotation in column 1 of the summary table will have altered to 'accptd' and ideally the datestamp and Moderator's action is included in the detailed view, (not shown).

7.edit first annotation on list passed by Automoderator

Whilst the Automoderator has passed the annotation as representing no threat against its evaluation settings, the Moderator nonetheless inspects the annotation by clicking 'new' against the first annotation in the summary table. The detailed view is displayed and the Moderator spots something in the text which would best be amended before the the annotation is accepted. In order to carryout that editing process the Moderator clicks the 'Edit' button.

The Editing Page

The page presents a modified form of the detailed view to the Moderator which includes a text entry area for the addition of wording etc. whilst still showing the original message and associated information. The text area is prefaced by a standard wording requesting the annotator re-submits the annotation. When the amendment is added the Moderator can then:

send the edited text and request to the annotator to repost the annotation
cancel the operation and return to the View annotations page
exit the entire service

Note there are also two alternative buttons for send or cancel near the text area for old hands who prefer not to scroll down; they have the same effect as explained above in the first two bullets.

The Moderator on clicking the "Send Edited Version" button causes the edit-request to go out to the annotator. At the same time the relevant annotation is rendered invisible to those viewing the annotations even though it is retained on the annotations database. (When/if the annotator submits the revised annotation this is most likely to be passed by the Automoderator and accepted by the Moderator and in effect will supplant the edited original version; it will be viewable throughout).

At the same time the system will return the Moderator to the View Annotations page where the entry in column 1 will have altered from 'new' to 'edtreq' to indicate the change in its state and its removal from public viewing. The Moderator has the option to purge the edited annotation if desired though typically this would not occur until the revised version has been subsequently accepted. (See accept first annotation on list passed by Automoderator ).

8.reject second annotation on list barred by Automoderator

As the Automoderator has barred the annotation as representing a threat against its evaluation settings, the Moderator closely inspects the annotation by clicking 'new' against the second annotation in the summary table. The detailed view is displayed and the Moderator recognises something in the text which would render the annotation unacceptable and opts to choose the rejection option. In order to carry out that rejection process, the Moderator clicks the 'Reject' button.

The Reject Annotation Page

The page presents a modified form of the detailed view to the Moderator which includes a text entry area for the explanation of the rejection whilst still showing the original message and associated information. The text area is prefaced by a standard wording explaining the reason for the annotation's rejection. When the explanation is added the Moderator can then:

send the rejected text and explanation to the annotator
cancel the operation and return to the View annotations page
exit the entire service

Note there are also two alternative buttons for send or cancel near the text area for old hands who prefer not to scroll down; they have the same effect as explained above in the first two bullets.

The Moderator on clicking the "Send Rejection" button causes the rejection to go out to the annotator. At the same time the relevant annotation is rendered invisible to those viewing the annotations even though it is retained on the annotations database.

At the same time the system will return the Moderator to the View Annotations page where the entry in column 1 will have altered from 'new' to 'rjctd' to indicate the change in its state and its removal from public viewing. The Moderator has the option to purge the rejected annotation if desired.

9.auto-reject second annotation on list barred by Automoderator

As the Automoderator has barred the annotation as representing a threat against its evaluation settings, the Moderator closely inspects the annotation by clicking 'new' against the second annotation in the summary table. The detailed view is displayed and the Moderator realises the annotation is completely unacceptable and does not even merit a response. The Moderator opts to choose the auto-rejection option. In order to carry out that auto-rejection process, the Moderator clicks the 'Auto-reject' button.

The Auto-reject Annotation Page

The page presents a repeated form of the detailed view to the Moderator of the annotation intended for auto-rejection whilst still showing the original message and associated information. No text area is required as no reason will be given for the annotation's auto-rejection. The Moderator can then opt to:

auto-reject the annotation without sending any message or information to the sender of the annotation
cancel the operation and return to the View annotations page
exit the entire service

Note there are also two alternative buttons for send or cancel near the text area for old hands who prefer not to scroll down; they have the same effect as explained above in the first two bullets.

The Moderator on clicking the "Auto-reject" button implements the auto-rejection. At the same time the relevant annotation is rendered invisible to those viewing the annotations but the annotation is retained on the annotations database.

At the same time the system will return the Moderator to the View Annotations page where the annotation in the summary table will have altered from 'new' to 'arjctd' to indicate the change in its state and its removal from public viewing. The Moderator has the option to purge the rejected annotation if desired.

10.purge auto-rejected (second) annotation on list barred by Automoderator

The Moderator identifies an annotation noted as 'arjctd' and clicks the link. The detailed view is presented and the Moderator selects the 'Purge' button.

The View Annotations page is re-displayed. The purged annotaion no longer appears in the summary table. The purged annotation is deleted from the annotations database.

11.attempt to purge a new unprocessed annotation on list

The Moderator attempts to purge an annotation noted as 'new' and clicks the link. The detailed view is presented and the Moderator selects the 'Purge' button.

The Moderator receives a warning message indicating that it is impossible to purge an annotation that has not been actioned.

The Moderator exits by clicking the 'OK' button and the View Annotations page is re-displayed.

12.select first annotation for action, then change mind and exit moderation service

The Moderator selects the first annotation in the summary table for action by clicking the link in column 1. The system displays the detailed view with the action buttons below the detailed view. The Moderator changes his/her mind and prefers to exit the entire moderation service by clicking 'Exit Moderation Service'.

The Exiting Annotation Moderation Service Page

The system displays a message detailing the number of annotations still marked as 'new', i.e. still awaiting Moderator action. The page displays two options for the Moderator:

'Exit Service' button - the Moderator exits the entire service
'Return to View Annotations' button - the system redisplays the View Annotations page

13.select first annotation for action, then change mind and cancel operation

The Moderator selects the first annotation in the summary table for action by clicking the link in column 1. The system displays the detailed view with the action buttons below the detailed view. The Moderator changes his/her mind and prefers to cancel the intended operation by clicking 'Cancel'. The system re-displays the summary table with the unchanged annotation.