RAMS - Collaborative Workflow for eResearch

Owned by Former user (Deleted)
Last updated: Jun 18, 2007 by Former user (Deleted)Version comment
2 min read

RAMS: Collaborative Workflow for eResearch

Speaker(s): James Dalziel, Professor of Learning Technology & Director, Macquarie E-Learning Centre Of Excellence (MELCOE), Macquarie University, Sydney, Australia. james@melcoe.mq.edu.au

Session Abstract

RAMS (the Research Activity Management System) builds on the LAMS V2 architecture for sequencing of collaborative activities and applies it to eResearch processes such as team meetings, peer review and research lifecycle management. RAMS integrates with Sakai. This presentation discusses future directions for RAMS, including opportunities for closer Sakai integration.

Presentation Materials

  • This presentation was given virtually. For a zipped file containing PPT + audio, see the attachments. For a record of the chat Q&A, see below.

Podcasts

  • See audio in zip file in attachments.

Additional Information

The Q&A for this session was conducted via Skype chat - the record of this is below:

57:56 PM aeaglek says: Questions from audience
58:42 PM aeaglek says: What tools are in Rams, is there a chat room, discussion room, etc? When you use these tools, will they integrate it into the workflow? Is there anywhere we can find a list of tools that are already available beyond the LAMS site?
01:23 PM aeaglek says: What tools are in Rams, is there a chat room, discussion room, etc? When you use these tools, will they integrate it into the workflow? Is there anywhere we can find a list of tools that are already available beyond the LAMS site?
01:49 PM James Dalziel says: The current tools for RAMS are the same as LAMS, minus the quiz tool
02:07 PM James Dalziel says: You can explore them using the RAMS demo
02:24 PM aeaglek says: What is the difference in the code base between LAMS and RAMS?
02:29 PM aeaglek says: What does this branching mean in practice?
02:36 PM James Dalziel says: One new tool that is on our mind is a "task completion" tool - which may be a simple as a series of checkboxes, but this could then be useful for branching, etc
03:12 PM James Dalziel says: The code base is currently equivalent, but we don't know yet whether we'll need to diverge or not - if we can, we'll keep them the same, and limit changes to configurations and skins
03:47 PM aeaglek says: How is exception handling done? Such as if a reviewer is sick and need to be replaced?
03:54 PM James Dalziel says: Branching allows different users to go down different pathways; and this could be controlled by the user, the monitor, or the system (based on input data like which tasks have been completed - if we bulod the task completion tool!)
04:32 PM aeaglek says: Session over....
04:37 PM aeaglek says: Thank you James
04:43 PM James Dalziel says: For exception related to people, there is a part of Monitoring that allows you to control who is in the sequence, and you can add new people here. We haven't yet got roles as part of this, but this is whether this would be done in the future.