Hey folks, Looks like I've run into a tenant-specific problem. I've recently reinstalled CSpace 1.8.3 from the tarballs, and followed the directions at http://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant+using+the+mini-build to create our tenant. So far I've made modifications to bunde/core-message.properties, and html/pages/CatalogingTemplate.html, both of which have worked as I'd hoped. What I'm running into right now is an inability to create catalog objects, either with my modified template (hid a few fields) or even after copying back the version in tenant-customizations-v1.8/ui/defaults/html/pages and redeploying. I've also restarted the cspace server in case the quick deploy was to blame. Regardless, when I try to create a catalog object I get an error in the UI such as this: URL:http://localhost:8180/cspace-services/collectionobjects/: STATUS:400:Create request failed: org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not found: dublincore:title. Document '/wac-domain/workspaces/CollectionObjects/e1a269b2-5551-4c94-84af' with title 'e1a269b2-5551-4c94-84af' and type 'CollectionObject' does not have any schema with prefix 'dublincore' I'm not seeing this problem in the lifesci tenant, which I've made no changes to. Does this error give anyone ideas about what might be going on? Debugging tips? thanks, Joe

Hi Joe, Richard Millet pointed out that one potential cause of this error might be if a common or extension schema (an extra 'part' that you might have added to the CollectionObject record, to add new fields), is missing "dublincore" in the list of schemas associated with its document type. This association between schemas and document types is declared in the OSGI-INF/core-types-contrib.xml file. Richard noted the following declaration of the common schema as an example: <?xml version="1.0"?> <component name="org.collectionspace.collectionobject.coreTypes"> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="schema"> <schema name="collectionobjects_common" prefix="collectionobjects_common" src="schemas/collectionobjects_common.xsd"/> </extension> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="doctype"> <doctype name="CollectionObject" extends="CollectionSpaceDocument"> <schema name="common"/> <schema name="dublincore"/> <schema name="collectionspace_core"/> <schema name="collectionobjects_common"/> </doctype> </extension> </component> Within your services/collectionobjects/3rdparty directory tree, you might look at each of your core-types-contrib.xml files to see if that might be the issue. In your note below, you didn't mention having made changes in the services layer to CollectionObject, so Richard and I have been trying to think of how else this problem could have cropped up ... If only your own tenant references a particular extension schema for CollectionObjects, and that 'dublincore' issue is present only in the packaging up of that particular schema into a Nuxeo document type (e.g. in core-types-contrib.xml), that might help explain why creating a CollectionObject in your tenant fails but that same operation succeeds in the lifesci tenant. Aron P.S. If you wish, you can privately send Richard and me copies of all of your *collectionobject* .jar files from $JBOSS_HOME/server/default/deploy/nuxeo.ear/plugins - which are built from that services/collectionobjects/3rdparty module - and we can poke around them and let you know what we find. On Wed, Aug 24, 2011 at 3:14 PM, Joe Slag <joe@slagwerks.com> wrote: > Hey folks, > > Looks like I've run into a tenant-specific problem. I've recently > reinstalled CSpace 1.8.3 from the tarballs, and followed the > directions at http://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant+using+the+mini-build > to create our tenant. So far I've made modifications to > bunde/core-message.properties, and html/pages/CatalogingTemplate.html, > both of which have worked as I'd hoped. > > What I'm running into right now is an inability to create catalog > objects, either with my modified template (hid a few fields) or even > after copying back the version in > tenant-customizations-v1.8/ui/defaults/html/pages and redeploying. > I've also restarted the cspace server in case the quick deploy was to > blame. Regardless, when I try to create a catalog object I get an > error in the UI such as this: > >  URL:http://localhost:8180/cspace-services/collectionobjects/: > STATUS:400:Create request failed: > org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not > found: dublincore:title. Document > '/wac-domain/workspaces/CollectionObjects/e1a269b2-5551-4c94-84af' > with title 'e1a269b2-5551-4c94-84af' and type 'CollectionObject' does > not have any schema with prefix 'dublincore' > > I'm not seeing this problem in the lifesci tenant, which I've made no > changes to. > > Does this error give anyone ideas about what might be going on? Debugging tips? > > thanks, > Joe > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

       <!-- Insert the four new lines here -->
        <schema name="common"/>
        <schema name="dublincore"/>
        <schema name="collectionspace_core"/>
        <schema name="collectionobjects_common"/>

        <prefetch>
            collectionobjects_common:objectNumber
            collectionobjects_common:objectNameList
            collectionobjects_common:responsibleDepartments
		</prefetch>
    </doctype>
</extension>

Hi Joe, > What I'm running into right now is an inability to create catalog > objects, either with my modified template (hid a few fields) or even > after copying back the version in tenant-customizations-v1.8/ui/defaults/html/pages > and redeploying. .... when I try to create a catalog object I get an > error in the UI such as this: > > ... Create request failed: > org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not > found: dublincore:title. Document Thanks, Joe, for your detailed error reports and artifacts from your system - they're much appreciated! Richard and I traced this through the code with an unmodified stack from the v1.8.3 tarballs, and were able to reproduce the exact behavior / error message you've been seeing. It appears you ran into an unfortunate edge case where this error will occur if both of these conditions apply: * In version 1.8.2 (and perhaps any 1.8.x) of the services layer. * When you create a new tenant in the services layer ... ** ... that doesn't extend CollectionObject with a custom schema. This appears to be an artifact of in-process services work, initiated in v1.8, that makes it possible to create a document type (such as a CollectionObject composed of a unique set of common and extension schemas) that is specific to a tenant, rather than shared between tenants. This issue is also specific in v1.8 to CollectionObject; you would not see it with any other record type. In v1.9, this issue is resolved. >From what I understand, you should be able to resolve the problem by adding four lines to a single file in the services source code tree for v1.8.2, and building and deploying that change to your CollectionSpace server. (You'll note that this fix is related to an observation / question you had during our earlier correspondence.) Details appear below. If I possibly can, I'll test these instructions here as well and make certain that they resolve the error; your own results would also be appreciated. Aron -- Edit this file in the services source code tree (e.g. within the source code you've downloaded from https://source.collectionspace.org/collection-space/src/services/tags/v1.8.2) services/collectionobject/3rdparty/nuxeo-platform-collectionobjects_common/src/main/resources/OSGI-INF/core-types-contrib.xml To add these four lines as shown below: <schema name="common"/> <schema name="dublincore"/> <schema name="collectionspace_core"/> <schema name="collectionobjects_common"/> -------- Before -------- <?xml version="1.0"?> <component name="org.collectionspace.collectionobject.coreTypes"> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="schema"> <schema name="collectionobjects_common" prefix="collectionobjects_common" src="schemas/collectionobjects_common.xsd"/> </extension> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="doctype"> <doctype name="CollectionObject" extends="CollectionSpaceDocument"> <prefetch> collectionobjects_common:objectNumber collectionobjects_common:objectNameList collectionobjects_common:responsibleDepartments </prefetch> </doctype> </extension> </component> -------- After -------- <?xml version="1.0"?> <component name="org.collectionspace.collectionobject.coreTypes"> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="schema"> <schema name="collectionobjects_common" prefix="collectionobjects_common" src="schemas/collectionobjects_common.xsd"/> </extension> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="doctype"> <doctype name="CollectionObject" extends="CollectionSpaceDocument"> <!-- Insert the four new lines here --> <schema name="common"/> <schema name="dublincore"/> <schema name="collectionspace_core"/> <schema name="collectionobjects_common"/> <prefetch> collectionobjects_common:objectNumber collectionobjects_common:objectNameList collectionobjects_common:responsibleDepartments </prefetch> </doctype> </extension> </component> Then: * Shut down both servers, if they are running. * Within services/collectionobject/3rdparty/nuxeo-platform-collectionobjects_common: * Type: mvn clean install * Type: ant undeploy deploy * Start both servers. --- On Wed, Aug 24, 2011 at 3:14 PM, Joe Slag <joe@slagwerks.com> wrote: > Hey folks, > > Looks like I've run into a tenant-specific problem. I've recently > reinstalled CSpace 1.8.3 from the tarballs, and followed the > directions at http://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant+using+the+mini-build > to create our tenant. So far I've made modifications to > bunde/core-message.properties, and html/pages/CatalogingTemplate.html, > both of which have worked as I'd hoped. > > What I'm running into right now is an inability to create catalog > objects, either with my modified template (hid a few fields) or even > after copying back the version in > tenant-customizations-v1.8/ui/defaults/html/pages and redeploying. > I've also restarted the cspace server in case the quick deploy was to > blame. Regardless, when I try to create a catalog object I get an > error in the UI such as this: > >  URL:http://localhost:8180/cspace-services/collectionobjects/: > STATUS:400:Create request failed: > org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not > found: dublincore:title. Document > '/wac-domain/workspaces/CollectionObjects/e1a269b2-5551-4c94-84af' > with title 'e1a269b2-5551-4c94-84af' and type 'CollectionObject' does > not have any schema with prefix 'dublincore' > > I'm not seeing this problem in the lifesci tenant, which I've made no > changes to. > > Does this error give anyone ideas about what might be going on? Debugging tips? > > thanks, > Joe > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

      <!-- Insert the four new lines here -->
       <schema name="common"/>
       <schema name="dublincore"/>
       <schema name="collectionspace_core"/>
       <schema name="collectionobjects_common"/>

       <prefetch>
           collectionobjects_common:objectNumber
           collectionobjects_common:objectNameList
           collectionobjects_common:responsibleDepartments
                   </prefetch>
   </doctype>

On Thu, Sep 1, 2011 at 2:24 PM, Aron Roberts <aronroberts@gmail.com> wrote: > Details appear below.  If I possibly can, I'll test these instructions > here as well and make certain that they resolve the error; your own > results would also be appreciated. The instructions below have been tested and do resolve the "Property not found: dublincore:title" issue in v1.8.3. Aron -- Edit this file in the services source code tree (e.g. within the source code you've downloaded from https://source.collectionspace.org/collection-space/src/services/tags/v1.8.2) services/collectionobject/3rdparty/nuxeo-platform-collectionobjects_common/src/main/resources/OSGI-INF/core-types-contrib.xml To add these four lines as shown below: <schema name="common"/> <schema name="dublincore"/> <schema name="collectionspace_core"/> <schema name="collectionobjects_common"/> -------- Before -------- <?xml version="1.0"?> <component name="org.collectionspace.collectionobject.coreTypes"> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="schema"> <schema name="collectionobjects_common" prefix="collectionobjects_common" src="schemas/collectionobjects_common.xsd"/> </extension> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="doctype"> <doctype name="CollectionObject" extends="CollectionSpaceDocument"> <prefetch> collectionobjects_common:objectNumber collectionobjects_common:objectNameList collectionobjects_common:responsibleDepartments </prefetch> </doctype> </extension> </component> -------- After -------- <?xml version="1.0"?> <component name="org.collectionspace.collectionobject.coreTypes"> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="schema"> <schema name="collectionobjects_common" prefix="collectionobjects_common" src="schemas/collectionobjects_common.xsd"/> </extension> <extension target="org.nuxeo.ecm.core.schema.TypeService" point="doctype"> <doctype name="CollectionObject" extends="CollectionSpaceDocument"> <!-- Insert the four new lines here --> <schema name="common"/> <schema name="dublincore"/> <schema name="collectionspace_core"/> <schema name="collectionobjects_common"/> <prefetch> collectionobjects_common:objectNumber collectionobjects_common:objectNameList collectionobjects_common:responsibleDepartments </prefetch> </doctype> </extension> </component> Then: * Shut down both servers, if they are running. * Within services/collectionobject/3rdparty/nuxeo-platform-collectionobjects_common: * Type: mvn clean install * Type: ant undeploy deploy * Start both servers.