From f25c835ccc40baf2566648500e1eca5a68d38acb Mon Sep 17 00:00:00 2001
From: ryounes <ryounes@440791e1-c2bf-4c1e-ad7c-caf3f8b0ebe8>
Date: Wed, 10 Aug 2011 16:47:31 +0000
Subject: [PATCH] In default list view, require subclass to belong to a
 classgroup. This is the same criterion we use for displaying class
 information elsewhere in the app.

---
 webapp/web/config/listViewConfig-default.xml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/webapp/web/config/listViewConfig-default.xml b/webapp/web/config/listViewConfig-default.xml
index cc24795ec..afa4cb7fb 100644
--- a/webapp/web/config/listViewConfig-default.xml
+++ b/webapp/web/config/listViewConfig-default.xml
@@ -22,7 +22,13 @@
             OPTIONAL { ?object rdfs:label ?label } 
             
             <collated> 
-            OPTIONAL { ?object a ?subclass } 
+            OPTIONAL { 
+                ?object a ?subclass.
+                # Require the subclasses retrieved to be in a classgroup, since others are not generally
+                # for display. See vivo-dev-all thread titled "Internal Entity and mostSpecificType,"
+                # Aug 9-10, 2011.
+                ?subclass vitro:inClassGroup ?classgroup 
+            } 
             FILTER ( afn:namespace(?subclass) != "http://vitro.mannlib.cornell.edu/ns/vitro/0.7#" )   
             </collated>