Thanks for clarifying the tenant-bindings situation.
Now that I get on to the second point of your message, I see that you've
found the problem. My pass at the schema modification in 1.7 was missing the
"section" attributes on the fields I added. Now that I've put them in,
everything's working!
As always, appreciate the debugging tips.
On Tue, Jun 7, 2011 at 9:37 PM, Aron Roberts aron@socrates.berkeley.eduwrote:
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?
Thanks for clarifying the tenant-bindings situation.
Now that I get on to the second point of your message, I see that you've
found the problem. My pass at the schema modification in 1.7 was missing the
"section" attributes on the fields I added. Now that I've put them in,
everything's working!
As always, appreciate the debugging tips.
- Joe
On Tue, Jun 7, 2011 at 9:37 PM, Aron Roberts <aron@socrates.berkeley.edu>wrote:
> . . .
> - 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?
>>
>
