Forum .LRN Q&A: live demo of dotTeach

Dear Rafael, sadly there is no documentation available so it is a little bit hard to test your module if the goal is not clear. Do you have it handy somewhere so we can take a look at it ?

Thanks
Malte

Hi Jon,

I am very interested in learning about dotTEACH. Could you point me to a document that explains the overall idea of dotTEACH and the overall functionalities? Thanks in advance!

Thanks Caroline, I have updated the password:

Login email (ID): mailto:guest@weg.ee.usyd.edu.au
Password: demo

Peter: An older revision to the abstracted documentation of dotTEACH is available under the /doc directory of the package, here:
http://129.78.27.143:8006/weg-course-info/doc/

(UPDATE: Clicking on the referential 'Help' link in the navbar with dotTEACH installed will refer the user to the user manuals based on type, to give a greater detail into the guide of the functionalities; please note some [3] of these manuals are *.pdf versions)

Cheers,

Jon

Hi Caroline,

The permissions system with dotTEACH is such that professors (currently)
have a more limited access in regards to administrational duties.
I've just set up two more accounts on the server, to illustrate the
functionalities of a Department admin and Site-wide admin respectively:

email: mailto:deptadmin@demo.co
password: demo

email: mailto:swadmin@demo.co
password: demo

(Currently both accounts are not registered as a Professor to any
subject, so no units will come up in the drop-down box on the portal page)
Essentially, site-wide administrators will be able to add new subjects,
streams these subjects are allocated to, add/remove memberss
(professors) to these units, as well as designate which department
administrators are allocated to which department.

Any problems feel free to let me know, thanks

Jon

Hi,

Yes, dotTeach is a package used for streamlining the process of adding course information for subjects, to be used in a number of areas across a Faculty.
It should allow for communication of this information to students (external visitors), and as well as amongst course coordinators, by way of reporting tools developed so that information can be shared between these coordinators and administrators.

It is designed to be more than a documentation package, as it currently is used in conjunction with a stateful workflow process, uses content repositories of information (in parts) and also tools that are more application-specific (such as email forms, and graduate attribute reports). I guess this could be demonstrated easier on the server site (above), which you are more than welcome to test out.

I am not entirely sure about the implementation border for dotTeach, though.

Cheers,

Jon

Hello Peter,

Thank you for the kind comments and interest in the project. I am just a developer on the project; Rafael and Surath had primarily been the ones heading the development long before I came on. Though it is good to know that there is some (possible) re-implementation in other universities & colleges abroad.

In response to your queries:
1) Are you referring to the Graduate Attribute Report (ga_list) ? If so, it is possible to have it query more (or different) GA's; I originally had it query every possible GA in the database, based on entries by subject coordinators - but found this to extend that particular drag-down box much too long (around 200+ rows!); though it depends on how such attributes will be implemented in other places.

2) Yes, you are correct - though Curriculum Maps should effectively still show up; try this location:
http://129.78.27.143:8006/weg-course-info/course_maps?stream=2476
(of course, as more subjects appear and degrees are populated then this will be more 'complete', too).
Pre-requisite subjects for chosen units of study will also be highlighted in different colours.

3) For the purposes of our implementation, a student normally participates (on average) in four subjects per semester (term). This can easily be implemented to five, or six, but it will also change the size of the resulting schedule display.

4) On the main dotTEACH page, Step 3. (and the single Step 5.) tasks are not currently implemented - they may eventually link to our own (other) university services, and thus may not be applied generically. Sorry about the confusion, I should remove these steps from the page sometime.

5) You're right, Step 4. links to the communities, sub-communities etc. that a user is a member of. We have primarily designed dotTEACH with the focus that the main base of users are not familiar with dotLRN, and thus provide a symbolic link to some of the services that dotLRN provides (such as community forums, messages, etc.).

6) What link do you click to that doesn't receive a response? Sorry, I don't think the link you pasted showed up . :)

Cheers,

Jon

Hello all,

A brief update on the dotTEACH package:

- Developer's documentation manual is now available here:
http://www.users.on.net/~jsuen/tif-project/developers_manual.pdf
or, a *.doc version:
http://www.users.on.net/~jsuen/tif-project/developers_manual.doc
(it is up-to-date for the current release of dotTEACH, 0.91a)

- User guides (to aid in navigating the application) are available at the demo site:
http://129.78.27.143:8006/dotlrn/help
(and mostly contain links to *.pdf versions of the guides)

- The package itself (source code) can be downloaded here:
http://www.weg.ee.usyd.edu.au/software/

Cheers,

Jon