MMI ORR Status

MMI Ontology Registry and Repository Status

MMI Ontology Registry and Repository and Associated Semantic Services

Testing phase: alpha
MMI ORR address: http://mmisw.org/orr

Noteworthy changes

  • 2010-06-30  1.9.8.alpha (20100630223813)
  • 2009-12-28
    • Named graphs have been enabled for programmatic registration of ontologies (219, 214)
  • 2009-12-17 - Ontology back-end 1.5.0beta3
    • New triple store server integrated and inference re-enabled. Preliminary tests satisfactory (229, 175)
  • 2009-11-30 - MMI ORR portal 1.7.0.alpha
    • Improvements in display of metadata information including clickable links (146)
    • "Remember me on this computer" feature implemented (207)
    • Code for checking UTF-8 charset in submitted ontologies was revised and improved (222, 43)
    • Programmatic direct registration of ontologies implemented (214)
    • Sample code for client applications implemented (65)
    • File upload for new version is now an alternative option besides in-place editing (203)
    • Other issues resolved: 194, 186, 208, 139, 226, 218, 223, 221, 209, 211
  • 2009-11-03 - MMI ORR portal 1.6.0.alpha
    • Several changes incorporated (from interim versions 1.5.0.alpha30)
    • Terms of Use link included (http://marinemetadata.org/orr/tou)
    • New wizards for registering external ontologies and corresponding new versions.
    • Important adjustments to address issues 177 and 99.
    • Bibliographical references now captured (issue 196).
    • Several other improvements
  • 2009-09-18
  • 2009-09-11:
    • General user account management, login, and password reset completed.
  • 2009-09-01:
    • Added "Search" functionality
  • 2009-09-01:
    • Initial version of Web VINE, to create term mappings, now integrated with MMI ORR. A test page has been created for testers.
  • 2009-06-08:
    • Initial version of the new portal has been released today for alpha testing (internal review).
    • Documentation page (this page) has been created with a summary of features as a starting point. Not everything is documented yet.
    • Please see the issue tracker.

Summary of features

  • Browse:
    • general browsing of the registered ontologies
    • Click any of the headers in the table to have the list sorted by that column. Click again to reverse the order.
    • First column is a menu with options to view the ontology in other formats and to see all available versions.
    • The left hand side comprises a tree view with submitters, authorities (abbreviation of the organizations) and type of ontology (mapping, vocabulary). The distinction between these type of ontologies still follows a simple heuristics while a more appropriate mechanism is incorporated.
    • Search ontologies
    • By default, any ontology having 'mmitest' or 'testing' as authority is NOT displayed in the browse list. These entries are only shown to the corresponding submitter. Administrators are always able to see all entries including the testing ones.
    • If the user is logged in, the tree section shows all the ontology submitters. Click on any submitter to only see her/his submitted ontologies.
  • Search terms
  • View ontology:
    • Clicking any of the entries in the browse list open en "ontology view" interface. The portal will load both the metadata and the contents (sometimes called "data" in these notes) of the ontology. If the user is allowed, the tool bar will include an option to edit a new version of the ontology.
  • Edit ontology:
    • Both the metadata and the data can be edited when entering the edit mode.
    • Three main cases are considered regarding the type of the ontology:
      • Vocabulary case: the portal determines whether the ontology can be edited with the voc2rdf general interface.
        • A tabular widget is displayed with the general functionality of the voc2rdf tool (basic in-situ editing of cells, and import/export of the contents in a CSV format).
        • A 'class name" field allows to indicate the name for the class for the corresponding terms in the table.
      • Mapping ontology: the portal determines whether the ontology can be edited with the VINE tool.
      • General ontology: Any other type of ontology.
        • A synopsis of the ontology contents in terms of classes, properties, and individuals is displayed in read-only mode.
        • In edit mode, an "upload local file" widget is included, which allows to replace the contents of the registered ontology.
        • Whenever a new ontology is loaded from disk, the portal asks the user in case there are fields in the metadata panel with different values in the uploaded file. The user can choose to keep the values already in the panel or overwrite them with the values in the uploaded file.
        • In any case, the contents (data) of the ontology will be replaced with the contents of the uploaded file.
  • Create vocabulary: Similar functionality as the editing of a new version (see above).
  • Upload a local file: This option allows the user to prepare and register an ontology by first uploading a local ontology. 
  • Create term mapping ontology: Preliminary but functional capability to create mappings (Web VINE)

 

Posted September 15th, 2009 by carueda
in