Differences

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

--- calculations [2017/01/10 14:45]
127.0.0.1 external edit
+++ calculations [2017/01/10 15:21] (current)
steveclarke [Scaled Scoring]
@@ Line 1: / Line 1: @@
-====== Glossary of Terms ======
+====== Calculations ======
-FIXME concept of versioning version fields, version navigation, object life cycles
+==== Scaled Scoring ====
+Item Writing tracks two types of Candidate scores: raw scores and scaled scores. A raw score is a score without any sort of adjustment or transformation, such as the simple number of Items answered correctly. A scaled score is the results of some transformation applied to the raw score.  The purpose of scaled scores is to report scores for all Candidates on a consistent scale.
-FIXME Status and Status rules (interaction of objects, status life cycle)
+Th scaled score is calculated using two different formulas based on the raw score.  One formula is used if the Candidate is at or above the raw cut score.  The other formula is used if the Candidate raw score is blow the raw cut score.
-FIXME Glossary for Expiry Effective Expiry Dates and not deleting records
+** At or Above Raw Cut Score**
-FIXME Authentication modes and impact - Under support and installation
+(CandidateRaw - RawCut) * ( (ScaledMax - ScaledCut) / (RawMax - RawCut) ) + ScaledCut
-FIXME web.config discussion - Under support and installation
+** Below Raw Cut Score**
-FIXME concept Roles vs Users and how inherited rights work.
-FIXME Custom fields TDA Customization etc.
-===== Banks and Bank Level =====
-CE Supports two types of Item Banking.  Level 1 Banking where there are multiple Exam and Item Banks and a single shared Bank for Attachments, Authors, Competencies etc.  Or Level 3 Banking where there are multiple Exam and Item Banks and multiple shared Banks.
-CE has many different types of objects.  An object can be an Item, Exam, Candidate, Address Type, User, etc.  Item Banking separates these objects into smaller groups of records.  Reasons for segregating the Banks are:
-  * Different Clients/Departments - some records might be used only specific clients or departments.  To prevent their use by other departments or clients, they are kept in separate Banks.
-  * Security - To limit exposure to records, [[security_edit_banks|Bank Security]] can be setup to limit User access to certain Banks.
-  * Legacy Data - Legacy data might be migrated into CE that users will want to keep separate from production data.
-  * Import Data - Data that is imported into CE users might want to keep separate until it is vetted or fully checked.
-Users can have Bank access restricted:
-  * None - No access to the Bank.
-  * Browse - The user has read only rights to the Bank.  Meaning they can view records and maintenance pages but cannot create new records, expire records or make any changes to records.
-  * Full - The user has full rights to the Bank, meaning they can view records, create new records, expire records or update existing records.
-=== Shared Object Types ===
-Regardless of Bank Level 1 or Bank Level 3 Item Banking, certain object types are always Shared. When an object type is **Shared** it means, regardless of [[security_edit_banks|Bank Security]], Users can access and maintain records.  It also means regardless of what Bank the user has selected to work with, these object type records are avaialable to work with.  Shared object types are found on the System menu and are: [[address_type_entry|Address Type]], [[bank_entry_level_1|Bank]], [[competency_type_entry|Competency Type]],[[contact_type_entry|Contact Type]], [[country_entry|Country]], [[country_region_entry|Country Region]], [[email_type_entry|Email Type]], [[ethnicity_entry|Ethnicity]], [[gender_entry|Gender]], [[item_meta_type_entry|Item Meta Type]], [[reference_type_entry|Reference Type]], [[security_entry_role|Security Roles]] and [[security_entry_user|Security Users]].
-=== Level 1 Banks vs. Level 3 Banks ===
-The difference between Level 1 Banks and Level 3 Banks is in the data that is separated by Item Banking.  Object records are either **Shared** or they are **Banked**.  When an object type is **Shared** it means, regardless of [[security_edit_banks|Bank Security]], Users can access and maintain records.  When an object type is **Banked** it means that the data is segregated by Bank and it is affected by [[security_edit_banks|Bank Security]].
-In a Level 1 Bank most object types are shared and not controlled by Item Banking.  Only Item and Exam type records are affected by Item Banking.
-^ State ^ Object Type ^
-| Shared| [[attachment_entry|Attachment]], [[author_entry|Author]], [[candidate_entry|Candidate]], [[competency_entry|Competency]], [[copyright_entry|Copyright]] and [[reference_entry|Reference]] |
-| Banked| FIXME links to Item, Item Group, Exam and Term |
-In a Level 3 Bank most object types are Item Banked.  Even though some object types are shared across multiple Exam/Item Banks, they are not shared throughout all Banks. Each Exam/Item Bank (at level 3) has a parent bank at level 2 which is a shared bank.  This shared bank shares all of its object records amongst all of the child Banks underneath it.
-^ State ^ Object Type ^
-| Shared among child Exam/Item banks| [[attachment_entry|Attachment]], [[author_entry|Author]], [[candidate_entry|Candidate]], [[competency_entry|Competency]], [[copyright_entry|Copyright]] and [[reference_entry|Reference]] |
-| Banked| FIXME links to Item, Item Group, Exam and Term |
-In the sample below, the **Shared** bank (in red) is shared by its child banks underneath it **Import** and **Production** (in orange). The **Client 3** bank (in blue) is shared by its child banks underneath it **Production** (in green).
-{{:level3banks.png?200|}}
-=== User Bank Security ===
-User Bank Security is maintained using [[security_edit_banks|Security Edit Banks]].
-In Level 1 Banking, the security is maintained for the Banks at Level 1 in the tree.  User rights are managed by Bank only for the FIXME links to Item, Item Group, Exam and Term entry tools.  All other object type data is shared and not affected by Bank Security.
-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 FIXME links to Item, Item Group, Exam and Term entry tools.
-===== Record Locking =====
-CE supports record locking.  Record locking is the technique of preventing multiple users from editing a record at the same time.  This is to prevent inconsistent results.  An example would be User 1 opens an Item to change the Competency from "A" to "B".  User 2 opens the same Item after user 2 started editing it.  User 2 attempts to change the Angoff to 0.5.  User 1 saves their change then User 2 saves their change.  Because User 2 retrieved their data before User 1 committed their change, their screen shows the Competency as "A" instead of "B".  When User 2 saves their Item, the Competency then reverts back to "A".
-To prevent this CE locks a record the moment a user begins editing the record.  Every time the user navigates to another edit page for the record or saves their work, they refresh their lock on that record.  When the user starts to edit or view another record or navigates to another tool in the system or logs off the record lock is released.
-When a user selects a record that is locked, a warning message appears on their screen, all of the entry controls are disabled and the **Save** button in hidden.
-{{:recordlocked.png?600|}}
-Record Locks are specific to the users session not the User ID.  This means two people can log in as "Administrator" and CE will track their locks separately.
-The default duration of a record lock before automatic release is 30 minutes.  This is configurable in the web.config file.
-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.
+(ScaledCut-1) - ( ( (RawCut-1) - CandidateRaw) * ( ( (ScaledCut-1) - ScaledMin) / ( (RawCut-1)- RawMinScore) ) )
+{{:scaledscore.png?200|}}