NIHVIVO-2733 Add custom list view for core:linkedRole - uses core:relatedRole view, with adaptations to fit both properties. Collation support for core:hasEditReviewRole. Improvements to the custom list queries and templates for core:hasRole, core:relatedRole, core:hasEditReviewRole.
This commit is contained in:
parent
90d822c6b5
commit
7f07155cf8
2 changed files with 14 additions and 4 deletions
|
@ -140,13 +140,25 @@ following <collated> elements:
|
|||
?infoResource and core:InformationResource:
|
||||
|
||||
<collated>
|
||||
OPTIONAL { ?subclass rdfs:subClassOf core:InformationResource .
|
||||
?infoResource a ?subclass
|
||||
OPTIONAL { ?infoResource a ?subclass
|
||||
?subclass rdfs:subClassOf core:InformationResource .
|
||||
}
|
||||
</collated>
|
||||
|
||||
- Postprocessing removes all but the most specific subclass value from the query result set.
|
||||
|
||||
- Alternatively (and preferably):
|
||||
<collated>
|
||||
OPTIONAL { ?infoResource vitro:mostSpecificType ?subclass
|
||||
?subclass rdfs:subClassOf core:InformationResource .
|
||||
}
|
||||
</collated>
|
||||
|
||||
Automatic postprocessing to filter out all but the most specific subclass will be removed
|
||||
in favor of this implementation in the future.
|
||||
|
||||
- Both collated and uncollated versions of the query should be tested, since the collation value
|
||||
is user-configurable via the ontology editor.
|
||||
|
||||
----------------------
|
||||
Datetimes in the query
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue