I've upgraded our CSpace installation to 1.7 and have been revisiting the schema modification process. However, what was working under 1.6 isn't totally working now, so I thought I'd ask if anything relevant had changed. The service side of my changes is working, and my new fields show up when I request collectionspace/chain/cataloging/uischema and /uispec. However, entering data in the web UI isn't working; when I click 'save' the fields empty out. I have verified that my cspace-config.xml changes don't have the bug I had last time around. Anything else to check for? cheers, Joe

Hi Joe, For starters, you might verify that the payload that the UI is sending to the app layer include your custom fields and their values. This document generally discusses how you might do this: <http://wiki.collectionspace.org/display/collectionspace/Guidelines+for+Bug+Triage> Aron In the message "[Talk] Any 1.6 -> 1.7 changes that might have affected sche", dated 2011-06-07, Joe Slag wrote: >I've upgraded our CSpace installation to 1.7 and have been revisiting >the schema modification process. However, what was working under 1.6 >isn't totally working now, so I thought I'd ask if anything relevant had >changed. > >The service side of my changes is working, and my new fields show up >when I request collectionspace/chain/cataloging/uischema and /uispec. >However, entering data in the web UI isn't working; when I click 'save' >the fields empty out. > >I have verified that my cspace-config.xml changes don't have the bug I >had last time around. Anything else to check for? > >cheers, >Joe > >_______________________________________________ >Talk mailing list >Talk@lists.collectionspace.org >http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

 where individual fields in the CollectionObject / Cataloging
 record that are only present in the custom 'naturalhistory'
 schema are specified like this, with a 'section="naturalhistory"'
 attribute:

 <field id="reference" section="naturalhistory">

 and that 'naturalhistory' identifier is defined near the top
 of default.xml in this way:

Hi Joe, A couple more things that might possibly have differed between 1.6 and 1.7, and may not yet be updated in the documentation on how to add custom fields; these are likely documented elsewhere: - You can now maintain a very sparse tenant bindings file, for your tenant. In that file, you only need to include any settings for your tenant that differ from the prototype (default) settings. All other configuration is picked up from a prototype file. You can see an example of this - the addition of a custom part (in this case, part 3) to CollectionObject / Cataloging records, with its own namespace and schema, for a specific tenant, in: <https://source.collectionspace.org/collection-space/src/services/trunk/services/common/src/main/cspace/config/services/tenants/hearstmuseum/tenant-bindings.delta.xml> - The app layer configuration (default.xml) uses a 'section' attribute, from what I recall, to specify fields that are present only in a custom schema. I don't know whether this differs from 1.6, but am mentioning this here just in case ... You can see an example of this in: <http://fisheye.collectionspace.org/browse/~br%3DUCJEPS/collectionspace/src/application/branches/UCJEPS/tomcat-main/src/main/resources/default.xml?r1=4794&r2=4870&ignore=w> where individual fields in the CollectionObject / Cataloging record that are only present in the custom 'naturalhistory' schema are specified like this, with a 'section="naturalhistory"' attribute: <field id="reference" section="naturalhistory"> and that 'naturalhistory' identifier is defined near the top of default.xml in this way: <services-record-path id="naturalhistory">collectionobjects_naturalhistory:http://collectionspace.org/services/collectionobject/domain/naturalhistory,collectionobjects_naturalhistory</services-record-path> Aron In the message "[Talk] Any 1.6 -> 1.7 changes that might have affected sche", dated 2011-06-07, Joe Slag wrote: >I've upgraded our CSpace installation to 1.7 and have been revisiting >the schema modification process. However, what was working under 1.6 >isn't totally working now, so I thought I'd ask if anything relevant had >changed. > >The service side of my changes is working, and my new fields show up >when I request collectionspace/chain/cataloging/uischema and /uispec. >However, entering data in the web UI isn't working; when I click 'save' >the fields empty out. > >I have verified that my cspace-config.xml changes don't have the bug I >had last time around. Anything else to check for?