Hi Claudia,
DataCite has a "IsActive" flag, that when set to false excludes the
metadata from being available in DataCite's metadata store.
Best,
Agustina
On Friday, 5 May 2017 14:27:41 UTC+1, Claudia Jürgen wrote:
>
> Hi Agusta,
>
> while your at it you may also clarify not only the
There is some debate about whether one ought to be able to probe the
existence of restricted objects, which 403 would enable. That's probably
the reason for the 404. We may need two levels of restriction to satisfy
every site.
--
You received this message because you are subscribed to the
Hi Agusta,
while your at it you may also clarify not only the required status code
(this might actually depend on the provider)
but how to handle "withdrawn" items in general. At the moment they keep
their is_registered status see
https://jira.duraspace.org/browse/DS-3474 and thus the metadata
Let me then check with both Rachael Kotarski (BL) and Martin Fenner (DataCite)
to see their recommendation. Will post it here once I get a response.
Many thanks again!
Agustina
> On 5 May 2017, at 14:18, Tom Desair wrote:
>
> Could you also check with DataCite to see
Could you also check with DataCite to see what status code they (and other
DOI providers) recommend for restricted items? Ideally I think we should go
for 403 (Forbidden) but that might still be too restrictive for them.
Based on their recommendation, I think it is definitely worth it to create
a
Hi Agustina,
seems as if xmlui and jspui are treating these cases differently
a) JSPUI
withdrawn - 200
restricted - 403
b) XMLUI
withdrawn - 404
restricted - 404
Restricted should be 403 as for withdrawn I'm not sure and tend to 200.
410 would indicate that the resource is gone forever, but
Hi Tom,
Many thanks for the swift response and the pointer. I already located it, and
was thinking of add a local fix to the repository but wanted to check with the
community first. This is definitely causing issues with DOIs. We are currently
using DataCite through the British Library for
Hi Agustina,
Yes this is the normal behaviour:
https://github.com/DSpace/DSpace/blob/dspace-5.6/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/artifactbrowser/RestrictedItem.java#L223
I agree that 404 is a rather aggressive status code and that maybe we
should change this to 403
Hi Andrea
Thank you so much, now it is running without problems.
Now i am running dcris in local host and i can not install into server and
can not do test. I have a doubt, i am interested in the integration with
the external database. I have readden the documentation, but i don´t
understand if