Thanks Bill. I'll use the modifyDatastream operation to update streams.
Smita
From: Bill Branan [mailto:[email protected]]
Sent: Monday, March 09, 2009 10:33 AM
To: Patel, Smita N; Fedora Commons SourceForce Developers
Subject: Re: [Fedora-commons-developers] REST API ingest issue
Yes, the updateObject method only updates the object's properties (state,
owner, label, etc). To update datastreams (like DC) you'll need to call the
modifyDatastream method instead.
Bill
On Mon, Mar 9, 2009 at 10:02 AM, Patel, Smita N
<[email protected]<mailto:[email protected]>> wrote:
Ok. Referring to a prior email that I sent you, I tested for the ingest
operation(REST) where if the object exists an update occurs. This is the test
that I ran. I updated the dc:title field and ingested. It did update the
object, but only with the last updated timestamp. The dc:title field was not
changed. Does this mean that only the object properties can be updated; not the
actual data in the foxml?
Thanks
Smita
From: Bill Branan
[mailto:[email protected]<mailto:[email protected]>]
Sent: Monday, March 09, 2009 9:52 AM
To: Patel, Smita N
Subject: Re: [Fedora-commons-developers] REST API ingest issue
Yes, at the same time that I merge my branch to update the REST API, I'll be
merging in a branch with some updates to trunk that will include the REST API
jar. We're still having discussions as to when to pull the experimental label
off of the REST API. It may happen for the 3.2 release, which is currently
slated for May 5th.
best,
Bill
On Mon, Mar 9, 2009 at 8:45 AM, Patel, Smita N
<[email protected]<mailto:[email protected]>> wrote:
Thanks for the detailed explanation. Will the trunk have the latest version of
the rest-api jar? Also, is the REST implementation out of the experimental
stage?
Thanks
Smita Patel
From: Bill Branan
[mailto:[email protected]<mailto:[email protected]>]
Sent: Friday, March 06, 2009 5:00 PM
To: Patel, Smita N
Cc:
[email protected]<mailto:[email protected]>
Subject: Re: [Fedora-commons-developers] REST API ingest issue
Hi Smita,
As a convenience, the REST API ingest method captures the case where an object
already exists and attempts an update instead. I agree that in this case you
should not get a 201 CREATED response, and I've changed this to a 200 OK in my
current branch (FCREPO-391) which will likely get merged to trunk in the next
few weeks. You can call the getObjectProfile method of the REST API to
determine existence prior to an ingest, you should get a 200 response if the
object exists and a 404 if not.
Bill
On Fri, Mar 6, 2009 at 4:03 PM, Patel, Smita N
<[email protected]<mailto:[email protected]>> wrote:
Hi, I am using fedora 3.1 REST API for our services implementation. On testing
the ingest operation though, I found that it is not working the same as the
ingest from the SOAP API-M implementation. When I called the REST API ingest
with the pid that is already existing in the repository, there was no error. It
actually updated the object and returned a HttpStatus.SC_CREATED status.
Whereas, In the API-M, there is an exception; The exception by way of an
example is : "The PID 'demo:2' already exists in the registry; the object can't
be re-created.". Is there not a duplicate PID check anymore in the REST ingest
operation. If there is, how do I call the REST ingest correctly? Are there any
examples that I can refer to, other than the online documentation?
Thank you,
Smita Patel
Sr. Developer
Emory University
________________________________
This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.
If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Fedora-commons-developers mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
