Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
concepts [2017/03/20 11:33] steveclarke [Status and Substatus] |
concepts [2019/02/28 14:48] (current) mikecable [Selection Grids] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Concepts ====== | ====== Concepts ====== | ||
- | FIXME web.config discussion - Under support and installation | + | ==== Archive Sessions ==== |
- | + | Item Writing assigns Registrants to [[session_entry|Sessions]] of [[exam_entry|Exams]]. Over time many Sessions may be created for an Exam. Each Session will have its own roster of Registrants. Some clients require that Sessions that identify a grouping of Registrants be removed from the system for confidentiality reasons. However, it is still required to keep all of the registrant responses, so that aggregated [[stats_item|Item Statistincs]] can be created. | |
- | FIXME discuss archive sessions and impact on calculations | + | |
- | + | ||
- | FIXME discuss track changes | + | |
+ | To handle this, Item Writing has **Archive Sessions**. When an Exam is created and Archive Session is automatically created for the Exam. Over time other Sessions will be created for the Exam. When the User deletes those Sessions, all the Registrants for those Sessions along with their response records are transferred to the Archive Session. This way the Archive Session preserves all the responses, but removes the confidential grouping information. | ||
==== Authentication Modes ==== | ==== Authentication Modes ==== | ||
Line 59: | Line 57: | ||
In Level 3 Banking, the security is maintained for the Banks at Level 3 in the tree. The security shared data in the parent bank ([[attachment_entry|Attachment]], [[author_entry|Author]], [[candidate_entry|Candidate]], [[competency_entry|Competency]], [[copyright_entry|Copyright]] and [[reference_entry|Reference]]) is inherited from the Level 3 Banks. Meaning if a level 3 Bank has **Full** rights, then the shared parent bank at level 2 has **Full** rights. User rights are managed for the shared parent bank and for the [[item_entry|Item]], [[item_group_entry|Item Group]], [[exam_entry|Exam]] and [[term_entry|Term]] entry tools. | In Level 3 Banking, the security is maintained for the Banks at Level 3 in the tree. The security shared data in the parent bank ([[attachment_entry|Attachment]], [[author_entry|Author]], [[candidate_entry|Candidate]], [[competency_entry|Competency]], [[copyright_entry|Copyright]] and [[reference_entry|Reference]]) is inherited from the Level 3 Banks. Meaning if a level 3 Bank has **Full** rights, then the shared parent bank at level 2 has **Full** rights. User rights are managed for the shared parent bank and for the [[item_entry|Item]], [[item_group_entry|Item Group]], [[exam_entry|Exam]] and [[term_entry|Term]] entry tools. | ||
+ | |||
+ | Click for more on [[general_navigation_tree|Tree controls]]. | ||
Line 148: | Line 148: | ||
===== Track Changes ===== | ===== Track Changes ===== | ||
- | The Track Changes feature enables Users to keep track of the changes made when editing the content in a rich text editor FIXME link. Changes are tracked when e.g., applying text formatting to a text selection, entering new content, deleting existing content, etc. Additionally, on selecting a tracked change a little pop up with details about it will appear at the bottom right corner of the browser. | + | The Track Changes feature enables Users to keep track of the changes made when editing the content in a [[general_navigation_radedtior|rich text editor]]. Changes are tracked when e.g., applying text formatting to a text selection, entering new content, deleting existing content, etc. Additionally, on selecting a tracked change a little pop up with details about it will appear at the bottom right corner of the browser. |
Further, the tracked change(s) can be accepted or rejected, either on a change by change basis or for the entire text. | Further, the tracked change(s) can be accepted or rejected, either on a change by change basis or for the entire text. | ||
Line 154: | Line 154: | ||
The Track Changes functionality entirely relies on HTML to show, recognize and manipulate the tracked content. Upon user interaction Track Changes adds and/or modifies the HTML output with additional tags and attributes which represent the actual tracked change. | The Track Changes functionality entirely relies on HTML to show, recognize and manipulate the tracked content. Upon user interaction Track Changes adds and/or modifies the HTML output with additional tags and attributes which represent the actual tracked change. | ||
===== Versioning ===== | ===== Versioning ===== | ||
- | [[attachment_entry|Attachments]], [[item_entry|Items]] and [[exam_entry|Exams]] can be reversioned. By default, all new Attachments, Items and Exams are created as **Version** 1 with a **Version 1 ID** value pointing to their ID. Reversioning an object, creates a copy of that object in the same [[concepts#Banks and Bank Level |Bank]]. The new object has a **Version** = Version + 1 with its **Version 1 ID** still pointing to the original version 1 record. | + | [[attachment_entry|Attachments]], [[item_entry|Items]], [[item_group_entry|Item Groups]] and [[exam_entry|Exams]] can be reversioned. By default, all new Attachments, Items, Item Groups and Exams are created as **Version** 1 with a **Version 1 ID** value pointing to their ID. Reversioning an object creates a copy of that object in the same [[concepts#Banks and Bank Level |Bank]]. The new object has a **Version** = Version + 1 with its **Version 1 ID** still pointing to the original version 1 record. |
- | Example: Attachment "Eiffel Tower " ID=25, Version=1 is reversioned. The original Attachment has 25 is Version1ID=25 because it is the first version of the Attachment. The reversioned record will get the next available Attachment ID automatically generated by the system. For sake of this example, lets assume it is 201. So the new Attachment record would by ID=201, Version=2, Version1ID=25. If the version 2 record is reversioned, then lets assume the next available ID=320, so the new record would be ID=320, Version=3, Version1ID=25. | + | Example: Attachment "Eiffel Tower " ID = 25, Version = 1 is reversioned. The original Attachment has 25 is Version1ID = 25 because it is the first version of the Attachment. The reversioned record will get the next available Attachment ID automatically generated by the system. For sake of this example, assume it is 201. So the new Attachment record would by ID = 201, Version = 2, Version1ID = 25. If the version 2 record is reversioned, then assume the next available ID = 320, so the new record would be ID = 320, Version = 3, Version1ID = 25. |
^ID^Version^Version1ID^ | ^ID^Version^Version1ID^ | ||
Line 166: | Line 166: | ||
==== Selection Grids ==== | ==== Selection Grids ==== | ||
- | The Attachment, Item and Exam grids by default only show the most recent version of the records. To display prior versions of the records, click the **Include Prior Versions** check box in the title bar. | + | The Attachment, Item, Item Group and Exam grids by default only show the most recent version of the records. To display prior versions of the records, click the **Include Prior Versions** check box in the title bar. |
{{:examentryspecialfilters.png?600|}} | {{:examentryspecialfilters.png?600|}} | ||
==== Viewing Prior Versions while Editing ==== | ==== Viewing Prior Versions while Editing ==== | ||
- | When editing Attachments, Items or Exams, users can navigate to other versions of the records by using the **Select Version** drop down on the blue info bar on the edit page. If there is only one version of the records, the **Select Version** drop down is disabled. | + | When editing Attachments, Items, Item Groups or Exams, users can navigate to other versions of the records by using the **Select Version** drop down on the blue info bar on the edit page. If there is only one version of the records, the **Select Version** drop down is disabled. |
{{:examversion1.png?400|}} | {{:examversion1.png?400|}} | ||
{{:examversion2.png?400|}} | {{:examversion2.png?400|}} | ||