Difference between revisions of "Academic Effect"
(→Document) |
(→Authentication and Security) |
||
Line 96: | Line 96: | ||
; Super User : This is typically Academic Effect support personnel. Legacy Rights - Can flit from account/subdomain to account/subdomain and see all. The only thing they cannot see fully are documents. (Future Rights - A basic user of a support/test organization, full administration site access with edit access to all site content, plus access to the Impersonation Tool which lets a user authenticate as other users temporarily to duplicate support issues.) | ; Super User : This is typically Academic Effect support personnel. Legacy Rights - Can flit from account/subdomain to account/subdomain and see all. The only thing they cannot see fully are documents. (Future Rights - A basic user of a support/test organization, full administration site access with edit access to all site content, plus access to the Impersonation Tool which lets a user authenticate as other users temporarily to duplicate support issues.) | ||
+ | |||
+ | ==User Data Structure== | ||
+ | ; Users : A user is a Contensive people record. | ||
+ | <blockquote> | ||
+ | * A user's organization is determined by the organization selected in their people record. | ||
+ | * A user's applications are set in the user's organization. | ||
+ | </blockquote> | ||
+ | ; Organization (Institution) : is a Contensive Organization, found under Manage Users > Organizations. | ||
+ | <blockquote> | ||
+ | * An organizations applications are set in the organization's workspaces tab. | ||
+ | </blockquote> | ||
+ | ; User Documents ; (tbd) | ||
+ | ; Institutional Documents ; (tbd) | ||
==Authentication and Security== | ==Authentication and Security== |
Revision as of 15:07, 17 July 2015
Contents
- 1 Terms
- 2 Roles
- 3 User Data Structure
- 4 Authentication and Security
- 5 Applications
- 6 Affirm
- 7 Align
- 8 Dashboard
- 9 Document
- 10 Effect
- 11 Execute
- 12 Reflect
- 13 Report
- 14 Structure (settings)
- 14.1 My Profile
- 14.2 Account Information
- 14.3 Application Settings
- 14.4 Manage Users
- 14.5 Messaging
- 14.6 Password Policies
- 14.7 Reporting Periods
- 14.8 Templates
- 14.9 Reflective Prompts
- 14.10 Courses
- 14.11 General Education
- 14.12 Institutional Priorities
- 14.13 Improvements Achieved
- 14.14 Organization Settings
- 14.15 Sources of Evidence
- 14.16 Standards
- 14.17 Strategic Initiatives
- 14.18 Think
- 14.19 Verify
- 15 Administration Tasks
- 16 Data Structure
- 16.1 Academic Ranks
- 16.2 Accreditation Chapter Shelf
- 16.3 Accreditation Chapters
- 16.4 Accreditation Shelf
- 16.5 Accreditations
- 16.6 Additional Websites
- 16.7 Analysis Questions
- 16.8 Annual Special Report
- 16.9 Application Alerts
- 16.10 Argument Statuses
- 16.11 Assessment Approval Statuses
- 16.12 Assessment Comments
- 16.13 Assessment Document Rules
- 16.14 Assessment Goal Comments
- 16.15 Assessment Goals
- 16.16 Assessment Objective Comments
- 16.17 Assessment Objective General Education Rules
- 16.18 Assessment Objective Institutional Priority Rules
- 16.19 Assessment Objective Meta Data
- 16.20 Assessment Objective Meta Data Achievement Statuses
- 16.21 Assessment Objective Meta Data Approval Statuses
- 16.22 Assessment Objective Standard Rules
- 16.23 Assessment Objective Strategic Plan Rules
- 16.24 Assessment Objectives
- 16.25 Assessments
- 16.26 Authentication Methods
- 16.27 Campuses
- 16.28 Career Information
- 16.29 CIP Codes
- 16.30 Cited Document Index
- 16.31 Common Passwords
- 16.32 Compliance Levels
- 16.33 Contract Lengths
- 16.34 Countries
- 16.35 Course Rules
- 16.36 Courses
- 16.37 Credential Headers
- 16.38 Degree Institutions
- 16.39 Degree Rules
- 16.40 Degree Types
- 16.41 Degrees
- 16.42 Departments
- 16.43 Divisions
- 16.44 Document Access Rules
- 16.45 Document Bookmarks
- 16.46 Document Citation Coauthors
- 16.47 Document Citation Editors
- 16.48 Document Entity Rules
- 16.49 Document Folder Access Rules
- 16.50 Document Folder Rules
- 16.51 Document Folders
- 16.52 Document Makes
- 16.53 Document Source Material Types
- 16.54 Document Sources
- 16.55 Document Statuses
- 16.56 Document Types
- 16.57 Documentation Types
- 16.58 Documents
- 16.59 Domains
- 16.60 Employee Types
- 16.61 Employment Statuses
- 16.62 Entities
- 16.63 Ethnicities
- 16.64 Faculty
- 16.65 Faculty Course Rules
- 16.66 Faculty Statuses
- 16.67 Facutly Degrees
- 16.68 Folder Permissions
- 16.69 Genders
- 16.70 General Education Elements
- 16.71 Institutional Priorities
- 16.72 Institutional Roles
- 16.73 Intervals
- 16.74 Measure Source Evidence
- 16.75 Measure Source Evidence Rules
- 16.76 Measure Source Evidence Types
- 16.77 Members
- 16.78 Narrative Statuses
- 16.79 Objective General Education Element Rules
- 16.80 Objective Institutional Priority Rules
- 16.81 Objective Standard Rules
- 16.82 Objective Strategic Plan Rules
- 16.83 Organization Campuses
- 16.84 Organization Document Source Material Types
- 16.85 Organization Document Sources
- 16.86 Organization Document Statuses
- 16.87 Organization Institutional Roles
- 16.88 Organization Research Types
- 16.89 Organizations
- 16.90 Password Policies
- 16.91 People
- 16.92 Permissions
- 16.93 Prefixes
- 16.94 Projects
- 16.95 Research Types
- 16.96 Role Rules
- 16.97 Roles
- 16.98 Salaries
- 16.99 Standard Shelf
- 16.100 Standards
- 16.101 Standards Comments
- 16.102 Standards Contributors
- 16.103 Standards Document Rules
- 16.104 States
- 16.105 Strategic Plans
- 16.106 Suffixes
- 16.107 System Status
- 16.108 Tenure Statuses
- 16.109 Titles
- 16.110 Units
- 16.111 User Tasks
- 16.112 Users Guide
- 16.113 Workspace Organization Rules
- 16.114 Workspaces
- 17 Public API (future)
Terms
- Applications
- A group of features gathered into a single installable unit. Formally called Workspaces.
- Projects
- A project is an group of tasks created in an application by and for a single user. It can be shared with other users.
- Roles
- A group of rights that can be assigned to a user as a unit. For example the Administrator role might have rights to all editing features.
- Rights
- An individual privilege assigned to roles. For example, the Administrator role might have the right to edit users.
- Project Owner
- A right granted to the user who creates a project. The Project Owner can view and edit the project.
- Project Author
- A right granted to a user that allows them to view and edit the project.
- Project Reviewer
- A right granted to a user that allows them to view a project.
- Affirm
- Breaks the standards out into projects and complete data entry for each standard, in preparation for the accrediting body to review.
- Align
- (define this application)
- Document
- (define this application)
- Effect
- Used to implement effective evaluation theory. Often. Academic and Performance assessment.
- Intent
- Group can get together to formulate a strategic plan. Create a high level strategic plan.
- Reflect
- Post Mortem analysis. Analyze past performance.
- Verify
- Enter facility and show they are qualified to teach
- Structure
- The settings for individuals and organizations.
- Effect Report
- Goals
- (define)
- Objectives
- (define)
- Supported Initiaives
- (define)
- Standards (Supported Initiative)
- (define)
- General Education (Supported Initiative)
- (define)
- Institutional Priorities (Supported Initiative)
- (define)
- Strategic Initiatives (Supported Initiative)
- (define)
- Measures
- (define)
- Standards
- Collections
- a way to group standards
- Official Standards
- a standard added and maintained within the system
- Public Standards
- A local standard that was published for everyone.
- Local Standards
- A standard added by an organizaiton.
Roles
- User
- An individual who has authentication access to the Academic Effect application framework.
- Basic User
- This is typically a customer with access to applications associated to the user's Institution. Access to Structure Profile and Structure Templates.
- Verify Manager
- This is typically a basic user granted special privileges in the Verify Application in Structure and Verify to mark the Verified checkbox (more detail).
- Verify Facilitator
- This is typically a basic user granted special privileges in the Verify Application to add data for degrees, but cannot verify it.
- PC Admin
- (Consider renaming Account Admin) This is typically the customer's administrator. They are a basic user with the following additional rights
- Review rights for all projects within the same organization
- Can view and modify account information in Structure
- Can generate an API access Key in Structure
- Access to the CIP code list in Structure
- Access to the Standard list in Structure
- Can modify profile fields of users within the organization, including fields to
- Change PC Admin rights
- Change Verify Manager rights
- Access and Modification of the Annual Special Report List in Structure
- Access to the Institutional Priorities List in Structure
- Access to the Strategic Plan List in Structure
- Access to the Degree List is Structure
- Update Analysis Questions
- Can do everything in all of the apps (except duplicate projects they do not own). Can add users and give all roles. Full access in structure, etc.
- Super User
- This is typically Academic Effect support personnel. Legacy Rights - Can flit from account/subdomain to account/subdomain and see all. The only thing they cannot see fully are documents. (Future Rights - A basic user of a support/test organization, full administration site access with edit access to all site content, plus access to the Impersonation Tool which lets a user authenticate as other users temporarily to duplicate support issues.)
User Data Structure
- Users
- A user is a Contensive people record.
- A user's organization is determined by the organization selected in their people record.
- A user's applications are set in the user's organization.
- Organization (Institution)
- is a Contensive Organization, found under Manage Users > Organizations.
- An organizations applications are set in the organization's workspaces tab.
- User Documents ; (tbd)
- Institutional Documents ; (tbd)
Authentication and Security
There are three methods of authentication: Native, LDAP (future), and CAS (future)
- Native Authentication
- Requires a unique username and a password. To modify Native Authentication for a user, edit their people record and change the values of username and password. Note that username must be unique
- LDAP
- (future)
- CAS
- (future)
Applications
An application in Academic Effect is a group of common features installed as a unit to an organization. An installed application is run when a user in that organization clicks button in the header with the applications name. Applications are installed by editing the organization and checked the appropriate checkbox in the Workspaces tab. (formally called Workspaces)
Affirm
Align
Dashboard
The dashboard is a default application that lists all the user's projects, and all the applications installed for the user's account.
Document
Files, Folders and Collections
Permissions
- Owner
- (tbd)
- Author
- (tbd)
- Reviewer
- (tbd)
Collections
- Institutional
- (tbd)
- My Collection
- (tbd)
- Shared with Me
- (tbd)
Document Sharing
- Sharing Collections, Folders and Files
- (tbd)
- Receiving Shared Collections, Folders and Files
- (tbd)
Effect
Execute
Reflect
Report
Structure (settings)
My Profile
Account Information
Application Settings
Manage Users
Messaging
Password Policies
Reporting Periods
Templates
Reflective Prompts
Courses
General Education
Institutional Priorities
Improvements Achieved
Organization Settings
Sources of Evidence
Standards
Strategic Initiatives
Think
Verify
Administration Tasks
- Create a new account
- (tbd)
- Create a new user
- (tbd)
Data Structure
Academic Ranks
Simple name/id list of academic rank selections
Accreditation Chapter Shelf
Reserved for future use.
Accreditation Chapters
Reserved for future use.
Accreditation Shelf
A simple name/id list, uses as an attribute of Accreditations.