up to all Development Components for VIVO 1.5

Model Swapping

Goal

Allow the VIVO application to display and edit models other than the default kb2 model. Allow the edit and display model to be edited by N3 editing. Allow the edit and display model to be browsed by using the normal RDF browsing capabilities of the system. Allow the editing of the menus and pages with the normal RDF browsing and N3 editing capabilities of the system.

In scope

  • Provide a way to indicate a model to use as the data model and a model to use as the display configuration model.
  • Editing the display and editing configuration model.
  • Support for index like pages for models that are not in the search index.

Discussion

Need to specify the read/write model and the display model. It seems that http query parameters are one basic way. That could be awkward but it would work as a first pass and would be useful for debugging. Another is that menu pages or edit configurations could be defined with specific models.

A mode based way of specifying a non-standard model was considered but the UI would be too confusing. This confusion was experienced with DataStaR with the “edit this dataset” feature.

Need to have a way to build index like pages without querying the Solr index.

Tasks

  • Implement a HTTP query parameter based model switching (done)
  • Implement model swapping for the individual profile page (1 day, in progress, mostly works)
  • Implement model swapping for N3 editing (2 day, in progress, partly works)
  • Implement custom form based model switching (3 day)
  • Implement a way to get class list like pages for non-standard models (3 days)
  • Create new ways to generate select lists in non-standard models (2 days)

Dependent components

These components may depend on the completion of this component.

  • New Menu Pages
  • Edit and display ontology and implementation
  • Ontology editor UI
  • No labels