Suggestions:
Posted November 13th, 2005 by Admin
in
Please add comments to this section to communicate your suggestions for watch.Jefferson-County.
Please add comments to this section to communicate your suggestions for watch.Jefferson-County.
Comments
add pull down/auto fill (like state) choice for JC cities
add pull down/auto fill (like state) choice for JC cities
add pull down/auto fill (like state) choice for JC zip codes
add pull down/auto fill (like state) choice for JC zip codes
center reporting map on jefferson county center point
center reporting map on jefferson county center point
Provide the coordinates.
Provide the coordinates. The map centers on your current location based on your IP address.
add example: suite, floor, room, apt to address additional
add example: suite, floor, room, apt to address additional
develop a bug report closed forum info to you. info from you, no
develop a bug report closed forum info to you. info from you, no discussions
develop an enhancement closed forum info to you, info from you,
develop an enhancement closed forum info to you, info from you, no discussion
allow delete of any content by the original author
allow delete of any content by the original author
E: Report Status
I might suggest that a status field be incorporated into the reporting, bug, questions, and enhancement applications. This field is updated by the "? reporting managers".
By using the information to populate a (KB) knowledge base system or (DSS) Decision support system in addition to record archive we can provide a richer user experience and faster visual indexing.
Examples...
Activity reporting:
Status: open, responding, closed
Post report... investigate report... update report... resolve report
Question posting...
Status: open, responding, closed
Ask a question... get an official answer... post question and answer to KB for search and view
Bug reporting...
Status: open, responding, closed
Report a bug... see bug status... experience bug fix
Enhancement reporting...
Status: open, responding, closed
Request an enhancement... see enhancement status... experience enhancement
E: Member Access Rules
I feel that as a group, we need to develop our service level agreement, IE: who can.. who can't, who will.. who won't.. etc.
If we are to follow a set of rules, I vote:
Open Access:
-Anyone can post a suspicious activity report.
-Anyone can view open discussion forums
-Anyone can view knowledge base (IE: tips, tricks, how to, what to do etc.)
Log-in Access:
multi level to control multiple things reporting, closed forums, community forums, view, edit, respond, open, close, move, reporting, DSS... etc. (we need to define and build)
member decision criteria (one or more of the following)
1- you must be a member of an official registered nWatch team and have passed nWatch training
2- you must be a member of an official registered CERT team and have passed CERT training
3- you must be a member of an official registered COPS team and have passed COPS training
4- you must be a member of SSP
5- you must be a member of a JC law enforcement group
6- you must be a member of JC emergency services or office of homeland security.
Access
Open Access:
-Anyone can post a suspicious activity report.
-Anyone can view open discussion forums
-Anyone can view knowledge base (IE: tips, tricks, how to, what to do etc.)
Log-in Access:
multi level to control multiple things reporting, closed forums, community forums, view, edit, respond, open, close, move, reporting, DSS... etc. (we need to define and build)
This is how it is currently set up, with the exception that anonymous users cannot view specific reports. This would allow the 'bad guys' to find out if their activity has been reported raising the specter of creating a 'game' for them.