Wiki source code of The AISOP recipe
Version 1.5 by AISOP Admin on 2025/01/14 20:31
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | (% class="jumbotron" %) |
| 2 | ((( | ||
| 3 | (% class="container" %) | ||
| 4 | ((( | ||
| |
1.4 | 5 | = The AISOP recipe = |
| |
1.1 | 6 | |
| |
1.4 | 7 | The AISOP webapp is a service built as the result of various training and configurations. |
| 8 | This recipe explains how to extract the content fragments, annotate them, and create model trained on it. This will let us create a pipeline and a seminar on which we can analyse portfolios. | ||
| |
1.1 | 9 | ))) |
| 10 | ))) | ||
| 11 | |||
| |
1.5 | 12 | |
| |
1.4 | 13 | == Basic Terms == |
| |
1.1 | 14 | |
| |
1.4 | 15 | The context of the AISOP-web-app usage is that of a course at learning institution which typically has fixed students and fixed contents. A course can contain multiple courses or modules. |
| |
1.1 | 16 | |
| |
1.4 | 17 | * **AISOP Web-app:** The nodeJS server that interfaces with the portfolio-composing system. |
| 18 | * **Portfolio:** the content written by a student in order to represent his or her progress, learning and knowledge using a textual and graphical form. Generally expressed in HTML, can be embedded in various web-pages. | ||
| 19 | * **Course-contents:** The set of slides, their annotations, the videos and handouts that normally read by students and teachers. | ||
| 20 | * **Analysis:** The set of programmes that recognize and measure the contents of a portfolio. Often also the name of the resulting interactive presentation (which can feature summaries or enriched portfolio views). | ||
| 21 | * **Composition Platform:** A space where the portfolio is written. Normally a web-space. In AISOP we have focussed on the classical e-portfol;io composition platform Mahara (a PHP server). | ||
| |
1.1 | 22 | |
| |
1.4 | 23 | ---- |
| |
1.1 | 24 | |
| |
1.4 | 25 | (% class="wikigeneratedid" %) |
| 26 | == 1) Data Preparation == | ||
| |
1.1 | 27 | |
| |
1.4 | 28 | === 1.1: Make a Concept Map === |
| |
1.1 | 29 | |
| |
1.4 | 30 | Employing tools such as CMapTools, create a graphical concept map that represents the topics of the course. This concept map can be familiar with the teachers and learners of this course as a way to show the paths through the content. |
| |
1.1 | 31 | |
| |
1.4 | 32 | From the concept map, extract a .cxl file which carries the same information and will be presented on the web-page. |
| |
1.1 | 33 | |
| |
1.4 | 34 | From the concept map, also extract a hierarchy of topics, assuming there is more than (approx) 10 topics in the map. The hierarchy should be a text file with a label per line and the label indented to the right in case of children relation as in the following example: |
| |
1.1 | 35 | |
| |
1.4 | 36 | >Algorithmization |
| 37 | > Flow Charts | ||
| 38 | > Programming | ||
| 39 | > Programming Paradigm | ||
| 40 | > Imperative Programming.... | ||
| |
1.1 | 41 | |
| |
1.4 | 42 | === 1.2: Extract Text of the Course Content === |
| |
1.1 | 43 | |
| |
1.4 | 44 | In order for the topic recognition to work, a model needs to be trained that will recognize the words used by the students to denote a part or another of the course. This allows to create relations between the concepts of the course and the paragraphs of the portfolio and offer these in the interactive dashboards. The training is the result of annotating fragments of texts which, first, need to be extracted from their media, be them PDF files, PowerPoint slides, scanned texts or student works. These texts will not be shared so that even protected material or even personal-information carrying texts can be used. |
| |
1.1 | 45 | |
| |
1.4 | 46 | Practically: |
| |
1.1 | 47 | |
| |
1.4 | 48 | * Assemble the documents |
| |
1.1 | 49 | |
| |
1.4 | 50 | === 1.3: Annotate Text Fragments === |
| 51 | |||
| |
1.1 | 52 | Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. |
| 53 | |||
| |
1.4 | 54 | ---- |
| |
1.1 | 55 | |
| |
1.4 | 56 | == 2) Deployment == |
| |
1.1 | 57 | |
| |
1.4 | 58 | === 2.1 Train a Recognition Model === |
| |
1.1 | 59 | |
| |
1.4 | 60 | ... |
| 61 | |||
| 62 | === 2.2 Create a Pipeline === | ||
| 63 | |||
| 64 | ... | ||
| 65 | |||
| 66 | === 2.3 Create a Seminar and Import Content === | ||
| 67 | |||
| 68 | ... | ||
| 69 | |||
| 70 | === 2.4 Interface with the composition platform === | ||
| 71 | |||
| 72 | ... | ||
| 73 | |||
| 74 | ---- | ||
| 75 | |||
| 76 | == 3) Usage == | ||
| 77 | |||
| 78 | === 3.1 Invite Users === | ||
| 79 | |||
| 80 | ... | ||
| 81 | |||
| 82 | === 3.2 Verify Imports and Analyses === | ||
| 83 | |||
| 84 | ... | ||
| 85 | |||
| 86 | === 3.3 Observe Usage and Reflect on Quality === | ||
| 87 | |||
| 88 | ... | ||
| 89 | |||
| 90 | === 3.4 Gather Enhancements === | ||
| 91 | |||
| 92 | ... on the web-app, on the creation process, and on the course | ||
| |
1.5 | 93 |