diff --git a/config/example.runtime.properties b/config/example.runtime.properties index a25e5922..6e61088d 100644 --- a/config/example.runtime.properties +++ b/config/example.runtime.properties @@ -143,7 +143,13 @@ visualization.temporal = enabled # The format for this property is id, name; id1, name1; id2, name2 etc. # See Service Metadata from this page http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi # for more information. -Vitro.reconcile.defaultTypeList = http://vivoweb.org/ontology/core#Role, core:Role; http://vivoweb.org/ontology/core#AcademicDegree, core:Academic Degree; http://purl.org/NET/c4dm/event.owl#Event, event:Event; http://vivoweb.org/ontology/core#Agreement, core:Agreement; http://vivoweb.org/ontology/core#Location, core:Location; http://xmlns.com/foaf/0.1/Organization, foaf:Organization; http://xmlns.com/foaf/0.1/Person, foaf:Person; http://vivoweb.org/ontology/core#InformationResource, core:Information Resource +Vitro.reconcile.defaultTypeList = http://vivoweb.org/ontology/core#Role, core:Role; \ + http://vivoweb.org/ontology/core#AcademicDegree, core:Academic Degree; \ + http://purl.org/NET/c4dm/event.owl#Event, event:Event; \ + http://vivoweb.org/ontology/core#Location, core:Location; \ + http://xmlns.com/foaf/0.1/Organization, foaf:Organization; \ + http://xmlns.com/foaf/0.1/Person, foaf:Person; \ + http://purl.obolibrary.org/obo/IAO_0000030, obo:IAO_0000030 # # Types of individual for which we can create proxy editors. diff --git a/doc/upgrade-1.6.html b/doc/upgrade-1.6.html index 6fdd5356..0cb35e51 100644 --- a/doc/upgrade-1.6.html +++ b/doc/upgrade-1.6.html @@ -51,6 +51,7 @@
webapp.name
In previous releases, Solr was deployed to Tomcat with a RemoteAddrValve
@@ -163,7 +166,9 @@
Sites that need to secure Solr are now left to their own devices.
+
In previous releases, the properties file for the VIVO logging system
@@ -175,7 +180,9 @@
Note that debug.log4j.properties
, if present, will still
override the default.
With release 1.6, the property group menu bar that was used on profile pages has been replaced @@ -183,7 +190,9 @@ within that group while the contents of the previously displayed group will be hidden. The array of tabs also includes a "View All" tab that, when clicked, displays the contents of all the property groups.
+
The VIVO software now supports the development of SPARQL query data getters that can be associated
@@ -195,7 +204,9 @@
data getters:
https://wiki.duraspace.org/display/VIVO/Enriching+VIVO+Content+Using+SPARQL+Query+Data+Getters
.
The template individual--foaf-person.ftl has been moved to the "templates" subdirectory in the wilma
@@ -204,7 +215,9 @@
theme directory or, if your installation does not have it's own theme directory, in the
themes/wilma/templates subdirectory
.
VIVO now supports multiple profile pages for foaf:Persons. This feature, which is optional so installations
@@ -218,7 +231,9 @@
Websnapr.) For more information on how to implement multiple profile page views, refer to this wiki page:
https://wiki.duraspace.org/display/VIVO/Multiple+foaf%3APerson+Profile+Pages
.
For Release 1.6 the VIVO Home Page has been redesigned. The Search field beneath the "welcome" text now @@ -229,7 +244,9 @@ activities and organizations; and, optionally a global map showing researchers' areas of geographic focus.
+The RDF files that initialize the data model have moved, in both the distribution and @@ -326,7 +343,9 @@ <include name="context.xml" /> </patternset>
+VIVO 1.6 includes limited support for other languages, in addition to American English. @@ -350,7 +369,9 @@ Add a new language to VIVO.
+In VIVO 1.6, the response to requests for linked data is changed, to be smaller and faster. @@ -391,8 +412,17 @@ VIVO release 1.6 can be configured to produce extended linked data like previous releases. However, extended linked data will not be supported in future releases.
-
+ The list of default types for Google Refine has changed, to accomodate changes in the
+ ontology. If you are using Google Refine, you may need to change your runtime properties
+ accordingly. The new defaults appear in example.runtime.properties
.
+