CP
Christopher Pott
Thu, May 16, 2013 8:45 AM
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can't import data to boolean fields. Whatever value I provide ("true", "yes", "1"), the field is populated with "false". I'm not certain if this is a new issue, but I've a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the "true" value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = "verso" type ="xs:boolean" />
Cheers,
Chris
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can't import data to boolean fields. Whatever value I provide ("true", "yes", "1"), the field is populated with "false". I'm not certain if this is a new issue, but I've a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the "true" value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = "verso" type ="xs:boolean" />
Cheers,
Chris
CH
Chris Hoffman
Thu, May 16, 2013 4:35 PM
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can’t import data to boolean fields. Whatever value I provide (“true”, “yes”, “1”), the field is populated with “false”. I’m not certain if this is a new issue, but I’ve a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the “true” value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = “verso” type =”xs:boolean” />
Cheers,
Chris
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
> Hi,
>
> Using the imports service (CS version 3.2.1 plus local extensions) I can’t import data to boolean fields. Whatever value I provide (“true”, “yes”, “1”), the field is populated with “false”. I’m not certain if this is a new issue, but I’ve a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
>
> Otherwise, the field appears to work fine, is visible in the database (type bool), and the “true” value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
>
> The field is defined in our extension to the cataloging schema like this:
> <xs:element name = “verso” type =”xs:boolean” />
>
> Cheers,
> Chris
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
CP
Christopher Pott
Thu, May 16, 2013 6:41 PM
Hi Chris,
I've attached an example import record. The import suceeds, but the <smkVerso> value is false in the database. In the service definition smkVerso is defined as <xs:element name = "smkVerso" type ="xs:boolean"/> (not "verso" as in the earlier example I provided). I will also look into testing the core schema as you suggest.
Thanks,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.org List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can't import data to boolean fields. Whatever value I provide ("true", "yes", "1"), the field is populated with "false". I'm not certain if this is a new issue, but I've a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the "true" value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = "verso" type ="xs:boolean" />
Cheers,
Chris
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Chris,
I've attached an example import record. The import suceeds, but the <smkVerso> value is false in the database. In the service definition smkVerso is defined as <xs:element name = "smkVerso" type ="xs:boolean"/> (not "verso" as in the earlier example I provided). I will also look into testing the core schema as you suggest.
Thanks,
Chris
________________________________
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.org List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can't import data to boolean fields. Whatever value I provide ("true", "yes", "1"), the field is populated with "false". I'm not certain if this is a new issue, but I've a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the "true" value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = "verso" type ="xs:boolean" />
Cheers,
Chris
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org>
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
CH
Chris Hoffman
Thu, May 16, 2013 11:46 PM
Hi Chris,
I took a quick look at your sample file, and the particular element looks fine, and the overall layout looks fine too. We're using "true" and "false" like you are. There must be something else going on, either with the schema extension or with the import service itself. Hopefully others on the list will have some ideas.
By the way, I really liked seeing your fine arts extension! I'll get in touch separately about borrowing that. By the way, do you have your customized code up in github or another repository?
Thanks,
Chris
On May 16, 2013, at 11:41 AM, Christopher Pott wrote:
Hi Chris,
I've attached an example import record. The import suceeds, but the <smkVerso> value is false in the database. In the service definition smkVerso is defined as <xs:element name = "smkVerso" type ="xs:boolean"/> (not "verso" as in the earlier example I provided). I will also look into testing the core schema as you suggest.
Thanks,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.org List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can’t import data to boolean fields. Whatever value I provide (“true”, “yes”, “1”), the field is populated with “false”. I’m not certain if this is a new issue, but I’ve a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the “true” value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = “verso” type =”xs:boolean” />
Cheers,
Chris
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Chris,
I took a quick look at your sample file, and the particular element looks fine, and the overall layout looks fine too. We're using "true" and "false" like you are. There must be something else going on, either with the schema extension or with the import service itself. Hopefully others on the list will have some ideas.
By the way, I really liked seeing your fine arts extension! I'll get in touch separately about borrowing that. By the way, do you have your customized code up in github or another repository?
Thanks,
Chris
On May 16, 2013, at 11:41 AM, Christopher Pott wrote:
> Hi Chris,
>
> I've attached an example import record. The import suceeds, but the <smkVerso> value is false in the database. In the service definition smkVerso is defined as <xs:element name = "smkVerso" type ="xs:boolean"/> (not "verso" as in the earlier example I provided). I will also look into testing the core schema as you suggest.
>
> Thanks,
> Chris
>
> Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
> Sendt: 16. maj 2013 18:35
> Til: Christopher Pott
> Cc: talk@lists.collectionspace.org List
> Emne: Re: [Talk] importing booleans
>
> Hi Chris,
> Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
> Chris
>
>
> On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
>
>> Hi,
>> Using the imports service (CS version 3.2.1 plus local extensions) I can’t import data to boolean fields. Whatever value I provide (“true”, “yes”, “1”), the field is populated with “false”. I’m not certain if this is a new issue, but I’ve a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
>> Otherwise, the field appears to work fine, is visible in the database (type bool), and the “true” value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
>> The field is defined in our extension to the cataloging schema like this:
>> <xs:element name = “verso” type =”xs:boolean” />
>> Cheers,
>> Chris
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
> <testboolimport.xml>
CP
Christopher Pott
Fri, May 17, 2013 7:33 AM
Hi Chris,
Our extensions are currently in Bitbucket, but will shortly be moving to SMK's new Github account. There are still some outstanding issues but this more or less represents the system we will use for our first deployment this summer. If you'd like to see it, you can fetch the current code here ('corpus' is the name of our project :)
https://bitbucket.org/christopher_pott/corpus_ui
https://bitbucket.org/christopher_pott/corpus_services
https://bitbucket.org/christopher_pott/corpus_application
Warning: the UI is in Danish and while you could just delete our texts overlay, I think you'd be missing definitions for for the fine arts and local extensions. However this wouldn't require a knowledge of Danish to figure out as all of the actual extension schema field definitions are in English.
Cheers,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 17. maj 2013 01:46
Til: Christopher Pott
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] importing booleans
Hi Chris,
I took a quick look at your sample file, and the particular element looks fine, and the overall layout looks fine too. We're using "true" and "false" like you are. There must be something else going on, either with the schema extension or with the import service itself. Hopefully others on the list will have some ideas.
By the way, I really liked seeing your fine arts extension! I'll get in touch separately about borrowing that. By the way, do you have your customized code up in github or another repository?
Thanks,
Chris
On May 16, 2013, at 11:41 AM, Christopher Pott wrote:
Hi Chris,
I've attached an example import record. The import suceeds, but the <smkVerso> value is false in the database. In the service definition smkVerso is defined as <xs:element name = "smkVerso" type ="xs:boolean"/> (not "verso" as in the earlier example I provided). I will also look into testing the core schema as you suggest.
Thanks,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can't import data to boolean fields. Whatever value I provide ("true", "yes", "1"), the field is populated with "false". I'm not certain if this is a new issue, but I've a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the "true" value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = "verso" type ="xs:boolean" />
Cheers,
Chris
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
<testboolimport.xml>
Hi Chris,
Our extensions are currently in Bitbucket, but will shortly be moving to SMK's new Github account. There are still some outstanding issues but this more or less represents the system we will use for our first deployment this summer. If you'd like to see it, you can fetch the current code here ('corpus' is the name of our project :)
https://bitbucket.org/christopher_pott/corpus_ui
https://bitbucket.org/christopher_pott/corpus_services
https://bitbucket.org/christopher_pott/corpus_application
Warning: the UI is in Danish and while you could just delete our texts overlay, I think you'd be missing definitions for for the fine arts and local extensions. However this wouldn't require a knowledge of Danish to figure out as all of the actual extension schema field definitions are in English.
Cheers,
Chris
________________________________
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 17. maj 2013 01:46
Til: Christopher Pott
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] importing booleans
Hi Chris,
I took a quick look at your sample file, and the particular element looks fine, and the overall layout looks fine too. We're using "true" and "false" like you are. There must be something else going on, either with the schema extension or with the import service itself. Hopefully others on the list will have some ideas.
By the way, I really liked seeing your fine arts extension! I'll get in touch separately about borrowing that. By the way, do you have your customized code up in github or another repository?
Thanks,
Chris
On May 16, 2013, at 11:41 AM, Christopher Pott wrote:
Hi Chris,
I've attached an example import record. The import suceeds, but the <smkVerso> value is false in the database. In the service definition smkVerso is defined as <xs:element name = "smkVerso" type ="xs:boolean"/> (not "verso" as in the earlier example I provided). I will also look into testing the core schema as you suggest.
Thanks,
Chris
________________________________
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.org<mailto:talk@lists.collectionspace.org> List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can't import data to boolean fields. Whatever value I provide ("true", "yes", "1"), the field is populated with "false". I'm not certain if this is a new issue, but I've a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the "true" value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = "verso" type ="xs:boolean" />
Cheers,
Chris
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org>
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
<testboolimport.xml>
CH
Chris Hoffman
Fri, May 17, 2013 2:35 PM
Thanks! This is great to see.
Chris
On May 17, 2013, at 12:33 AM, Christopher Pott wrote:
Hi Chris,
Our extensions are currently in Bitbucket, but will shortly be moving to SMK's new Github account. There are still some outstanding issues but this more or less represents the system we will use for our first deployment this summer. If you'd like to see it, you can fetch the current code here ('corpus' is the name of our project :)
https://bitbucket.org/christopher_pott/corpus_ui
https://bitbucket.org/christopher_pott/corpus_services
https://bitbucket.org/christopher_pott/corpus_application
Warning: the UI is in Danish and while you could just delete our texts overlay, I think you'd be missing definitions for for the fine arts and local extensions. However this wouldn't require a knowledge of Danish to figure out as all of the actual extension schema field definitions are in English.
Cheers,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 17. maj 2013 01:46
Til: Christopher Pott
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] importing booleans
Hi Chris,
I took a quick look at your sample file, and the particular element looks fine, and the overall layout looks fine too. We're using "true" and "false" like you are. There must be something else going on, either with the schema extension or with the import service itself. Hopefully others on the list will have some ideas.
By the way, I really liked seeing your fine arts extension! I'll get in touch separately about borrowing that. By the way, do you have your customized code up in github or another repository?
Thanks,
Chris
On May 16, 2013, at 11:41 AM, Christopher Pott wrote:
Hi Chris,
I've attached an example import record. The import suceeds, but the <smkVerso> value is false in the database. In the service definition smkVerso is defined as <xs:element name = "smkVerso" type ="xs:boolean"/> (not "verso" as in the earlier example I provided). I will also look into testing the core schema as you suggest.
Thanks,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.org List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can’t import data to boolean fields. Whatever value I provide (“true”, “yes”, “1”), the field is populated with “false”. I’m not certain if this is a new issue, but I’ve a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the “true” value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = “verso” type =”xs:boolean” />
Cheers,
Chris
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Thanks! This is great to see.
Chris
On May 17, 2013, at 12:33 AM, Christopher Pott wrote:
> Hi Chris,
>
> Our extensions are currently in Bitbucket, but will shortly be moving to SMK's new Github account. There are still some outstanding issues but this more or less represents the system we will use for our first deployment this summer. If you'd like to see it, you can fetch the current code here ('corpus' is the name of our project :)
>
> https://bitbucket.org/christopher_pott/corpus_ui
> https://bitbucket.org/christopher_pott/corpus_services
>
> https://bitbucket.org/christopher_pott/corpus_application
>
> Warning: the UI is in Danish and while you could just delete our texts overlay, I think you'd be missing definitions for for the fine arts and local extensions. However this wouldn't require a knowledge of Danish to figure out as all of the actual extension schema field definitions are in English.
>
> Cheers,
> Chris
>
>
>
> Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
> Sendt: 17. maj 2013 01:46
> Til: Christopher Pott
> Cc: talk@lists.collectionspace.org
> Emne: Re: [Talk] importing booleans
>
> Hi Chris,
>
> I took a quick look at your sample file, and the particular element looks fine, and the overall layout looks fine too. We're using "true" and "false" like you are. There must be something else going on, either with the schema extension or with the import service itself. Hopefully others on the list will have some ideas.
>
> By the way, I really liked seeing your fine arts extension! I'll get in touch separately about borrowing that. By the way, do you have your customized code up in github or another repository?
>
> Thanks,
> Chris
>
>
> On May 16, 2013, at 11:41 AM, Christopher Pott wrote:
>
>> Hi Chris,
>>
>> I've attached an example import record. The import suceeds, but the <smkVerso> value is false in the database. In the service definition smkVerso is defined as <xs:element name = "smkVerso" type ="xs:boolean"/> (not "verso" as in the earlier example I provided). I will also look into testing the core schema as you suggest.
>>
>> Thanks,
>> Chris
>>
>> Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
>> Sendt: 16. maj 2013 18:35
>> Til: Christopher Pott
>> Cc: talk@lists.collectionspace.org List
>> Emne: Re: [Talk] importing booleans
>>
>> Hi Chris,
>> Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
>> Chris
>>
>>
>> On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
>>
>>> Hi,
>>> Using the imports service (CS version 3.2.1 plus local extensions) I can’t import data to boolean fields. Whatever value I provide (“true”, “yes”, “1”), the field is populated with “false”. I’m not certain if this is a new issue, but I’ve a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
>>> Otherwise, the field appears to work fine, is visible in the database (type bool), and the “true” value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
>>> The field is defined in our extension to the cataloging schema like this:
>>> <xs:element name = “verso” type =”xs:boolean” />
>>> Cheers,
>>> Chris
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>
>> <testboolimport.xml>
>
CP
Christopher Pott
Tue, May 21, 2013 11:16 AM
D'oh... I've found what was wrong; the boolean values (some of them at least, such as "smkVerso") were appearing twice in the import, first as 'true' and then again as 'false', the default. Now I just have to work out why (I'm using jaxb to generate the xml and my schema definitions only include these values once). I'll try to recompile my collectionobject jaxb libraries and see if this helps.
Thanks,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.org List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can't import data to boolean fields. Whatever value I provide ("true", "yes", "1"), the field is populated with "false". I'm not certain if this is a new issue, but I've a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the "true" value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = "verso" type ="xs:boolean" />
Cheers,
Chris
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
D'oh... I've found what was wrong; the boolean values (some of them at least, such as "smkVerso") were appearing twice in the import, first as 'true' and then again as 'false', the default. Now I just have to work out why (I'm using jaxb to generate the xml and my schema definitions only include these values once). I'll try to recompile my collectionobject jaxb libraries and see if this helps.
Thanks,
Chris
________________________________
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.org List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can't import data to boolean fields. Whatever value I provide ("true", "yes", "1"), the field is populated with "false". I'm not certain if this is a new issue, but I've a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the "true" value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = "verso" type ="xs:boolean" />
Cheers,
Chris
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org>
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
CH
Chris Hoffman
Tue, May 21, 2013 3:53 PM
Hi Chris,
It is SO easy to make mistakes like that. Believe me, we have felt that pain. Good luck fixing the problem!
Regards,
Chris
On May 21, 2013, at 4:16 AM, Christopher Pott wrote:
D’oh... I’ve found what was wrong; the boolean values (some of them at least, such as “smkVerso”) were appearing twice in the import, first as ‘true’ and then again as ‘false’, the default. Now I just have to work out why (I’m using jaxb to generate the xml and my schema definitions only include these values once). I’ll try to recompile my collectionobject jaxb libraries and see if this helps.
Thanks,
Chris
Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
Sendt: 16. maj 2013 18:35
Til: Christopher Pott
Cc: talk@lists.collectionspace.org List
Emne: Re: [Talk] importing booleans
Hi Chris,
Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
Chris
On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
Hi,
Using the imports service (CS version 3.2.1 plus local extensions) I can’t import data to boolean fields. Whatever value I provide (“true”, “yes”, “1”), the field is populated with “false”. I’m not certain if this is a new issue, but I’ve a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
Otherwise, the field appears to work fine, is visible in the database (type bool), and the “true” value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
The field is defined in our extension to the cataloging schema like this:
<xs:element name = “verso” type =”xs:boolean” />
Cheers,
Chris
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Chris,
It is SO easy to make mistakes like that. Believe me, we have felt that pain. Good luck fixing the problem!
Regards,
Chris
On May 21, 2013, at 4:16 AM, Christopher Pott wrote:
> D’oh... I’ve found what was wrong; the boolean values (some of them at least, such as “smkVerso”) were appearing twice in the import, first as ‘true’ and then again as ‘false’, the default. Now I just have to work out why (I’m using jaxb to generate the xml and my schema definitions only include these values once). I’ll try to recompile my collectionobject jaxb libraries and see if this helps.
>
> Thanks,
> Chris
>
> Fra: Chris Hoffman [mailto:chris_h@berkeley.edu]
> Sendt: 16. maj 2013 18:35
> Til: Christopher Pott
> Cc: talk@lists.collectionspace.org List
> Emne: Re: [Talk] importing booleans
>
> Hi Chris,
> Interesting, we did successfully import into boolean fields that were part of the core schema and into extensions. Have you been able to import into booleans in the core schema? It might be worth trying. Could you send us an example payload you're trying to import? We'd be happy to check it out.
> Chris
>
>
> On May 16, 2013, at 1:45 AM, Christopher Pott wrote:
>
>
> Hi,
>
> Using the imports service (CS version 3.2.1 plus local extensions) I can’t import data to boolean fields. Whatever value I provide (“true”, “yes”, “1”), the field is populated with “false”. I’m not certain if this is a new issue, but I’ve a recollection that this has worked earlier. Does anyone have any hints or experience of this problem or where I could be going wrong?
>
> Otherwise, the field appears to work fine, is visible in the database (type bool), and the “true” value can be successfully set and stored via the collectionspace UI (and hence by the collectionobjects service API).
>
> The field is defined in our extension to the cataloging schema like this:
> <xs:element name = “verso” type =”xs:boolean” />
>
> Cheers,
> Chris
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
