Feature Wiki
Tabs
Introducing Portfolio
1 Description
This page deals with the Portfolio component to be released with ILIAS 4.2. The idea of developing a Mahara Interface is discussed on the respective page.
- the portfolio required the revision of the Personal Desktop
- it builds on the extension of the Personal Website
- Personal Resources
- Blogs
- Skills/Competencies in Portfolio
- Portfolio Exercise
- reflect on their learning, their experiences, objectives and failures. These "learning diaries" can be kept to the learner or can be a part of an Portfolio Exercise.
- present themselves, their competencies and achievements to others. These "presentation portfolios" are created for and published to a target group defined by the learner him- or herself.
Learners can have several portfolios. Learners can choose for each portfolio what content they would like to present, how this content is structured and who should be able to see or comment on the portfolio. A portfolio consists of one or more tabs, it features a permanent link so people can access it via internet.
The portfolio allows for import of personal data from the Personal Data, use of skill-sets, content edited with the ILIAS page editor and resources from "My Workspace".
Learners own the portfolio and grant the access to others if they choose to.
- all enrolled users of the platform
- selected enrolled users (Access-list)
- send a link and access code to people not enrolled in ILIAS
- full access to anybody in the world wide web
Learners may use themes for their portfolios.
Learners can export their portfolios to HTML and get a zip archive. Other forms of export (leap2a or PDF) could be implemented for upcoming releases.
The portfolio feature can be switched on or off. It is possible to use only Blogs or the Personal Resources without the portfolio as such.
Meeting at 11 August 2011 in Cologne about current status of e-Portfolio implementation
- "Shared by Other Users" is to be renamed to "Resources of Other Users" (German: "Ressourcen anderer Benutzer")
- Public Comments
- will be available for files, blogs and web links (as in repository)
- will be available from "Resources of Other Users" list as action (overlay)
- will still be part of the info screen
- Private Notices
- will be avaible for all objects in the personal workspace (as in repository)
Blog
- Layout
- the profile picture as part of the page title can be switched off
- the page title should be bigger, needs white space
- blog postings should be enhanced using more whitespace and/or borders
- Public Comments
- should be separated more clearly from the content, e.g. wider title bar
- can be switched off
- will be shown below postings (in contrast to the overlays in the repository)
- embedded blogs in portfolios will keep "their" comments
- Usage of (scorm) page templates in portfolio pages
Portfolio
- Layout
- the profile picture as part of the page title can be switched off
- the page title should be bigger, needs white space
- Public Comments
- should be separated more clearly from the content, e.g. wider title bar
- can be switched off
- if deactivated, embedded blogs will also not have public comments
- Private Notices
- will not be available
- Navigation
- a tree navigation as in the skills management could be used to display all portfolios and their pages on the left side
- this could avoid confusion when switching between portfolios and their pages (2 very similar table GUIs)
- a breadcrumb will be added
- the portfolio title will be displayed in page screens (title should be moved from table title to header section)
- Pages need to be copied to other portfolios
- Input fields for portfolio and page titles are too small
- (Object Type) Icon is still missing
- "Edit" links should be renamed in "Edit Portfolio" and "Edit Page"
Exercise
- Existing blogs/portfolios can be used as exercise submissions
- A blog/portfolio can be used in several exercises at once
- Navigation between the exercise and the blog/portfolio has to be 1 click
- Working instructions and their file uploads have to be displayed in the blog/portfolio
- Information about the latest submission and a download link is to be given in the blog/portfolio
- A download link is needed in the exercise assignment list, too
- List of submissions: the public profile should be linked here
Skills Management
- Administratin: Explorer/Tables instead of Hiearchy Form should be used for editing
- Enty Page for users should give overview on all current skill levels
- Self-Evaluation should be offered on overview screen
- Presentation in Portfolios: It should be possible to hide certain skills.
Discussion needed
- Exercise wording has to be discussed
- exercise, assignment (Übung, Übungseinheit) vs. Aufgabe
- Abgabe / Einrechung is not used consistently
- Administration settings for Personal Workspace / Blogs / Portfolios
- Default settings
- Global switches to deactivate feature
- Global switches for public comments
- Personal Desktop
- Should workspace objects be integrated here?
- In what way should the central column (Selected [Repository] Objects, My Groups & Courses) be adapted?
Nice-To-Have / Postponed
- Tags in Blogs
- Pre-defined structure templates for Portfolio or Public Profile (as in Xing)
- Scorm Certificates
- Layout of exercise working instructions (community discussion needed)
- Personal Workspace: quotas
- German Term for Exercises: "Aufgaben" anstatt "Übungen" (community discussion needed)
Meeting at 16 June 2011 in Cologne about current status of e-Portfolio implementation
- New dropdown menu for Personal Desktop (former tabs are dropdown menu items)
- New submenu "My Workspace/Mein Arbeitsraum"
- New submenu "Personal Data/Persönliche Daten" with two tabs "Personal Data/Daten zur Person" and "Published Data/Veröffentlichte Daten"
- The former "Public Profile/Öffentliches Profil" is now called "My Profile/Mein Profil"
- It is possible to use a selected portfolio as "My Profile/Mein Profil" (instead of the personal data list).
- New submenu "Portfolios" where portfolios are created and edited
- It is possible to select one portfolio as "My Profile/Mein Profil".
- Add New Item-menu will be implemented like in repository
- For 4.2, the following objects can be added to the personal workspace (in later versions, more object types are possible):
- File
- Blog
- Weblink - new!
- Folder
- Certificate Exercise
- Certificate SCORM module - new!
- Certificate Test
Open Issues:
- Workflow for adding notices
- New Action menu entry to go to Notices
- New Icon for Workspace
- Instead of "Verifications" we will re-use the concept of "Certificates" and offer them for tests (already existing), SCORM modules (maybe) and exercises (new - needs to be implemented).
- Records / Content-Belege for wiki pages to which a user has contributed are postponed for 4.3. We need a reasonable way of creating an anonymised view on this content (even for forums). There is already a simple way to include a wiki page or a forum page by going via HTML export or creating a PDF via print view.
- General Layout:
- ILIAS main menu is deactivated.
- There is an ILIAS bar on top, incl. ILIAS logo and "Back to LMS"
- Below, the blog title is presented (no blog icon or other ILIAS elements).
- The blog text is presented with fixed width and two columns (content in main column, navigation and other elements in right column).
- A background image can be uploaded as background of blog title
- A background colour for the entire blog page can be defined.
- On top of the navigation bar (right side) there is an "About Me" block with name of blog owner, picture (if activated) and link to "My Profile".
- Under the navigation bar there is a new list of "Keywords" (these keywords can be added to each blog posting by the author).
- Will be postponed for 4.3. We need to collect experience with the current portfolio implementation before.
- In the blog it is necessary to get an easy access to the current assignment of the exercise.
- General Layout
- Reduced main menu (like in blogs)
- Fixed width
- Portfolio title and author are presented on top of the portfolio (no user picture).
- Page templates (SCORM) shall be used for portfolios to support two columns layout for example.
The specification has been amended by the workshop results documented on this wiki page. Please check that information, too.
- plan: brainstorm a list of your achievements, competences, learning goals, personal development plans, whatever, ...
- gather: hoard the material evidence ("artifacts") of whatever is on your list. it should go into a container to be kept safe.
- organise and select: tag and evaluate your artifacts
- reflect: write about your reasons for picking the artifact to substantiate whatever is on your list. how does it support your claims?
- get feed-back: peers or authorities might be invited to comment on your portfolio.
- get rich assessment: authorities assign grades for the portfolio that documents i.e. a project, semester work,...
- publish: present your portfolio or special selections of it to potential employers, social networks, ...
- move on: export and take the protfolio somewhere else
Features of an e-Portfolio system. Please add any feature that seems to be a part of an e-Portfolio system for you. You can mark a feature with your name and --, -, o, +, ++ to show how important you think the feature would be. If you have any source in the internet that explains the feature in detail, add a link to the source.
- Views and Artefacts, see Mahara (Alex Killing: +; Sonja Burgauer: ++)
- Groups, see Mahara (Alex Killing: -; Sonja Burgauer: +; Oliver Lang: ++)
- Friends and Messaging, see Mahara (Alex Killing: -; Sonja Burgauer: -)
- Topics of Interests, see Mahara (Alex Killing: +; Sonja Burgauer: -)
- Personal file repository, see Mahara (Alex Killing: o; Sonja Burgauer: ++)
- Blogs, see Mahara (Alex Killing: +; Sonja Burgauer: ++)
- Embed RSS Feeds, see Mahara (Alex Killing: +; Sonja Burgauer: o)
- Resumé Builder, see Mahara (Alex Killing: o; Sonja Burgauer: o)
- Managing Skills and Goals, see Mahara (Alex Killing: +; Sonja Burgauer: +)
- Import / Export
- Ready or adaptable to cover ELP needs (Europäisches Sprachenportfolio ESP) at educational level (ESP I,II,III) e.g.LOLIPOP. (Bernhard Schuler)
- Personal Document Center (as part/extension of the Personal Desktop)
- Weblogs
- Extension of the Personal Profile (with templates for „CV“-data, competences, goals, carrerplans etc.)
- Presentation Component or „Webfolio“ or „View(s)“
- Export-Function (xml, html, pdf...)
We prefer integration (and not the connection to already existing eportfolio-systems), because we want to minmize the effort concerning
- discussions and decisions about the „right“ e-portfolio-System for campuswide use,
- server maintenance
- user training
In preparation to that we compared and matched
- different lists of „portfolio activities“ (incl. empiric dates about their importance)
- the corresponding „e-portfolio“-features of elgg, mahara and pebblepad, and
- the already existing functions/features of ILIAS, that can be used to support portfolio work,
- the missing functions in ILIAS.
2 Status
- Scheduled for Release: ILIAS 4.2
- Funding: Hochschule Bremen
- Development: leifos
3 Additional Information
- If you want to know more about this feature, its implementation or funding, please contact: Alex Killing / killing (at) leifos.com
4 Discussion
Alex K., 21 Oct 2009: How are all these things exported, if the user leaves the system? HTML Export of the views? Is this sufficient?
the other Alex ;-), 21 October 2009: The portfolio belongs to the learner. She should be able to export the reflection part and the goals and the files and the views. HTML is fine for me.
Sonja: The whole portfolio should be exportable (lifelong learning), the chosen export format should be compatible with the established eportfolio-software (like mahara, elgg and the like). Mahara (which we use at the PHTG) is a sound eportfolio-system that is common in Switzerland and which serves our requirements. That's also one reason (among others) why we are voting for an interface to Mahara rather as an implementation in ILIAS.
Alex K.: I have added the links to mahara import/export demo and LEAP2A Spec.
Actually, in Mahara, you can
a) export all of the data or b) some of the views
b) as a Standalone HTML-Website or b) using the Leap2A format
- http://wiki.cetis.ac.uk/LEAP2A_specification
- http://wiki.mahara.org/Developer_Area/Import%2f%2fExport/Interoperability
Maybe it should be possible to export and import e-Portfolios?
TVT: As it seems in 4.2Alpha the exercise supports the writing of blogs not of blogposts. So for every exercise a new blog is created. Wouldn't it be better to let the learner chose whether to use an existing blog or create a new one?
TVT, 10.8.2011
You can submit a whole blog in an exercise in ILIAS 4.2 beta1. Which i highly appreciate.
But it would support usability if you don't see the "Finalize und submit"-Button anymore if you submited the blog already. Even better would be an according message at the blog-screen.
JF 24 Jan 2011: We highly appreciate this feature. We must continue the conceptual discussion. Subfeatures should be represented in separate feature wiki pages as soon as possible.
Matthias Kunkel, 24 Jan 2011: New version of specification uploaded (v 0.16)
Oliver Lang (PHTG), 11 Mai 2011: Nachtrag meiner Mail zum Jour Fixe (sorry, only in german)
Bei der Positionierung des Menüeintrages Portfolio ist uns an der PHTG unklar, warum das Portfolio bei dem Persönlichen Profil angesiedelt ist. Für uns wäre hier ein separater Menüpunkt eigentlich logischer. Auch wenn das persönliche Portfolio im Einzelfall stark mit dem persönlichen Profil verzahnt sein kann, sollte es wie die anderen Menüeinträge (Mail, Kalender, ...) behandelt und auffindbar sein.
Nicht ganz nachvollziehbar ist uns die Positionierung von Blogs unter Materialien.
Blogs sollten unserer Meinung nach wie alle anderen Objekte in ILIAS behandelt werden (Wiki, Lernmodul, ...). In diesem Zusammenhang erscheint uns die Option zur Erstellung von Blogs im Magazin, vor allem in Kursen und Gruppen sehr sinnvoll. In einigen Lehr-/Lern-Szenarien an der PHTG aber auch der Pädagogischen Maturitätsschule (z.B. in der Sprachenlehre) wäre ein "gemeinsam" geführtes Blog didaktisch sinnvoll. Hier steht nicht die kooperative und kollaborative Contenterstellung im Vordergrund, sondern vielmehr das Protokollieren von z.B. Gruppenprozessen. Durch die Vergabe eines Zeitstempels können im Blog die jeweiligen Posts einer bestimmten Entwicklungsphase zugeordnet werden - dies ist z.B. im Wiki nur getrennt vom Content im Verlauf möglich. Durch die Vergabe von z.B Kategorien/Tags könnten zudem Posts nach Autoren intern gefiltert werden.
Die Erstellung von Blogs kann in der Administration deaktiviert werden. Ist es auch vorgesehen, dass die Portfolio-Funktion global deaktiviert werden kann? Falls ja, welche Auswirkungen würde dies auf andere Funktionen haben? Speziell auf Blogs (werden diese dann auch automatisch deaktiviert, da Blogs momentan als Hauptbestandteil im Sinne eines Lerntagebuchs im Portfolio betrachtet werden)?
Bei den Materialien ist uns aufgefallen, dass nur ausgewählte Objekte erstellt werden können. Wäre es im Sinne eines persönlichen Resourcenmanagements bzw. -pools nicht sinnvoller, auch hier möglichst alle Objekte (auch Lernmodule, etc.) zuzulassen?
Ein wichtiger Aspekt ist für uns die Exportfunktion von Portfolios, wie sie z.B. in Mahara gegeben ist. Wir setzen Mahara nun seit 2 Jahren in einem Studiengang flächendeckend ein. In dieser Zeit haben bereits einige Studierende die Hochschule gewechselt. Durch die Exportfunktion in Mahara (Leap2A) konnten diese Studierenden ihr Portfolio inkl. aller Dateien und bereits erstellten Ansichten "mitnehmen" und weiter nutzen. Hinsichtlich des lifelong learnings sollte dies auch mit Portfolios möglich sein, die in ILIAS erstellt wurden. Zumindest ein Austausch zwischen verschiedenen ILIAS-Installationen sollte angestrebt werden. Ein alleiniger HTML-Export erscheint uns nicht praktikabel. Darüber hinaus ist der Export für uns bei dem eventuellen Wechsel der Portfolioplattform ein zentraler Punkt.
In MAHARA werden generell keine Rechte auf einzelne Artefakte vergeben, sondern man stellt die Materialien in einer oder mehreren Ansicht(en) zusammen und regelt somit die Zugriffsrechte. Also nur über Ansichten wird entschieden, wer (meine persönlichen) Dateien, Materialien, etc. sehen darf.
Beim ePortfolio von ILIAS haben wir beim Testen festgestellt, dass man Rechte auf einzelne Materialien vergibt. In den Portfolios von ILIAS (was unserem Verständnis nach den Ansichten in MAHARA entspricht) können jedoch keine Zugriffsrechte vergeben werden - bis auf die Default-Einstellung. Wir sind der Meinung, dass ILIAS auch die Option von MAHARA beinhalten sollte. Wir fragen uns darüber hinaus wie man die Container Portfolios anderen Personen freischalten kann? Man kann zwar ein Portfolio als Default(Profil) online schalten, aber wie ist es mit weiteren erstellten Portfolios? Also konkret: Wo entscheide ich wer mein Portfolio wo wann sehen darf?
Was auch nicht ganz klar ist: Wenn ein Portfolio als Default gesetzt wurde, können keine weiteren User-Information mehr (Name, Kontaktinformationen, etc.) aufgerufen werden.
Matthias - your minutes are wonderful, as is your way of chairing meetings. Thank for being such a good chairman and report writer! alexandra
5 Follow-up
Last edited: 17. Apr 2025, 15:09, Kunkel, Matthias [mkunkel]