Hi Bojan,
Many thnaks for the quick answer.
With kind regards,
Marianna
>
>
> Am 17.06.2011 13:40, schrieb Marianna Mühlhölzer:
> > Hi Bojan,
> >
> > I want to use the REST Interface for browsing our DSpace repository
> by
> > title, date and subject. When trying to sort items I get problem
Hi Marianna,
Am 17.06.2011 13:40, schrieb Marianna Mühlhölzer:
> Hi Bojan,
>
> I want to use the REST Interface for browsing our DSpace repository by
> title, date and subject. When trying to sort items I get problems with
> the pagination. The _perpage parameter does not work. Using _perpage
> a
Hi Bojan,
I want to use the REST Interface for browsing our DSpace repository by
title, date and subject. When trying to sort items I get problems with
the pagination. The _perpage parameter does not work. Using _perpage
alone has no influence on the number of retrieved items. I always get
all ite
Thanks Bojan
I've updated my DSpace's instance's rest code and am able to retrieve
the logo as you have outlined below.
Cheers
Hayden
On 06/06/11 20:52, Bojan Suzic wrote:
> Hi Hayden,
>
> For the logo issue you previously mentioned, I have updated the code and
> wiki page info.
>
> /communit
Hi Hayden,
For the logo issue you previously mentioned, I have updated the code and
wiki page info.
/communities/{id} - returns information about particular community
/communities/{id}/logo - returns corresponding logo id
The logo is considered as bitstream, like other bitstreams in the system
Peter your patch has worked for me thanks.
The next issue seems to be with search; I get the same error when
executing most searches (although not all).
For example, the following search succeeds:
http://www.wijiti.com:8080/i/testing/rest/search.xml?query=geisha
but most searches don't:
http:
Hi Peter,
> I was looking at the DSpace REST API module today, and I too had errors
> with getting null when viewing something like:
> http://localhost:8080/restapi/communities/213.xml
...
> Attached is my patch for fixing that. https://gist.github.com/952058
> (I'd prefer not sending files to th
Quick FYI:
Bugs/patches for the REST API can actually be submitted directly to our
JIRA at:
https://jira.duraspace.org/browse/DS
Just be sure that when you submit the bug/patch, you select the
"Component" as "REST API (experimental)".
- Tim
On 5/2/2011 1:13 PM, Peter Dietz wrote:
> Hi All,
>
Hi All,
I was looking at the DSpace REST API module today, and I too had errors with
getting null when viewing something like:
http://localhost:8080/restapi/communities/213.xml
*message* *Failure processing entity request (/communities/213.xml): null*
*description* *The server encountered an int
Hi Bojan,
Thanks for getting back to me on this. I was having an issue whereby I
was loosing the connection to the DB through the context. In
investigating this I found the problem was the calling of
context.complete() in the ItemEntity constructor as the context.complete
nulls the connection
Hi Mark,
sorry for late answer. I think this error is related to number of
database connections opened. As you have already noticed in the code,
for each request it creates new Context object, which maintains
connection to the database. Under some circumstances/conditions, I think
this object
A 500 is an internal server error, what do the logs say?
cheers,
Steve
On 15/03/2011, at 9:03 PM, Mark Melia wrote:
> Hi Bojan,
>
> I have taken the latest code from the SVN address above and the
> authentication issue is still there. I am not sure how you are able to
> over come it without
Hi Steve,
Thanks for the reply - the only thing outputted on the logs when the
request is made is:
2011-03-15 10:14:15,017 INFO org.dspace.rest.providers.UserProvider @
user:anonymous:ip_addr=:entity_exists:29
Thanks,
Mark
On 15/03/11 10:16, Steve Swinsburg wrote:
> A 500 is an internal serv
Hi Bojan,
I have taken the latest code from the SVN address above and the
authentication issue is still there. I am not sure how you are able to
over come it without changing the code in the AbstractBaseProvider. I
have made the change you suggested - rather than just removing the
exception th
Hi Bojan,
Thanks a million for your reply. I am thinking maybe I do have an
earlier version of the code - Today I tried to get details on one
particular collection using
http://localhost:8080/rest/communities/29.xml - this resulted in an error -
HTTP Status 500 - Failure processing entity reque
Am 11.03.2011 00:58, schrieb Kim Shepherd:
> Also, kudos to Bojan for continuing to support his work. Sounds like I
> need to give it another go :-)
Thanks :) but I would suggest you to wait a little bit.. I will soon
release it as RC, then it would provide better stability and probably
fit you
I'm sorry, I don't. We are not actually building a repository but developing
software that will communicate with repositories. So our dspace server is only
for testing and development.
Chris
- Original Message -
Hi Chris,
Do you have a public-facing repository that is making use
Hi Chris,
Do you have a public-facing repository that is making use of this? It would
be great to see it in action.
I feel I may be a bit "behind the times" as far as this project goes..!
Also, kudos to Bojan for continuing to support his work. Sounds like I need
to give it another go :-)
Cheers
Hi Bojan and Chris,
Thanks for your reply.
The action I am calling is the search rest call I am making is search -
http://localhost:8080/dspace/search.xml?query=testitem
When this is called it looks like the method refreshParams is called in
the AbstractBaseProvider class. This method checks if
I have used it and so far it works perfectly. Our test repository does not use
authentication and the plugin seems to work fine.
Chris
- Original Message -
> Hello everyone,
>
> Just wondering if anyone else has played around with Bojan Suzic's
> great
> REST API extension? I am trying
Hi Mark,
no, it is not necessary to be logged in order to search.
By my understanding, you have already installed the extension and it
requires a user to be logged in order to search?
If that is the case then please send your configuration description
direct to me, the message/action you tried a
Hello everyone,
Just wondering if anyone else has played around with Bojan Suzic's great
REST API extension? I am trying to allow for REST queries to be done on
my DSpace. With our DSpace anonymous users can search. It seems to me
that you must log in as an authenticated user to do anything wit
22 matches
Mail list logo
