wiki:doc/metadataEditor
Last modified 11 years ago Last modified on 01/31/06 11:21:28

Metadata editor

Learning Objects Editing

Eurêka provides a full featured powerful online editing tool for learning objects. You can access it either by creating a new learning object or by editing an existing one. Browse through the thematic navigation until you find the primary theme where you'd like the learning object to appear in. On your way you can create the hierarchy by adding new subthemes (See the section called “Themes, Navigation and Classification”).

You can also creating a new learning object based on a previoulsy created template. Templates are simply learning objects that have been tagged as template in the «Management» editing section. All data from the template will be cloned in the new resource. The learning object editor provides a complete interface separated in the nine LOM metadata categories. The apperance of the editor is completely configurable via Profiles.

Two special tabs have been added to overhaul LOM specifications. The first tab called «Management» contains metadata related to the way the learning object is used inside Eurêka. Using this section you can set a learning object as a template, modify the access rights to the learning object, the editorial validation status, the refusal reason (if any) and finally the type of resource. Setting a resource as «read-only» prevents all unwanted changes to it using the editor. By default, all resources automatically imported (read OAI-PMH and Eurêka spider) will be set to read-only since Eurêka should not normally have the editorial authority. The editorial validation status is required to let public users see learning objects. The type of resource is needed to let users embed binary files along with a given resource.

When changing the status of a resource you will reset its the internal validation date. This is the date used by OAI PMH and for displaying new learning objects on the home page.

If you need to embed binary files with a resource, use the «Files» tab. A file upload form will be displayed. Using default configuration, you are not allowed to upload files larger than 50 megabytes. Uploading a file will automatically set LOM 4.1 Mime type, LOM 4.3 Location. The binary files will be stored inside the database. Thus, you must follow the section called “Database Backup / Restore Procedure”, if you don't want to lose those files. Note

Note that when replicating a resource containing binary files, the original URL to the parent resource will be cloned. Thus, the binary files won't cloned, they will remain in the original learning object. In spite of this, it is not recommended to embed binary files in templates since I can become quite a choir to keep track of the original file.

Profiles

Profiles allow one to specify how editing and validation will be handled. One could create many profiles, one for each specific applications. For example, you could decide not to display certain LOM element that you believe to be superfluent for a given application. This might be done in order to simplify editing for people that do not need to know LOM implementation. Using profiles each LOM element can be specified as mandatory, recommended or simply not present. You can also let the user use vocabularies that extend LOM's specification for elements based on closed-vocabulary terms. For example, you could create a new vocabulary representing more adequately the reality of a certain country in terms of school system. This vocabulary could then be linked to LOM 5.6 element, allowing users to creating learning objects describing the reality of a given country. Moreover, profiles can be simplified so that they automatically expand all LOM categories on display.