Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Space Index

0-9 ... 7 A ... 3 B ... 0 C ... 7 D ... 2 E ... 2
F ... 3 G ... 20 H ... 1 I ... 3 J ... 2 K ... 0
L ... 0 M ... 3 N ... 0 O ... 2 P ... 10 Q ... 2
R ... 4 S ... 9 T ... 5 U ... 3 V ... 0 W ... 2
X ... 0 Y ... 0 Z ... 0 !@#$ ... 0    

0-9

Page: 2.0 Release
2.0 Functional Requirements and Spec https://source.sakaiproject.org/svn/gradebook/tags/pre-2.2-reorganization/xdocs/specs/GB2reqSpec.html
Page: 2.1 Release
Page: 2.1.0 Release Notes
2.1.0 Release Notes Changes in Sakai 2.1 ==================== New features ------------ Group awareness - If sections or user teams have been defined for a site, the group names will be displayed in a filtering menu on the Assignment Detail, Course Grade,
Page: 2.2 Release
A significant amount of work done on the Gradebook for Sakai 2.2 release was under-the-hood: 1) Repackage Gradebook service component http://bugs.sakaiproject.org/jira/browse/SAK-4331 2) Restructure Gradebook directories and package names http://bugs.sak
Page: 2.3 Release
Development for the 2.3 version of the Gradebook was focused on adding four major areas of functionality: 1) upload and import of data; 2) selective control over the release of posted scores and grades by date, by time, by individual assignment, etc.; 3)
Page: 2.4 Release
The 2.4 release of the gradebook is driven by two major goals: Integration with the new Sakai Course Management API Add significant new end user functionality to a core Sakai application Note: these goals for 2.4 do not include meeting a major community r
Page: 2.5 Release
Projected scope of Sakai gradebook 2.5 release work: Major changes include: Allow categories and/or weighted categories. Item weighting deferred past summer. Allow new grade entry types: percentages and letter grades Ability to import grades using a down

A

Page: Application Menu
The Application Menu appears at the top of each page. It is a bar-separated list of links to application pages. If the current page is on that list, the corresponding link is disabled (that is, rendered as plain text). The Sakai Style Guide 1.4 describes
Page: Assignment Not Counted
We're adding a feature that will allow instructors to indicate which asignments should be counted toward the final grade.
Page: Automated Grade Exports
DRAFT Automated Grade Exports Gradebook2 internally uses a REST call to trigger final grade submissions. Since the client is somewhat tightly coupled to the server session that produces it, some assumptions are made downstream of the REST point about the

B

C

Page: Closed Fixes
Page: Comments Feature
Page: Comments Feature Wireframes
Page: Configurable Spreadsheet Download
The basic requirement is to provide a means to configure which data are output and the column order for each of of the Gradebook spreadhseet downloads (Roster, Course Grade views). These configurations can only be set on a per installation basis via a pro
Page: Context Switching
In a standalone web app, after making sure the user was authenticated, we'd show a list of accessible gradebooks to choose from. However, embedded in a framework, that choice will have already been made: the user won't see a "Gradebook" link unless they'r
Page: CSS Issues
The Sakai Style Guide is meant to provide an integrated look-and-feel between Sakai applications. Part of that is defining CSS class names and usages. A list (with sample definitions) can be found in the "hiFiWireframes" produced for each version of the S
Page: Current Functional Requirements and Spec
New 2.3 features have not yet been added to the comprehensive functional specification. This will be done shortly. The 2.2 gradebook release largely included improvements that did not have a direct impact on end user functionality, hence the 2.1 release d

D

Page: Design Guidelines
Taking some cues from MyFaces (particularly the popularity of the x:saveState tag) and from a few books and articles published since the Pilot, we developed an experimental set of guidelines for JSF design, along with a new component to support them. Here
Page: Differences between Sakai Gradebook Tools (GB1/GB2/GBNG)
GAP analysis between Gradebook2 and Gradebook (UNIVERSIDAD DE MURCIA) Quick Check List (Thanks Unlicensed user). Please, feel free to add new rows if needed. Status in GBNG GB1 [11.x] GB2 [1.9.1] GB NG Related JIRA Comments/Questions Institutional Suppor

E

Page: Embedded HTML structure
The display context of the web application effects what HTML it should emit. For example, when running standalone a "logout" link is appropriate; when running within a framework, a "logout" link usually isn't. When running standalone with complete control
Page: Export and import between sites
Add gradebook to Sakai site export/archive. All student information will be removed All scores will be removed Only internal gradebook assignments (those with all data stored in gradebook tables) will be included in the export. Assignment due dates will b

F

Page: Facades
Page: FlowState Tag
As part of this approach, we've implemented an invisible JSF component to glue the JSP page and the backing bean together. It's called "gbx:flowState". This is from the JavaDoc: This JSF UI component lets backing beans track the request life cycle and sav
Page: Functional Requirements

G

Page: GAP analysis between Gradebook2 and Gradebook
Main differences between Gradebook2 and Gradebook This document has been elaborated by members of the University of Murcia (Special kudos to Unlicensed user) and it includes the main differences that have been found between the latest versión of Gradebook
Page: GB2 Building Tips for Windows
These are some notes and hints to get Gradebook 2 to build on Windows. Eventually these may be incorporated and improved in gradebook 2. There were 2 major problems for building gradebook 2 on Windows, the patching needed (for 2.6) and the the deployGWT.s
Page: Grade Import
We were wary of trying to figure out how to import grades from a spreadsheet in the initial specification. But in the Baltimore SEPP Conference, there seemed to be a lot of interest in the feature. Josh: "The reason I think we should discuss reprioritizin
Page: Gradebook 2.1 Functional Requirements and Notes
------------------------------------------------------------ The following features were prioritized for the 2.1 gradebook. Promised features: *Section awareness *Grade Log Prioritized features to be incorporated if time allows. The rankings may be subjec
Page: Gradebook API Changes
New proposed changes to the API (8/20/2008) Our new strategy is to inject a new Spring bean into Sakai that overrides the default GradebookManagerHibernateImpl calculations and incorporates our new logic (for drop lowest/highest, for extra credit, for wei
Page: Gradebook Coordination - Denver 2010
Summary of current situation We have worked our way into a situation where we have stronger gradebook options, but the gradebook is forked, and this is not desirable or maintainable. The goal is a coordinated plan which draws things back into a state of s
Page: Gradebook Creation and Access
When embedded in an LMS/CMS framework, we need to let the framework decide when a gradebook should be created, and we need to let the framework decide which gradebook to show. As a result, the GradebookService interface has a "createGradebook" method, and
Page: Gradebook Development Update 3-28-2007
The next Gradebook Update teleconference will be held Wednesday March 28, 2007 at 11:00 a.m. PST. Same Teleconference details as for http://bugs.sakaiproject.org/confluence/display/SG2X/Gradebook+Requirements+Planning+3-9-2007 http://bugs.sakaiproject.org
Page: Gradebook Meeting June 1, 2007
The next Gradebook Update teleconference will be held Friday June 1, 2007 at 1:00 p.m. PST (4:00 EDT). Teleconference details to be listed below. Agenda: Review code status for IU June release Review commitments for work remaining for 2.5 Release Review Q
Page: Gradebook Project Meeting 5-19-2007
The next Gradebook Update teleconference will be held Friday May 18, 2007 at 10:00 a.m. PST. Teleconference details listed below. Agenda: Review commitments for work remaining for 2.5 Release Review QA Progress on current code release Review status of a f
Page: Gradebook Project Meeting April 26, 2007
2.5 Development Discussion via VTC Notes and audio recording can be found under attachments on 2.5 Release page: http://confluence.sakaiproject.org/confluence/x/EpU http://confluence.sakaiproject.org/confluence/x/EpU Notes: http://confluence.sakaiproject.
Page: Gradebook Requirements Planning 3-9-2007
Preliminary Agenda The primary focus of the meeting is to discuss the requirements to be implemented by Indiana over the next several months, hence: defining the general Scope of this work and confirming/choreographing available resources which can be ap
Page: Gradebook Review 08-03-2007
Gradebook status August 3, 2007 Present: Lance Speelmon, Brian Donnelly, Kirk Alexander Since there were no other participants, Lance just gave Kirk and Brian an update on the Indiana work this summer and their plans for their own release August 16, 2007.
Page: Gradebook Summit Meeting 2-23-07
You are invited to attend a Gradebook Summit Meeting on Feb. 23, 2007 from 9am to 5:30pm at the University of California's Berkeley campus. Please email Mara Hancock (mara@media.berkeley.edu) if you will be driving to the campus since you will need a park
Page: Gradebook2
Scope This page lays out some basic information about the Sakai Gradebook2 tool, including #instructions for installation, the original #motivation, some #specifics of the new tool, links to additional #resources, and a high-level #roadmap of development.
Page: Gradebook2 Calculations - An Explanation
Calculations Scope The goal of this document is to provide a high level explanation of how the Gradebook2 Calculations are implemented, for institutions that may be evaluating the tool and/or to aid in QA efforts and explanations to faculty. More technica
Page: Gradebook2 Developer Best Practices
This is a quick reference document for developer best practices when working on the Gradebook2 project. 1. Versioning We made a decision fairly early on in the development of Gradebook2 that it should be versioned independently of Sakai releases. The basi
Page: Gradebook2 UCDavis Specific Implementation Details
Final Grade Submission Using Export Advisor (GRBK-37) Configure gradebook2's applicationContext.xml to select the UC Davis specific ExportAdvisor By default, it points to the "org.sakaiproject.gradebook.gwt.sakai.api.ExportAdvisor" bean which implements t
Page: Gradebook2 Usage Statistics
Chris Schauer shared the following queries that can help to understand Gradebook2 usage at your institution: https://gist.github.com/anonymous/e628571e0f712490346e https://gist.github.com/anonymous/e628571e0f712490346e You could share the results of those
Page: Grader Comments
Instructors/Site Owners: Users with the gradebook.gradeall and/or gradebook.gradesection permission(s) will have the ability to add and change comments Users will have the opportunity to comment on a per student, per assignment basis. Comments will be ent

H

Home page: Home
Gradebook Contacts Gradebook: Unlicensed user & Unlicensed user / Gradebook2: Unlicensed user Description PC-Description Plans & Status PC-Plans Gradebook2 The majority of the information in this space focuses on the current Gradebook tool and service of

I

Page: Index
{index}{index}
Page: Institutions Using Gradebook2
Name Gradebook2 Version Sakai Version Comment University of California, Davis 1.8.1 rSmart CLE 2.8.7 Production Virginia Tech 1.7.0 with some local changes Sakai 2.8.1 Production University of Michigan 1.5.1 Sakai 2.7.1 Pilot (Stealthed) in production Rut
Page: Integrated paging and sorting
MyFaces and Oracle ADF both provide paging and sorting via all-in-one JSF components. When you want to make a list's display table paged and sortable, no Java code has to be written. You just use the new JSP tags, and their component code handles all the

J

Page: JSF Component Development
Oliver has decided priorizitation of these components. The message handling approach is needed first. Paging controls (for a statically sorted table) are next. Classes with thousands of students will be completely unmanageable otherwise. Although the func
Page: JSF Design Notes
Pilot Issues Design Guidelines FlowState Tag Results

K

L

M

Page: Meeting Agendas and Notes
Page: Messaging
After a request is processed, typically some sort of message needs to be presented to the user. Validation messages will typically be positioned close by any form elements they're associated with. More generic notifications will appear at a predictable po
Page: Moving from Gradebook Classic/Gradebook 2 to GradebookNG
This is an open forum to discuss the implications of a move from Gradebook2 to GradebookNG (result of the Gradebook Enhacements Project). If your institution is currently using Gradebook2, we encourage you to join the discussion and share your thoughts an

N

O

Page: Open Bugs and Feature Requests
Page: Open or Reopened Fixes
Open, In Progress or Reopened JIRA Tickets

P

Page: Paging and Sorting Components
The graphic layout of paging and sorting controls is governed by the Style Guide, and therefore should be deployed as generically as possible by Sakai applications (including the gradebook). However, the gradebook's response to those controls needs to tak
Page: Paging Approach
Page: Paging Tag Proposal
JSP <sakaix:dataPager firstRow="{#bBean.firstRow}" maxDisplayedRows="#{bBean.maxDisplayedRows}" dataRows="#{bBean.dataRows}"> Java // Called during action event handling for a navigation control. public void setFirstRow(int firstRow) { this.firstRow = fir
Page: PC-Description
Allows instructors to list assignments and scores, and calculate, store, and distribute grade information to students.
Page: PC-Plans
16-Feb-2009: Worked on incorporating non-calculating items and gradebook types (SAK-14551 http://bugs.sakaiproject.org/jira/browse/SAK-14551), allowing entry of institution specific grades in course grade override field (SAK-13934 http://bugs.sakaiproject
Page: Pilot Issues
JSF is an immature technology. As such, JSF developers need to deal with lack of best practices, realistic sample code, or clear workarounds to common problems. Last year's Berkeley Pilot Gradebook project wrestled with a number of design and usability is
Page: Post 2.4 Roadmap
Planning and design for the 2.5 development cycle will begin on 2/15. The major deliverable for 2.5 is weighted grade entry categories. See related issues Plus additional feedback captured as part of the Requirements process. Some requirements are conting
Page: Post 2.5 Functionality
Require Instructor to Input Values for Course Grade Scale
Page: Post2.4 QA
Tendered Resources for Iteration 1 (End date: June 1) Institution Resources Area Time available Indiana Megan May any and all 10-15 hrs/week until Sakai 2.4 releases Indiana Kristol Hancock focus on UI 2 hrs/ week Berkeley Daphne Oogle 1-2 hrs/ week Geo
Page: Presentation
There's more to presentation layer integration than just taking advantage of shared JSF components. This area covers those topics.

Q

Page: QA
Permissons Breakdown of Major functionality Gradebook Setup GB item Creation Entering grades & comments Categories & Weighting Drop Highest / Drop Lowest / Keep Highest (CLE >= 2.9.0) Grader Permissions (requires TA role) Grade calculation Export and impo
Page: QA2 tag Results - Georgia Tech
Users Conducted with Georgia Tech faculty over the course of three days, Feb. 3-5, 2009. Demographics User Number Gender Age Department Tech-savvy Uses local Sakai instance? Uses Sakai gradebook? User 1 (J) Male 31-40 Management Low No No User 2 (MC) Male

R

Page: Removed and Newly Suggested Features
The following were included in the original MIT / UC Berkeley requirements for an online Gradebook but stripped from the Sakai 2.0 release. Section Awareness Grading History Logs Grader Comments Student Details Page Assignment Not Counted Assignment Categ
Page: Require Instructor to Input Values for Course Grade Scale
Introduction Below is a description, written by our staff that provide consulting services for faculty, of the issues with providing default values for the course grade scale. We will use this space to work out the requirements for this functionality as w
Page: Resolved Fixes
Resolved JIRA tickets
Page: Results
The results so far seem encouraging. It's been simpler for us to track and solve problems. We've hit fewer JSF surprises. The code may not be as concise as it would be if we directly referenced domain objects, but at least it's very clear what the code is

S

Page: Sakai Integration
Page: SAMigo Integration
Page: Search-dropdown-nav Roster Interactions
Dropdown, search box, find and clear button interactions The introduction of the dropdown list raises the issue of how it interacts with the other roster data inputs and controls. dropdownsearch.gif Ray has implemented the dropdown with the following rule
Page: Section Filter Dropdown
The section filter dropdown specs need to deal with at least one tricky problem. Within the Section Info tool, when you create one or more sections, you must assign the sections a category. That category name, e.g., discussion, plus a number is the defaul
Page: Sorting Approach
Page: Sorting Tag Proposal
JSP <sakaix:dataTable var="row" value="#{bBean.dataList}" sortColumn="#{bBean.sortColumn}" sortAscending="#{bBean.sortAscending}"> <h:column> <f:facet name="header"> <sakaix:commandSortHeader columnName="dueDate" immediate="true"> <h:outputText value="Due
Page: Specifications
Pre-2.5 GB Technical Design Current Functional Requirements and Spec 2.5 2.5 Release
Page: Suggestions for Future Features
Page: Summit Meeting Notes Feb. 23, 2007
Mark Norton (note-taker) Introductions Oliver covered gradebook history Olvier summarized work being done for 2.4 Lance summarized categories, weighting, new grade scales, etc. Linda: we are interested in IMS interoperability. Linda: is there a standard a

T

Page: Task List and Schedule
Page: Tasks and Schedule through Dec 06
Assignee Deliverable Completed By Louis Database design (no comment history) Friday, 10/20 Josh, Louis Review design Monday, 10/23 Louis Add simple comments textarea to 'Assignment Details' and 'Course Grade' pages Wednesday, 10/25 Ray or Josh/Louis Revie
Page: Tasks and Schedule through March 07
Page: Technical Design
A Compendium of Technical Issues from the development leading up through version 2.1. Sakai Integration SAMigo Integration Presentation --CSS Issues --URL Filtering_AuthN --Context Switching Facades JSF Component Development Messaging Paging and Sorting C
Page: Teleconference and Phone Information
Here are the details for connecting to the video/phone bridge tomorrow. Use bridge #107. See you tomorrow. L FROM A TELEPHONE*:*To connect to a videoconference by telephone, you must call the Auto Attendant and enter the conference code and PIN (if req

U

Page: UMich suggested enhancements
Our largest college has a custom built gradebook that has reached end of life. They would like to use GB2 as a replacement but need certain features added to accommodate functions that had been provided by the legacy system. The list below is an overview
Page: URL Filtering_AuthN
Requirements For every defined gradebook application page, three conditions implicitly need to hold: Is there an authenticated user? Has a gradebook been selected? Does this user play an authorized role in this gradebook? When any of these conditions don'
Page: User Testing
Status Summary Summary to be added after testing has been completed. Notes This round of testing will focus on a general survey of pain points for gradebook 2 screens. Goals This test should discover: Can instructors accomplish their common tasks efficien

V

W

Page: Wireframes
Page: Wireframes and Functional Design Discussion

X

Y

Z

!@#$

  • No labels