Differences

This shows you the differences between two versions of the page.

--- concepts [2017/03/15 13:05]
steveclarke [Concepts]
+++ concepts [2019/02/28 14:48] (current)
mikecable [Selection Grids]
@@ Line 1: / Line 1: @@
 ====== 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 concept Roles vs Users and how inherited rights work.
-FIXME discuss archive sessions and impact on calculations
+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 ====
@@ 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.
+Click for more on [[general_navigation_tree|Tree controls]].
@@ Line 101: / Line 101: @@
 There are circumstances where a user might persist their lock of a record inadvertently.  These include closing their browser, instead of logging off.  Having their computer shut down or having their network connection drop.  In order to clear their Record Locks use the [[Record_Lock|Record Lock]] tool.
+===== Security Rights and Roles =====
+=== Rights ===
+In CE, each [[security_entry_user|User]] has permissions (rights) to the various menu options and reports. When they log into CE, CE checks their permissions and hides menu options they have no access to or restricts their functionality on menu options they have //browse// permissions to.
+Users can have one of three levels of permissions:
+  * None - No access to the menu option or report.
+  * Browse - The User has read only permissions to the menu option, meaning they can view records and maintenance pages, but cannot create new records, expire records or make any changes to records.  The User can run the reports.
+  * Full - The User has full rights to the menu option, meaning they can view records, create new records, expire records or update existing records.
+The User security is set on the [[security_edit_forms|Security Forms]] page.  The permissions set for the User are known as Security Rights.
+=== Roles ===
+**Roles** can also be setup within CE.  A [[security_entry_role|Role]] is a set of permissions.  Users can then be added as [[security_edit_roles|Members]] of the Role.  When a User is a Member of the Role, they inherit all the permissions of that role.
+For example a Role of "Lookup Administrator" could be setup that grants permissions to the Author, Competency, Copyright and Reference entry tools, but not the Exam or Item entry tools.  Any User who is a Member of the "Lookup Administrator Role" will inherit the permissions to the Author, Competency, Copyright and Reference entry tools.
+Security permissions are supersetted between the User permissions and the Role permissions conveyed by membership.  As an example, there is an "Item Admin" role that has permissions to Item Entry, and "Exam Admin" role that has permissions to Exam Entry.  A User who has permissions to Candidate Entry is made a member of both the "Item Admin" and "Exam Admin" Roles.  The means the User now has permissions to Item Entry (from Role), Exam Entry (from Role) and Candidate Entry (form their Rights).
+Security always takes the highest permission.  If a User has **Full** permissions granted from a Role and **Browse** permissions granted the User receives **Full** permission since it is higher.
 ===== Status and Substatus =====
@@ Line 127: / Line 147: @@
 The Substatus values are dependant on the Status values.  Each Status value has a different Substatus list associated with it.  Substatuses have no impost on system business logic.  Substatus lists are customized by TDA.  Contact [[start|TDA]] for customized Substatus values.
+===== Track Changes =====
+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.
+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 =====
-[[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^
@@ Line 140: / Line 166: @@
 ==== 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|}}
 ==== 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|}}
 {{:examversion2.png?400|}}