The Drupal mEducator 3.0 installation includes a Resource metadata description content type, which was created following the meducator metadata schema. A user can create a metadata description for objects outside of the platform as well as for objects that exists in the platform.


Drupal mEducator 3.0 installation profile exposes all available metadata description through a SPARQL endpoint.  In the installed instance the SPARQL endpoint exists in the following address:


A web interface for querying the metadata description database is also available at the same address.

More functionality added using the RESTFULL web services API of the Drupal. SPARQL endpoint is accessible through a simple web service implemented using HTTP and the 3 basic principles of REST:  

  1. A base URI for the web service, which is: http://www.meducator3.net/drupal/sparql (for our installation).
  2. Internet media types of the data supported by the web service, which are: XML, Plain, Turtle, JSON, Serialized PHP, RDF/XML, Query Structure, HTML Table,TSV.
  3. A set of operations supported by the web service using HTTP methods which are: select, construct, ask, describe, load, insert, delete, dump.

The RESTFULL Web services API supports, also, an API key (optional) for restricting the access to specific users only.

Advanced search functionality included out the box. Users can search the metadata descriptions using all possible combinations, through a detailed constructed form, accessible via a web interface.  Future work, will allow the users to search not only the platform’s metadata descriptions, but also other resources, through a connected (one or more) SPARQL endpoints. The connected SPARQL endpoints must expose their information according the meducator metadata schema.

Batch import and export of the metadata descriptions are included. A user can transfer data between different meducator Drupal installations. The URIs of the transferred metadata descriptions remaining the same after the transfer, using Persistent URL (PURL) functionality.

Each user of the platform has its own FOAF profile, which can be extended as needed. A special feature is the relationships module. create relationship types (friend, co-worker, student, etc). Relationship types can be setup to be one-way or mutual. If a relationship type is one-way (subscriber) only the requester is shown as relating to the requested. Relationship types can also be set as needing or not needing approval. Administrators can give users the option to auto approve relationships on a per-relationship type basis. When creating or editing new content, the user can give special permissions (e.g. view, update, delete) to each one of his/her relationship groups, for example give update permissions to his/her colleagues. 

Several content types included as an example and administrators can create their own content types.  Each new content type can have a resource metadata description. Currently, in Drupal mEducator 3.0 installation profile the following content types included and working out of the box: Articles, Video, Presentations.

Some other features included in the installation profile are: OpenID login support, SPARQL endpoints views, SMART Link connection API, etc.