Hi, Does anyone know if I can use the REST api for person (for example) to update a person record by adding the URI to the collectionspace_core schema? I just sent this payload to a server (ucjeps.cspace): > <?xml version="1.0" encoding="UTF-8"?> > <document name="persons"> > <ns2:collectionspace_core xmlns:ns2="http://collectionspace.org/collectionspace_core/"> > <uri>/personauthorities/492326d1-efb1-4d2b-96d9/items/d97fdc83-95fc-4ce7-b8a2-d313d050c5da</uri> > </ns2:collectionspace_core> > <ns2:persons_common xmlns:ns2="http://collectionspace.org/services/person"> > <nameNote></nameNote> > <displayName>Aaron I. Liston</displayName> > </ns2:persons_common> > </document> The nameNote updated (from Collector to nothing), but the URI was not inserted. I guess I could write a SQL job to do this. Thanks, Chris

Chris, In the REST API, I don't believe the fields in the collectionspace_core part are client-editable. Yes, a SQL script is an option instead. Is this an attempted workaround for http://issues.collectionspace.org/browse/CSPACE-5012? Aron On Wed, May 16, 2012 at 8:38 PM, Chris Hoffman <chris.hoffman@berkeley.edu> wrote: > Hi, > > Does anyone know if I can use the REST api for person (for example) to > update a person record by adding the URI to the collectionspace_core schema? >  I just sent this payload to a server (ucjeps.cspace): > > <?xml version="1.0" encoding="UTF-8"?> > <document name="persons"> >     <ns2:collectionspace_core > xmlns:ns2="http://collectionspace.org/collectionspace_core/"> > > <uri>/personauthorities/492326d1-efb1-4d2b-96d9/items/d97fdc83-95fc-4ce7-b8a2-d313d050c5da</uri> >     </ns2:collectionspace_core> >     <ns2:persons_common > xmlns:ns2="http://collectionspace.org/services/person"> >         <nameNote></nameNote> >         <displayName>Aaron I. Liston</displayName> >     </ns2:persons_common> > </document> > > > The nameNote updated (from Collector to nothing), but the URI was not > inserted.  I guess I could write a SQL job to do this. > > Thanks, > Chris > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

Thanks, Aron. Yes, this is because the import service is not populating the URI. Chris On May 16, 2012, at 9:34 PM, Aron Roberts wrote: > Chris, > > In the REST API, I don't believe the fields in the > collectionspace_core part are client-editable. Yes, a SQL script is > an option instead. > > Is this an attempted workaround for > http://issues.collectionspace.org/browse/CSPACE-5012? > > Aron > > On Wed, May 16, 2012 at 8:38 PM, Chris Hoffman > <chris.hoffman@berkeley.edu> wrote: >> Hi, >> >> Does anyone know if I can use the REST api for person (for example) to >> update a person record by adding the URI to the collectionspace_core schema? >> I just sent this payload to a server (ucjeps.cspace): >> >> <?xml version="1.0" encoding="UTF-8"?> >> <document name="persons"> >> <ns2:collectionspace_core >> xmlns:ns2="http://collectionspace.org/collectionspace_core/"> >> >> <uri>/personauthorities/492326d1-efb1-4d2b-96d9/items/d97fdc83-95fc-4ce7-b8a2-d313d050c5da</uri> >> </ns2:collectionspace_core> >> <ns2:persons_common >> xmlns:ns2="http://collectionspace.org/services/person"> >> <nameNote></nameNote> >> <displayName>Aaron I. Liston</displayName> >> </ns2:persons_common> >> </document> >> >> >> The nameNote updated (from Collector to nothing), but the URI was not >> inserted. I guess I could write a SQL job to do this. >> >> Thanks, >> Chris >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>

Can someone tell us what we are supposed to do about CSPACE-5012 and imports, assuming it is still a problem in 2.4? I don't think we should have to fix these in SQL, since we have been discouraged from doing such things. Should this be considered a blocker and fixed/patched right away? Susan > Thanks, Aron. Yes, this is because the import service is not populating > the URI. > Chris > > > On May 16, 2012, at 9:34 PM, Aron Roberts wrote: > >> Chris, >> >> In the REST API, I don't believe the fields in the >> collectionspace_core part are client-editable. Yes, a SQL script is >> an option instead. >> >> Is this an attempted workaround for >> http://issues.collectionspace.org/browse/CSPACE-5012? >> >> Aron >> >> On Wed, May 16, 2012 at 8:38 PM, Chris Hoffman >> <chris.hoffman@berkeley.edu> wrote: >>> Hi, >>> >>> Does anyone know if I can use the REST api for person (for example) to >>> update a person record by adding the URI to the collectionspace_core >>> schema? >>> I just sent this payload to a server (ucjeps.cspace): >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <document name="persons"> >>> <ns2:collectionspace_core >>> xmlns:ns2="http://collectionspace.org/collectionspace_core/"> >>> >>> <uri>/personauthorities/492326d1-efb1-4d2b-96d9/items/d97fdc83-95fc-4ce7-b8a2-d313d050c5da</uri> >>> </ns2:collectionspace_core> >>> <ns2:persons_common >>> xmlns:ns2="http://collectionspace.org/services/person"> >>> <nameNote></nameNote> >>> <displayName>Aaron I. Liston</displayName> >>> </ns2:persons_common> >>> </document> >>> >>> >>> The nameNote updated (from Collector to nothing), but the URI was not >>> inserted. I guess I could write a SQL job to do this. >>> >>> Thanks, >>> Chris >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

I've gone ahead and unilaterally made http://issues.collectionspace.org/browse/CSPACE-5012 a v2.4 blocker. This is becoming a huge pain point for our implementers when importing data. Please note that "right away" fix may *potentially* be a hack that will need to be replaced by a new blocker for v2.5, to replace the hack by better designed and more maintainable code. I'm going to suggest this issue can worked on during the QA period, as AFAIK, we don't have any QA test plans for the Imports service (?) and thus changes to that service shouldn't impact QA testing. Also, this just involves an addition of a new value to the collectionspace_core part, so the likelihood that it will break something or cause any other regression is quite small, as long as we handle errors sensibly. I'm presuming that we can have support for testing any fix from Susan, Chris H. and others? On Thu, May 17, 2012 at 8:21 AM, <sstone@socrates.berkeley.edu> wrote: > Can someone tell us what we are supposed to do about CSPACE-5012 and > imports, assuming it is still a problem in 2.4? I don't think we should > have to fix these in SQL, since we have been discouraged from doing such > things. Should this be considered a blocker and fixed/patched right away? > > Susan > > >> Thanks, Aron.  Yes, this is because the import service is not populating >> the URI. >> Chris >> >> >> On May 16, 2012, at 9:34 PM, Aron Roberts wrote: >> >>> Chris, >>> >>>  In the REST API, I don't believe the fields in the >>> collectionspace_core part are client-editable.  Yes, a SQL script is >>> an option instead. >>> >>>  Is this an attempted workaround for >>> http://issues.collectionspace.org/browse/CSPACE-5012? >>> >>> Aron >>> >>> On Wed, May 16, 2012 at 8:38 PM, Chris Hoffman >>> <chris.hoffman@berkeley.edu> wrote: >>>> Hi, >>>> >>>> Does anyone know if I can use the REST api for person (for example) to >>>> update a person record by adding the URI to the collectionspace_core >>>> schema? >>>>  I just sent this payload to a server (ucjeps.cspace): >>>> >>>> <?xml version="1.0" encoding="UTF-8"?> >>>> <document name="persons"> >>>>     <ns2:collectionspace_core >>>> xmlns:ns2="http://collectionspace.org/collectionspace_core/"> >>>> >>>> <uri>/personauthorities/492326d1-efb1-4d2b-96d9/items/d97fdc83-95fc-4ce7-b8a2-d313d050c5da</uri> >>>>     </ns2:collectionspace_core> >>>>     <ns2:persons_common >>>> xmlns:ns2="http://collectionspace.org/services/person"> >>>>         <nameNote></nameNote> >>>>         <displayName>Aaron I. Liston</displayName> >>>>     </ns2:persons_common> >>>> </document> >>>> >>>> >>>> The nameNote updated (from Collector to nothing), but the URI was not >>>> inserted.  I guess I could write a SQL job to do this. >>>> >>>> Thanks, >>>> Chris >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > >

Thanks, Aron, yes we'll help testing. Even if this is available as a patch on 2.4, it will help a lot. Chris On May 17, 2012, at 8:44 AM, Aron Roberts wrote: > I've gone ahead and unilaterally made > http://issues.collectionspace.org/browse/CSPACE-5012 a v2.4 blocker. > This is becoming a huge pain point for our implementers when importing > data. Please note that "right away" fix may *potentially* be a hack > that will need to be replaced by a new blocker for v2.5, to replace > the hack by better designed and more maintainable code. > > I'm going to suggest this issue can worked on during the QA period, as > AFAIK, we don't have any QA test plans for the Imports service (?) and > thus changes to that service shouldn't impact QA testing. Also, this > just involves an addition of a new value to the collectionspace_core > part, so the likelihood that it will break something or cause any > other regression is quite small, as long as we handle errors sensibly. > > I'm presuming that we can have support for testing any fix from Susan, > Chris H. and others? > > On Thu, May 17, 2012 at 8:21 AM, <sstone@socrates.berkeley.edu> wrote: >> Can someone tell us what we are supposed to do about CSPACE-5012 and >> imports, assuming it is still a problem in 2.4? I don't think we should >> have to fix these in SQL, since we have been discouraged from doing such >> things. Should this be considered a blocker and fixed/patched right away? >> >> Susan >> >> >>> Thanks, Aron. Yes, this is because the import service is not populating >>> the URI. >>> Chris >>> >>> >>> On May 16, 2012, at 9:34 PM, Aron Roberts wrote: >>> >>>> Chris, >>>> >>>> In the REST API, I don't believe the fields in the >>>> collectionspace_core part are client-editable. Yes, a SQL script is >>>> an option instead. >>>> >>>> Is this an attempted workaround for >>>> http://issues.collectionspace.org/browse/CSPACE-5012? >>>> >>>> Aron >>>> >>>> On Wed, May 16, 2012 at 8:38 PM, Chris Hoffman >>>> <chris.hoffman@berkeley.edu> wrote: >>>>> Hi, >>>>> >>>>> Does anyone know if I can use the REST api for person (for example) to >>>>> update a person record by adding the URI to the collectionspace_core >>>>> schema? >>>>> I just sent this payload to a server (ucjeps.cspace): >>>>> >>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>> <document name="persons"> >>>>> <ns2:collectionspace_core >>>>> xmlns:ns2="http://collectionspace.org/collectionspace_core/"> >>>>> >>>>> <uri>/personauthorities/492326d1-efb1-4d2b-96d9/items/d97fdc83-95fc-4ce7-b8a2-d313d050c5da</uri> >>>>> </ns2:collectionspace_core> >>>>> <ns2:persons_common >>>>> xmlns:ns2="http://collectionspace.org/services/person"> >>>>> <nameNote></nameNote> >>>>> <displayName>Aaron I. Liston</displayName> >>>>> </ns2:persons_common> >>>>> </document> >>>>> >>>>> >>>>> The nameNote updated (from Collector to nothing), but the URI was not >>>>> inserted. I guess I could write a SQL job to do this. >>>>> >>>>> Thanks, >>>>> Chris >>>>> >>>>> _______________________________________________ >>>>> Talk mailing list >>>>> Talk@lists.collectionspace.org >>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>>> >>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> >>

Really appreciate this, Aron. It's OK with me if it is an ugly hack underneath, as long as it doesn't break anything else. I can help test after next Tuesday, since I am out of town and not able to work before that (but checking email and making trouble, as you see). Susan > I've gone ahead and unilaterally made > http://issues.collectionspace.org/browse/CSPACE-5012 a v2.4 blocker. > This is becoming a huge pain point for our implementers when importing > data. Please note that "right away" fix may *potentially* be a hack > that will need to be replaced by a new blocker for v2.5, to replace > the hack by better designed and more maintainable code. > > I'm going to suggest this issue can worked on during the QA period, as > AFAIK, we don't have any QA test plans for the Imports service (?) and > thus changes to that service shouldn't impact QA testing. Also, this > just involves an addition of a new value to the collectionspace_core > part, so the likelihood that it will break something or cause any > other regression is quite small, as long as we handle errors sensibly. > > I'm presuming that we can have support for testing any fix from Susan, > Chris H. and others? > > On Thu, May 17, 2012 at 8:21 AM, <sstone@socrates.berkeley.edu> wrote: >> Can someone tell us what we are supposed to do about CSPACE-5012 and >> imports, assuming it is still a problem in 2.4? I don't think we should >> have to fix these in SQL, since we have been discouraged from doing such >> things. Should this be considered a blocker and fixed/patched right >> away? >> >> Susan >> >> >>> Thanks, Aron.  Yes, this is because the import service is not >>> populating >>> the URI. >>> Chris >>> >>> >>> On May 16, 2012, at 9:34 PM, Aron Roberts wrote: >>> >>>> Chris, >>>> >>>>  In the REST API, I don't believe the fields in the >>>> collectionspace_core part are client-editable.  Yes, a SQL script is >>>> an option instead. >>>> >>>>  Is this an attempted workaround for >>>> http://issues.collectionspace.org/browse/CSPACE-5012? >>>> >>>> Aron >>>> >>>> On Wed, May 16, 2012 at 8:38 PM, Chris Hoffman >>>> <chris.hoffman@berkeley.edu> wrote: >>>>> Hi, >>>>> >>>>> Does anyone know if I can use the REST api for person (for example) >>>>> to >>>>> update a person record by adding the URI to the collectionspace_core >>>>> schema? >>>>>  I just sent this payload to a server (ucjeps.cspace): >>>>> >>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>> <document name="persons"> >>>>>     <ns2:collectionspace_core >>>>> xmlns:ns2="http://collectionspace.org/collectionspace_core/"> >>>>> >>>>> <uri>/personauthorities/492326d1-efb1-4d2b-96d9/items/d97fdc83-95fc-4ce7-b8a2-d313d050c5da</uri> >>>>>     </ns2:collectionspace_core> >>>>>     <ns2:persons_common >>>>> xmlns:ns2="http://collectionspace.org/services/person"> >>>>>         <nameNote></nameNote> >>>>>         <displayName>Aaron I. Liston</displayName> >>>>>     </ns2:persons_common> >>>>> </document> >>>>> >>>>> >>>>> The nameNote updated (from Collector to nothing), but the URI was not >>>>> inserted.  I guess I could write a SQL job to do this. >>>>> >>>>> Thanks, >>>>> Chris >>>>> >>>>> _______________________________________________ >>>>> Talk mailing list >>>>> Talk@lists.collectionspace.org >>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>>> >>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> >> >

Thanks, Chris! This almost certainly will lend itself to being a patch that can be applied to v2.4, if for any reason this doesn't get into 2.4. On Thu, May 17, 2012 at 8:55 AM, Chris Hoffman <chris.hoffman@berkeley.edu> wrote: > Thanks, Aron, yes we'll help testing.  Even if this is available as a patch on 2.4, it will help a lot. > Chris > > > On May 17, 2012, at 8:44 AM, Aron Roberts wrote: > >> I've gone ahead and unilaterally made >> http://issues.collectionspace.org/browse/CSPACE-5012 a v2.4 blocker. >> This is becoming a huge pain point for our implementers when importing >> data.  Please note that "right away" fix may *potentially* be a hack >> that will need to be replaced by a new blocker for v2.5, to replace >> the hack by better designed and more maintainable code. >> >> I'm going to suggest this issue can worked on during the QA period, as >> AFAIK, we don't have any QA test plans for the Imports service (?) and >> thus changes to that service shouldn't impact QA testing.  Also, this >> just involves an addition of a new value to the collectionspace_core >> part, so the likelihood that it will break something or cause any >> other regression is quite small, as long as we handle errors sensibly. >> >> I'm presuming that we can have support for testing any fix from Susan, >> Chris H. and others? >> >> On Thu, May 17, 2012 at 8:21 AM,  <sstone@socrates.berkeley.edu> wrote: >>> Can someone tell us what we are supposed to do about CSPACE-5012 and >>> imports, assuming it is still a problem in 2.4? I don't think we should >>> have to fix these in SQL, since we have been discouraged from doing such >>> things. Should this be considered a blocker and fixed/patched right away? >>> >>> Susan >>> >>> >>>> Thanks, Aron.  Yes, this is because the import service is not populating >>>> the URI. >>>> Chris >>>> >>>> >>>> On May 16, 2012, at 9:34 PM, Aron Roberts wrote: >>>> >>>>> Chris, >>>>> >>>>>  In the REST API, I don't believe the fields in the >>>>> collectionspace_core part are client-editable.  Yes, a SQL script is >>>>> an option instead. >>>>> >>>>>  Is this an attempted workaround for >>>>> http://issues.collectionspace.org/browse/CSPACE-5012? >>>>> >>>>> Aron >>>>> >>>>> On Wed, May 16, 2012 at 8:38 PM, Chris Hoffman >>>>> <chris.hoffman@berkeley.edu> wrote: >>>>>> Hi, >>>>>> >>>>>> Does anyone know if I can use the REST api for person (for example) to >>>>>> update a person record by adding the URI to the collectionspace_core >>>>>> schema? >>>>>>  I just sent this payload to a server (ucjeps.cspace): >>>>>> >>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>> <document name="persons"> >>>>>>     <ns2:collectionspace_core >>>>>> xmlns:ns2="http://collectionspace.org/collectionspace_core/"> >>>>>> >>>>>> <uri>/personauthorities/492326d1-efb1-4d2b-96d9/items/d97fdc83-95fc-4ce7-b8a2-d313d050c5da</uri> >>>>>>     </ns2:collectionspace_core> >>>>>>     <ns2:persons_common >>>>>> xmlns:ns2="http://collectionspace.org/services/person"> >>>>>>         <nameNote></nameNote> >>>>>>         <displayName>Aaron I. Liston</displayName> >>>>>>     </ns2:persons_common> >>>>>> </document> >>>>>> >>>>>> >>>>>> The nameNote updated (from Collector to nothing), but the URI was not >>>>>> inserted.  I guess I could write a SQL job to do this. >>>>>> >>>>>> Thanks, >>>>>> Chris >>>>>> >>>>>> _______________________________________________ >>>>>> Talk mailing list >>>>>> Talk@lists.collectionspace.org >>>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>>>> >>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>> >>> >