Fullscreen

History: aw1l 3.1 Results

Comparing version 9 with version 12

VersionFast NextLast Version

@@ -Lines: 23-29 changed to +Lines: 23-29 @@

!!! Students
- On the student side, there where a total of 229 surveys and 223 selfrecording tables collected of invested time (divided in methodologies and subjects in Table 3).
+ On the student side, there where a total of 229 surveys and 223 self-recording tables collected of invested time (divided in methodologies and subjects in Table 3).
- {SHEET(id=16)}Table 3. Surveys and selfrecording tables handed in, for each work methodology and subject.{SHEET}
+ {SHEET(id=16)}Table 3. Surveys and self-recording tables handed in, for each work methodology and subject.{SHEET}

A count of the extra comments voluntarily written by the students in their surveys in the blank fields is shown in Table 4, classified by type of methodology and feeling.

@@ -Lines: 55-59 changed to +Lines: 55-59 @@

__Three examples of POSITIVE comments expressed after working with the TRADITIONAL methodology__
- # ''"I have not had any problem to communicate with the members of the group since that we are together in the class and taking profit of the smae spare hours is very helpful"''
+ # ''"I have not had any problem to communicate with the members of the group since that we are together in the class and taking profit of the same spare hours is very helpful"''
# ''"I think that the meetings in person improve the work much more, they are an enrichment for the person"''
# ''"All the possible doubts that we have had, have been able to ask directly to the teacher and this is also well"''

@@ -Lines: 67-71 changed to +Lines: 67-71 @@
The methodology for writing documents collaboratively and cooperative learning based on Wiki (“__Wiki methodology__”) comprises two aspects to allow sharing information, and following changes with an always ready available copy of your merged version (or any previous version, if needed):
(1)a Wiki-like philosophy or conception of the way of working (what e called "__Wiki philosophy__", from now onwards), as well as
- (2)a Wiki-like computer technology ("__Wiki technology__", according to definition and initial prototype of Wiki de Ward Cunningham, 1995).
+ (2)a Wiki-like computer technology ("__Wiki technology__", according to definition and initial prototype of Wiki from Ward Cunningham, 1995).

The "__Wiki philosophy__" means that:

@@ -Lines: 89-91 changed to +Lines: 89-116 @@
Then, some additional recommendations can be given (more Tiki-related, in this case):
+ It's advisable to define a structure of pages Wiki (book-like collection of Wiki pages, with the featured named "Structures" in Tiki).
+ * Make single Wiki pages to be as small and divided in sub-pages as possible, in order to avoid the attempts of simultaneous editions of the same content (remember that, up to present date, no Wiki engine can cope with merging the changes from simultaneous edits of the same page; a “Concurrent Versions System” -like tool would be needed instead). In case of attempt of simultaneous edition of Wiki pages of TikiSheets, Tiki would warn the user that another using is editing this content before him/her, and haven't saved or canceled edition yet.
+
+ In case of small tables, include them directly in the text with the proper Wiki format, so that these tables are created and will be editable directly within the body of the Wiki page.
+
+ In case of big tables, on the other hand, include them through the “wysiwyg” tables that are included in the Spreadsheets feature in Tiki starting in 1.9 version onwards (http://doc.tikiwiki.org/Spreadsheet - also known as ''TikiSheets'')
+
+ In order to include graphs:
+ # In case of common graphs (pie chart, multi-line, multi-bar, stacked bars), TikiSheet feature can generate graphics (figures) directly from the web spreadsheet in Tiki, and you can dynamically include them inside Wiki pages (changes in spreadsheet data will automatically update the figures shown in Wiki pages).
+ # In case of need of more complex or different graphs inside Wiki pages:
+ + Generate them with your favorite software (there are very nice free software tools to create them), and you need to convert them to bitmap images (like photos; formats *.jpg, *.png, or *.gif), either by exporting the graph as such through your software, or by taking a computer screenshot when the image is viewed and cropping it to your needs (different procedures depending on the operating system in the computer). Once the image is in the hard drive, then select it and press “Upload picture” from within the Wiki page edit form.
+ + In order to include many graphs generated from external software programs, an easy procedure to convert all of them from graphs in ))OpenOffice(( Calc or MS Excel (for instance), into single images on disk could be to save the spreadsheet as html - Web page. Image files should be either in the same directory as the generated html file, or in a folder of the same name as the html file, depending on the program). Then they can be uploaded as images or photos to the Wiki page as previously described.
+
+ The powerful “Category system” in Tiki can be used if some dynamic information and coordination is desired regarding the pages that are in on-going process, or just need to be polished, spell checked, improved markup, etc. (or already finished). Even if this would require some more training from students since they may not be used to categorizing content (web or desktop content). Each single object in Tiki can be categorized into one or many of the defined categories (http://doc.tikiwiki.org/Categories).
+
+ Once the edition of all the pages is finished, it is possible to export (“print” in Tiki language) at once the whole structure of Wiki pages in html. This can be done with the option "Wiki > Print", in the main menu, through selecting the “structure” of pages to print. This would be the equivalent procedure of working with a master document and sub-documents with standard Office software programs.
+ * Saving as web page on hard disk from Internet browser is needed again, selecting as “Full Web page” (or similar option, depending on the browser).
+ * Then a conversion of the html document on hard disk to common office document format is needed. From ))OpenOffice(( (OOo) , an extra step is needed and thus it will be explained here to illustrate a possible procedure. Open the html document with OOo (everything will be inside a single-cell long table). Select the whole content from inside the single cell of the table (the full contents of your document), copy it and paste it into a new (blank) OOo Writer document. Save this new document as text document (either ".sxw" or ".odt"). Then you can already edit the document as wished in that Office suite with normality (modifying styles and formats if needed, including a paginated initial index, header and footer, numbers of pages, etc.).
+
+ Before printing the final version in paper, the tasks from the " Editor-in-chief " figure/s are very recommended, as previously reported:
+ * synthesizing ideas,
+ * deleting repetitions,
+ * unifying styles and markup (that will be the minimum, thanks to the unified ".css" stylesheet employed by web portals such as Tiki does)
+ * improving the spelling and grammar of the text. A good dictionary (online or paper) and standard office spell check tools may help the editor in chief for this final review, specially when the most of the students didn't pay attention to this issues. Some help to reduce duty load at the end for the editor in chief, would be to promote single users to take care of it, and to use spell checking online tools while still editing through the web forms in the Wiki. These could be, for instance, the “Konqueror” Web browser for spell checking almost any language at real time while writing, for GNU/Linux, or also recently through the “Google toolbar” for any operating system, in case your language is supported.
+ * make a copy of the document in ".pdf" (there are nice free software tools which produce them, such as ))OpenOffice((, ))PdfCreator((, for instance.

History

Legend: v=view , s=source , c=compare, d=diff
Information Version Html Action
Tue 06 de June, 2006 17:07 CEST by Xavier.dePedro from 83.180.166.105 12
Current
Html v  s
Tue 06 de June, 2006 17:07 CEST by Xavier.dePedro from 83.180.166.105 12 Html v  s  c  d
Sat 03 de June, 2006 16:30 CEST by Xavier.dePedro from 83.180.153.74 11 v  s  c  d
Sat 03 de June, 2006 15:13 CEST by Xavier.dePedro from 83.180.153.74 10 v  s  c  d
Sat 03 de June, 2006 16:19 CEST by Xavier.dePedro from 83.180.153.74 9 v  s  c  d
Sat 03 de June, 2006 15:13 CEST by Xavier.dePedro from 83.180.153.74 8 v  s  c  d
Sat 03 de June, 2006 15:02 CEST by Xavier.dePedro from 83.180.153.74 7 v  s  c  d
Sat 03 de June, 2006 15:02 CEST by Xavier.dePedro from 83.180.153.74 6 v  s  c  d
Sat 03 de June, 2006 11:32 CEST by Xavier.dePedro from 83.180.153.74 5 v  s  c  d
Fri 02 de June, 2006 15:08 CEST by Xavier.dePedro from 83.177.57.188 4 v  s  c  d
Fri 02 de June, 2006 14:37 CEST by Xavier.dePedro from 83.177.57.188 3 v  s  c  d
Fri 02 de June, 2006 12:07 CEST by Xavier.dePedro from 83.177.57.188 2 v  s  c  d
Fri 02 de June, 2006 11:43 CEST by system from 0.0.0.0
creat des d'estructura
1 v  s  c  d

Col·laboren [toggle]

ub.edu Logo UAB Logo
ourproject.org Logo Agaur Logo
Logo de l'ICE de la UB

Traduccions automàtiques [toggle]