Tools should be be able to be better integrated with one another and linking between tools should be handled in a standard way by the framework. eg: 1) gradebook/assignments, 2) resources/assignments, 3) gradebook/discussion,
To expand on this requiremnet: There needs to be a way to link tools to each other within the sakai framework. In other words, something like "Tool A depends on Tool B version 1.5 and cannot function without it" should be specified in the tool xml file. Also, there should be ways for Tool A to pull data from Tool B or send data to Tool B that are standardized and confidured via an XML file contained within the structure of Tool A.
Use-Case: I have an attendance tool (AT tool) that I have written. My attendance tool works by interfacing with a system at my university which records attendance using "clickers" that students operate to indicate their presence in class. This data is stored in an external database which is part of the attendance system. The instructor accesses this database through the AT tool. The instructor can use the tool to calculate grades based on the attendance data from the external system and send a grade item and set of grades to the gradebook tool being used in his course site. The grades are calculated based on a set of rules in the AT tool. The instructor may create multiple grade items or choose to update an existing grade item. The key is that the AT tool has to be able to get a list of grade items, or send a list of grades and a grade item definition to the gradebook tool. It also needs to be able to send a grade item ID and a set of grades and probably needs to get the updated grades.
This is obviously very complicated and this requirement only talks about it on a fairly non-technical level. The key here is some standardized way of linking tools together and defining input and output of data.
CLE team bulk inactive issues cleanup - if this is important then reopen or create a new issue
David Horwitz February 23, 2010 at 6:32 AM
MAINT TEAM REVIEW: This feature request is currently unassigned and will be reviewed. In line with stated Jira practice http://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines Feature requests that are not going to be implemented will be closed with a status of "wont fix". If you intend implementing this issue please ensure that its up to date and assigned correctly
Aaron Zeckoski February 26, 2006 at 10:41 AM
Ready for voting
Aaron Zeckoski February 10, 2006 at 12:26 PM
I expanded on the requirement and added a use case to it. -AZ
Tools should be be able to be better integrated with one another and linking between tools should be handled in a standard way by the framework.
eg:
1) gradebook/assignments,
2) resources/assignments,
3) gradebook/discussion,
To expand on this requiremnet:
There needs to be a way to link tools to each other within the sakai framework. In other words, something like "Tool A depends on Tool B version 1.5 and cannot function without it" should be specified in the tool xml file.
Also, there should be ways for Tool A to pull data from Tool B or send data to Tool B that are standardized and confidured via an XML file contained within the structure of Tool A.
Use-Case:
I have an attendance tool (AT tool) that I have written. My attendance tool works by interfacing with a system at my university which records attendance using "clickers" that students operate to indicate their presence in class. This data is stored in an external database which is part of the attendance system. The instructor accesses this database through the AT tool. The instructor can use the tool to calculate grades based on the attendance data from the external system and send a grade item and set of grades to the gradebook tool being used in his course site. The grades are calculated based on a set of rules in the AT tool. The instructor may create multiple grade items or choose to update an existing grade item.
The key is that the AT tool has to be able to get a list of grade items, or send a list of grades and a grade item definition to the gradebook tool. It also needs to be able to send a grade item ID and a set of grades and probably needs to get the updated grades.
This is obviously very complicated and this requirement only talks about it on a fairly non-technical level. The key here is some standardized way of linking tools together and defining input and output of data.