Skip to end of metadata
Go to start of metadata

Page Contents


Unless otherwise noted, the migration items are cumulative. Thus, beginning with one's current version level, all items from all subsequent sections, i.e., (increasing) version levels, should be checked for possible applicability.

Migration from 6.0.x

Installation Update: web.xml

If your EDG installation uses a web.xml for 6.0 or older(for details, see Server Installation and Integration > Tomcat Installation Instructions), you can update it with the following elements:


Collection Optimizations are Enabled

Segregating schema definitions to ontologies only, is a recommended practice, and it also enables performance optimizations on other collection types. This can no longer be disabled (easily). EDG will block the importation of graphs that would violate this condition. For background and details see: 5.3 Migration > Schemas Restricted to Ontologies and Ontology Editor > Classes vs. Instances.

NOTE: If necessary, administrators can disable this optimization through a SPARQL update; contact TopBraid Support for details.

SHACL-based Ontologies Required to View/Edit Assets

The tabular-editors of EDG collections (for searching, viewing, and editing assets) requires the underlying schema to be backed by SHACL. To migrate a collection's included ontologies to a SHACL basis, see: Ontology Utilities > Convert OWL Axioms to SHACL Constraints.

Reference Dataset: Must Receive A Primary Key

Reference datasets no longer allow classes without a primary key property to be used as their main entity. For background and details, see: Reference Datasets > Ontology for main entity class.

Find Code Searching Requires Explicit Datatypes

Find Code searching requires that the underlying schema (main entity class) defines a sh:datatype constraint for any non-string code (ME datatype property).

  • No labels