Current Release

This documentation covers the latest release of VIVO, version 1.14.x.
If you are able to help contribute to this documentation, please contact vivo at lyrasis dot org
Looking for another version? See all documentation.

Overview

The emphasis in ontology design has been fewer properties connecting more classes. For example, we see that the relationship between a Person, an Authorship, and an Article is very similar to the relationship between a Person, an Award Receipt and an Award. Similarly, a data property can be re-used by a set of classes and its subclasses. 

The profile pages in VIVO have been organized by properties. This re-use of properties makes it difficult to organize information on the page. Not only do we want to see at a glance the difference between an authorship and a received award; we may also want to display them in different areas of the page, using different custom views, etc.

VIVO allows us to create "faux" properties, as restrictions on object or data properties. The faux property has the same property URI as its base property. Range of faux data properties is always the same as range of base data property. Domain and range of faux object properties and domain of faux data properties are limited to not disjoint classes. Once we have established these criteria, we can assign display properties to the faux property, just as if it were its own property with its own URI.

In this way, we can define faux properties as follows:

URIDomainRangelabelproperty group
relatedByPersonAward or Honor Receiptawards and honorsBackground
relatedByPersonAuthorship

selected publications

Publications
relatedByAward or HonorAward or Honor ReceiptreceiptsOverview
relatedByInformation Content EntityAuthorshipauthorsOverview
relatesAward or Honor ReceiptPersonaward or honor forOverview
relatesAward or HonorAward or Honor Receiptreceipt ofOverview


Now, these same relationships display quite differently:


In general, it makes sense to partition all of a property into faux properties. Then the base property is set to be invisible (except to the root user), and the faux properties display the desired information.

What do you need to know?

How to follow the GUI for faux properties.

Getting started

VIVO comes with a default set of faux properties. You can edit them to suit your display requirements, or make more extensive modifications.

Creating a faux property

First, navigate to the control panel for the property (object or data) you want to create a faux property for.  The control panel can be accessed by clicking Object Property Hierarchy or Data Property Hierarchy on the Site Administration Page, then clicking on an object property, i.e. related by, or in the case Data Property Hierarchy by clicking on a data property, i.e. additional name. The Create New Faux Property button can be found next to a list of that property's existing faux properties.


Editing a faux property

There are several ways to navigate to the Faux Property Editing Form. Perhaps the most common way is to show the profile page for an individual, and turn on verbose property display.

In this example, we see that positions is a faux property of vivo:relatedBy. If you click on the link for positions, you will see the Faux Property Editing Form for positions. On the other hand, if you click the link for vivo:relatedBy, you will see the Object Property Editing Form for vivo:relatedBy. In addition to the parameters for vivo:relatedBy, you will also see links to each of the faux properties that are based on it:

From each of these pages, you can modify or delete the faux property that is displayed. 

Alternatively, the Faux Property Editing form can be accessed by navigating to the Site Administration Page and clicking Faux Property Listing. This will display the complete list of faux properties. Click the title to access the editing form for that faux property.

Note: Faux property custom list views are configured in the Faux Property Editing form, rather than as documented in Custom List View Configuration for ontology properties.


  • No labels
Write a comment...