Hi all, I checked with Rachael Kotarski, from the British Library and with Martin Fenner, who has replied today. Below their responses:
>From Rachael: "I think that 403 is appropriate, but I have CC’d DataCite incase Martin does have a view on this." Martin's response: "Returning a 404 status in situations like this is not unusual. Some organizations prefer this over 403, see for examples https://stackoverflow.com/questions/28582830/access-denied-403-or-404"; @Tom did you open a Jira ticket for this issue? Kind regards, Agustina On Friday, 5 May 2017 16:53:25 UTC+1, [email protected] wrote: > > 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 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 is >> available in the Metadata Store. >> >> Thanks >> >> Claudia Jürgen >> >> >> Am 05.05.2017 um 15:20 schrieb Agustina Martinez: >> > 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 <[email protected]> wrote: >> >> >> >> 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 "quick-win" Jira ticket for this. >> >> >> >> Best regards, >> >> Tom >> >> >> >> Tom Desair >> >> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 >> >> Gaston Geenslaan 14, Leuven 3001, Belgium >> >> www.atmire.com < >> http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> >> >> >> >> >> >> >> >> 2017-05-05 15:12 GMT+02:00 Agustina Martinez <[email protected] >> <mailto:[email protected]>>: >> >> 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 DOIs. >> The BL regularly checks the DOI links across the repository and reports >> back to us with issues for us to fix them. It surprises me that this hasn’t >> come up before. >> >> >> >> I think it would be really useful to change the response status to >> either 403 (Forbidden) or 202 (Accepted) as you suggest. Would it be useful >> if I open a ticket in Jira for this? >> >> >> >> Kind regards, >> >> Agustina >> >> >> >>> On 5 May 2017, at 14:08, Tom Desair <[email protected] <mailto: >> [email protected]>> wrote: >> >>> >> >>> 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 >> >> < >> 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 (Forbidden) or 202 (Accepted). >> >>> >> >>> Best regards, >> >>> Tom >> >>> >> >>> >> >>> Tom Desair >> >>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 >> >>> Gaston Geenslaan 14, Leuven 3001, Belgium >> >>> www.atmire.com < >> http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> >> >> >> >>> >> >>> 2017-05-05 13:59 GMT+02:00 <[email protected] <mailto: >> [email protected]>>: >> >>> Hi all, >> >>> >> >>> We are using DSpace 5.6 and noticed that the item display page for >> restricted and withdrawn items returns 404 status code. This causes issues >> with DataCite DOIs: i.e. when landing to the item via the doi link the user >> sees a correct landing page but when DOI validation checks are being >> performed by DOI registration agencies (e.g. via W3C link checker) 404 >> errors are being reported. >> >>> >> >>> Is anyone else experiencing similar problems? Is using 404 in this >> case best practice? >> >>> >> >>> Kind regards, >> >>> Agustina >> >>> >> >>> -- >> >>> You received this message because you are subscribed to the Google >> Groups "DSpace Technical Support" group. >> >>> To unsubscribe from this group and stop receiving emails from it, >> send an email to [email protected] <mailto: >> [email protected]>. >> >>> To post to this group, send email to [email protected] >> <mailto:[email protected]>. >> >>> Visit this group at https://groups.google.com/group/dspace-tech < >> https://groups.google.com/group/dspace-tech>. >> >>> For more options, visit https://groups.google.com/d/optout < >> https://groups.google.com/d/optout>. >> >>> >> >> >> >> -- >> Claudia Juergen >> Eldorado >> >> Technische Universität Dortmund >> Universitätsbibliothek >> Vogelpothsweg 76 >> 44227 Dortmund >> >> Tel.: +49 231-755 40 43 >> Fax: +49 231-755 40 32 >> [email protected] >> www.ub.tu-dortmund.de >> >> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie >> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für >> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender >> und vernichten Sie diese Mail. Vielen Dank. >> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen >> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher >> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines >> solchen Schriftstücks per Telefax erfolgen. >> >> Important note: The information included in this e-mail is confidential. >> It is solely intended for the recipient. If you are not the intended >> recipient of this e-mail please contact the sender and delete this message. >> Thank you. Without prejudice of e-mail correspondence, our statements are >> only legally binding when they are made in the conventional written form >> (with personal signature) or when such documents are sent by fax. >> > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
