up to all Development Components for VIVO 1.5
Component description
Goal:
Create an ontology or set of annotations that will allow the configuration of important editing and display behaviors of a vitro system. Create a way to edit this configuration in a running vitro system through a web interface. Implement the the changes needed to support the behaviors configured in the vitro system.
Discussion questions:
Should we make the application ontology an annotation ontology or a logical ontology?
Can we just use the vitro-0.7.owl annotations for most things for now?
Scope of the component for v1.5
Implementing existing behaviors and and editing of existing behaviors.
It is not clear if implementing new behaviors is in our out of scope.
Configurable items:
- Different display label for a property depending on the type of the profile page
- For a class, have a way to specify which properties should be offered for editing and display
- Have a way to specify the method for generating pick lists in different situations
- Sorting or collating a list of statements by the type of the object (this be done with a custom list view, it would be nice to do this through the web interface) VIVOFEED-1018
- Display limits, display rank and display tiers for classes
- Per class display limits and display tiers for properties
- What classes get included in the search and indexes
- Menu configuration
- Class groups (as display ontology sub classes?)
- per class custom entry form, custom display view, custom search view
- display level and update level permissions?
- Select from existing and offer create new
- property groups?
Design work needed for the component
At least four parts:
- Annotations or ontology for configuring the editing and display aspects of a VIVO system.
- Designing how the information will be stored, the first-time loading of a configuration, and a way to edit this configuration.
- UI design for editing the display and editing configuration
- Modifying the N3 front-end editing system to support this editing
- Implement the display and editing code to support the configuration
Can this component be addressed in stages?
The existing annotations could be used as the first version to avoid the ontology design work and the implementation of behaviors. Then this item would be reduced to just implementing editing the configuration with the N3 editor.
Dependency on any other component
Possibly on the ability for N3 editing to work with graphs other than the main VIVO data graph.
