Learning technology standar d s observatory
Download
1 / 65

Learning Technology Standar d s Observatory - PowerPoint PPT Presentation


  • 52 Views
  • Uploaded on
  • Presentation posted in: General

Learning Technology Standar d s Observatory. Luis Anido-Rifón Grupo de Ingeniería de Sistemas Telemáticos (GIST) University of Vigo. Contents. Project Team Introduction Support for a Dynamic Observatory A Multilingual Observatory Roles involved Interoperability Additional Functionality

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha

Download Presentation

Learning Technology Standar d s Observatory

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Learning technology standar d s observatory
Learning Technology Standards Observatory

Luis Anido-Rifón

Grupo de Ingeniería de Sistemas Telemáticos (GIST)

University of Vigo


Contents
Contents

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


The project team
The Project Team

  • PT leader: Luis Anido-Rifón

  • PT members:

    • Manuel Fernández-Iglesias

    • Martín Llamas-Nistal

    • Manuel Caeiro-Rodríguez

    • Judith Rodríguez-Estévez

    • Juan Santos-Gago

    • Fernando A. Mikic

    • Luis Álvarez-Sabucedo

      Grupo de Ingeniería de Sistemas Telemáticos

      ETSI Telecomunicación

      University of Vigo


Introduction
Introduction

  • The output of this work will be

    • A dynamic Observatory for Learning Technology Standards

    • A set of administration tools to manage the entire web site.

  • Different lingual versions of the observatory may be provided as a result of this work.

  • Further population will be based on administration tools with restricted permissions over the observatory data.


Support for a dynamic observatory
Support for a Dynamic Observatory

  • Structure and contents will be dynamic.

  • Structure will consist on a tree composed of a three-level category system and a fourth level for contents

  • Each node in the first three levels will have a page linked to it.

  • The fourth level will have as many pages linked as desired.


Support for a dynamic observatory ii
Support for a Dynamic Observatory (ii)

  • To create and fill the repository administrators will follow a three-step procedure:

    • Create the structure

    • Create contents (www pages)

    • Bind contents to nodes in the structure

  • The whole process will be supported by a Web-based authoring tool.







Generating a dynamic structure
Generating a dynamic structure.

  • Administration tools will allow to:

    • Create a node in the structure

    • Rename

    • Enable/Disable (visible / not visible)

    • Delete


Generating dynamic contents
Generating dynamic contents

  • Contents are supported by two main components:

    • Pages: containers for information

    • Elements: media elements to be included in pages

    • Pages  SCO

    • Elements  assets


Generating dynamic contents elements i
Generating dynamic contents. Elements (i)

  • Authoring tools provided will facilitate the creation of the following types of elements to be included in pages:

    • Paragrahps

    • Text + Images

    • Hyperlinks

    • Enumerates

    • Itemizes


Generating dynamic contents elements ii
Generating dynamic contents. Elements (ii)

  • Advanced elements will support to directly introduce HTML code in a page. In this way, other multimedia elements not included in the pre-defined elements can be used in the observatory.

  • A tool to upload embedded objects will be provided.



Generating dynamic contents ii
Generating dynamic contents (ii)

  • Pages may be annotated with keywords and areas (selected from a pre-defined set of areas of interest for the observatory). This information will be used by an internal search engine to help users to locate contents in the observatory.


Generating dynamic contents iii
Generating dynamic contents (iii)

  • Example: A page containing a description on LOM draft 4.0 may be annotated as follows:

    • Keywords: LOM, previous versions

    • Areas: Educational Metadata

    • The set of areas of interest will be dynamic (add a new area, remove, etc.)


Binding contents and structure i

So far, we have a container structure and a pool of pages with contents.

The last step is to bind a page from the pool to a node in the structure.

Binding contents and structure (i)


Binding contents and structure ii
Binding contents and structure (ii) with contents.

  • This binding is implemented through a simple UI where users just need to match the element of the structure with the page already created in the previous step.

  • This binding can be modified, removed or created at any time using the authoring tool.

  • The same page may be bind to two or more nodes in the structure



Index
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Multilinguality i
Multilinguality (i) with contents.

  • Different views of the observatory (structure+contents) may exist. One instance per EU language is possible.

  • Each lingual view of the repository will be managed by a concrete administrator responsible for the development and maintenance of its contents.

  • Different lingual versions may have different contents and structure.

  • The same individual may be responsible for more than one lingual version of the repository.


Multilinguality ii
Multilinguality (ii) with contents.

  • Different language versions may be completely different. Actual contents depend on those responsible for filling it; for example, User20 is responsible for the observatory in German, …


Multilinguality iii
Multilinguality (iii) with contents.

  • While User21 is responsible for the observatory in English


Multilinguality i v
Multilinguality (i with contents.v)

  • Interface towards standards observers will be automatically updated according to the information provided by administrators. Therefore, support for the whole set of EU languages will be automatically provided.

  • Nevertheless, some pre-defined labels are fixed (e.g. the word “news” to access the news system). Help from the WS will be required to translate them to the whole set of EU languages.

  • The interface for administration and authoring tools will be developed in English.


Index1
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Roles involved
Roles involved with contents.

  • There are four different roles involved:

    • Standards observers.

    • Administrators:

      • General administrator

      • Observatory administrator

      • Local administrator


Roles involved local administrator i
Roles involved: Local administrator (i) with contents.

  • Responsible for managing the structure and the contents below three-level nodes

  • They define subcategories below the second-level nodes.

  • They produce pages to be used in the third and fourth levels.



Roles involved local administrator ii i
Roles involved: Local administrator ( with contents.iii)

  • The same local administrator may be responsible for different categories in different lingual versions of the observatory


Roles involved local administrator iv
Roles involved: Local administrator ( with contents.iv)

For example, user2 may be responsible for entering and maintaining information on IEEE LTSC, LOM and PAPI in English and French and IMS consortium, LIP and SCORM in Spanish, while user 3 may be responsible for AICC and CMI in English, French and Spanish and IEEE LTSC, LOM and LIP in Italian.


Roles involved observatory administrator i
Roles involved: Observatory administrator (i) with contents.

  • Responsible for the dynamic development of the main structure of the Web site.

  • Responsible for one or more lingual views of the observatory.

  • He will also be allowed to act as local administrator in the lingual versions he is responsible for


Roles involved observatory administrator ii
Roles involved: Observatory administrator (ii) with contents.

  • At least, the observatory administrator would create a first level category for “standardization bodies” (with each body appearing as a second level category below it, e.g. LTSC, IMS, ADL, etc.) and for each standardization category or area (e.g. metadata, learner profiles, runtimes, packaging, etc.).


Roles involved general administrator
Roles involved: General administrator with contents.

  • Responsible for managing observatory administrators and local administrators (e.g. definition of new users, assignation of responsibilities).

  • The general administrator will have complete access to the different lingual versions of the repository available.


Roles involved1
Roles involved with contents.


Index2
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Interoperability i
Interoperability (i) with contents.

  • In addition to the previously presented dynamic information system, administrators will have the possibility to enter metadata about the different standards present in the repository.

  • For this, the PT will define a conceptual model and a binding to XML for describing e-learning standards and e-learning standardization bodies.


Interoperability ii
Interoperability (ii) with contents.

  • Administrators with the correct permissions will be allowed to fill a metadata record to be binded to a page.

  • Publication needs approval by the observatory administrator.

  • This record will be used to generate the corresponding XML file.


Interoperability iii
Interoperability (iii) with contents.

  • Metadata about e-learning standards (conceptual model):

    • Name: LOM

    • Version: 1.0

    • Date: June 2002

    • Area: Educational Metadata

    • Institution: IEEE LTSC

    • Editor: Erik Duval

    • Locator: http://ltsc.ieee.org/

    • Summary: This standard defines ….


Interoperability iv
Interoperability (iv) with contents.

  • Binding to XML

<standard>

<name>LOM</name>

<version>1.0</version>

<date>June 2002</date>

<area>Educational Metadata</area>

<institution>IEEE LTSC</institution>

<editor>Erik Duval</editor>

<locator>http://ltsc.ieee.org/</locator>

<summary>This standard defines…</summary>

</standard>


Interoperability v
Interoperability ( with contents.v)

  • The main page of the observatory will provide a link to those available downloable “metadata” files about the standards in the observatory

  • Although this data may also be displayed to standards observers, the main aim is to provide a mechanism to transfer information to other e-learning standards observatory/portals.


Index3
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Additional functionality i
Additional with contents. Functionality (i)

  • Open discussion forum

  • News: administrators will be able to define news which will be displayed in the Observatory.


Additional functionality ii
Additional with contents. Functionality (ii)

  • Events. administrators will be allowed to publicize events related to the learning technology standardization process. Initial data for an event will be the same as provided for a page in the observatory main structure. The home page of the observatory will include an events display area where they will be shown according to the event dates. Past events will be automatically deleted from this area.


Additional functionality iii
Additional Functionality (iii) with contents.

  • Events calendar. Using this information, a calendar with the information about events will be displayed to users.

  • News and events letter bulletin. Using data from news and events, the repository will create a monthly bulleting including news published and events celebrated during that month. This bulleting will be created in PDF


Additional functionality iv
Additional Functionality (iv) with contents.

  • Notification mechanism. There will be a notification mechanism to allow users to subscribe to the news and/or events information system. News and information on events will be sent by e-mail.


Additional functionality v
Additional Functionality (v) with contents.

  • Standards producers agenda. An agenda will be developed to provide access and contact information for those individuals actively involved in the learning technology standardization process. Approval for being included in the agenda will be granted by the general administrator.


Additional functionality vi
Additional Functionality (vi) with contents.

  • Internal search engine. To locate information on standards or standardization bodies. This engine will use keywords and areas marked when contents are annotated.


Index4
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Population
Population with contents.

  • The PT will fill the observatory with initial data on those standards and bodies indicated by the WS.

  • The main standardization bodies will be contacted and provided with local administration accounts to further feed the observatory, maintain and update their data.


Index5
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Technical issues
Technical issues with contents.

Due to the expertise of the team and the strict project deadlines, the development of the observatory will be supported by the following technologies and software infrastructure:

  • ASP.NET

  • SQL Server 7.0

  • MikTex

  • Propietary C++ software to create PDF news and events letter bulletin.


Index6
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Hosting
Hosting with contents.

The prototype will be developed and accessed from the University of Vigo facilities.

From September, 2003, the observatory will be deployed in an ISP that will provide ahigh-bandwidth access.


Index7
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Cwa i
CWA (i) with contents.

In addition to the above described observatory itself, it is expected that a CWA is developed and agreed upon, based on the contents of the design document. The final CWA is expected for delivery by end 2003.


Cwa ii
CWA (ii) with contents.

The PT suggest to focus the CWA contents on a reference manual to ease the further maintenance of the observatory:

  • Manual for administrators (local, observatory and general).

  • Manual for standards observers.

    In addition, the conceptual model for the metadata used to describe standards and standardization bodies should be defined as part of the CWA.


Index8
Index with contents.

  • Project Team

  • Introduction

  • Support for a Dynamic Observatory

  • A Multilingual Observatory

  • Roles involved

  • Interoperability

  • Additional Functionality

  • Population

  • Technical support

  • Hosting

  • CWA

  • Timeline


Timeline i
Timeline (i) with contents.

  • Key dates (year 2003):

    • March/april (Q1 meeting)

    • July (Q2 meeting)

    • October (Q3 meeting)

    • December (Q4 meeting)


Timeline ii
Timeline (ii) with contents.

  • By Q1 meeting:

    • First prototype of the administration tool for the general administrator.

    • First prototype of the observatory (English UI version).


Timeline iii
Timeline (iii) with contents.

  • By Q2 meeting:

    • Fully functional version of administration tools for:

      • General administrator

      • Observatory administrator

      • Local administrator

    • Second version of the observatory (fully functional version of the dynamic contents/structure and 50% of additional functionalities (forum, news, etc.) completed.

    • First draft of CWA

    • Filling the repository (English content)

    • Establisment of contact with standardization bodies


Timeline iv
Timeline (iv) with contents.

  • By Q3 meeting:

    • Fully functional version of the observatory.

    • Transfer to a commercial ISP.

    • Second version of the CWA.

    • Request for comments/suggestions.

    • Request for additional language versions (translations of labels for the UI to be provided by the WS)


Timeline v
Timeline (v) with contents.

  • By Q4 meeting:

    • Final CWA delivery.

    • Final version of the observatory (additional language versions implemented)


Thanks

VIGO with contents.

Thanks

  • Please send your comments to

    lanido@det.uvigo.es


ad
  • Login