Now that 1.8 is out, I've been taking a look at the schema-modification related changes. I'm not entirely clear on whether the example of services/collectionobject/3rdparty/nuxeo-platform-collectionobject-hearst indicates the new preferred place to put our schema files (before, we were extending eg. the collectionobject schema in the nuxeo-platform-cs-collectionobject tree). Since it appears that a directory tree such as the nuxeo-platform-collectionobject-hearst example is the place to put our local core-types-config.xml files, I'm guessing it's also the proper home for our local .xsd file. The lifesci example of a local tenant bindings delta seemed pretty straightforward, so I adapted that to our local changes. Unfortunately, after running maven & ant and starting up nuxeo and collectionspace, I'm not seeing a collectionobjects_wac table in postgres as I did in MySQL: nuxeo=> \dt *wac* No matching relations found. ...and while creating an object via a sample XML payload with our custom schema returned success, the collectionobjects_wac part is ignored. Did I misinterpret any of the changes? Any tips on tracking down what isn't working? thanks, Joe