litvinovg/vitro
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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.

Browse source
This commit is contained in:
ryounes 2011-07-01 23:29:34 +00:00
parent 90d822c6b5
commit 7f07155cf8
2 changed files with 14 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/list_view_configuration_guidelines.txt
View file

@ -140,13 +140,25 @@ following <collated> elements:
?infoResource and core:InformationResource: ?infoResource and core:InformationResource:
<collated> <collated>
OPTIONAL { ?subclass rdfs:subClassOf core:InformationResource . OPTIONAL { ?infoResource a ?subclass
?infoResource a ?subclass ?subclass rdfs:subClassOf core:InformationResource .
} }
</collated> </collated>
- Postprocessing removes all but the most specific subclass value from the query result set. - 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 Datetimes in the query

2
webapp/src/edu/cornell/mannlib/vitro/webapp/dao/jena/ObjectPropertyStatementDaoJena.java
View file

@ -293,8 +293,6 @@ public class ObjectPropertyStatementDaoJena extends JenaBaseDao implements Objec
return Collections.emptyList(); return Collections.emptyList();
} }
// RY One oddity here is that SDB adds the bound variables to the query select terms,
// even if they're not included in the query.
QuerySolutionMap initialBindings = new QuerySolutionMap(); QuerySolutionMap initialBindings = new QuerySolutionMap();
initialBindings.add("subject", ResourceFactory.createResource(subjectUri)); initialBindings.add("subject", ResourceFactory.createResource(subjectUri));
initialBindings.add("property", ResourceFactory.createResource(propertyUri)); initialBindings.add("property", ResourceFactory.createResource(propertyUri));