-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please implement a method for dealing with broken DOI #670
Labels
Comments
@nthieberger I've created a fix for this, but cannot deploy it to the staging server for you to test out, because we haven't been supplied with SSH access to the staging machine. |
Dear Andrew,
Jono had the logon details for the staging server and should be able to
create a logon for you. I am in Vanuatu for the next week and am unable to
try this. I'm sorry if Jono is no longer there, but assume that your
processes allow for succession in situations like this.
Thanks,
Nick
…On Mon, 23 Jul 2018 at 13:51, Andrew Grimm (Terem Technologies account) < ***@***.***> wrote:
@nthieberger <https://github.com/nthieberger> I've created a fix for
this, but cannot deploy it to the staging server for you to test out,
because we haven't been supplied with SSH access to the staging machine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#670 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAlUoInX_cyHtbzfJOV5ovXenT5SoaQqks5uJTo7gaJpZM4Ub_Ww>
.
|
Hi Andrew,
I am unable to log on to the staging server so is it possible to start a
new one and provision it from the source?
Nick
…On Mon, 23 Jul 2018 at 12:51, Andrew Grimm (Terem Technologies account) < ***@***.***> wrote:
@nthieberger <https://github.com/nthieberger> I've created a fix for
this, but cannot deploy it to the staging server for you to test out,
because we haven't been supplied with SSH access to the staging machine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#670 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAlUoInX_cyHtbzfJOV5ovXenT5SoaQqks5uJTo7gaJpZM4Ub_Ww>
.
|
agrimmtt
added a commit
that referenced
this issue
Nov 7, 2018
… they lack authorisation, but can view the item or collection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a doi fails it needs to send the user some informative advice. If the doi pointed to an essence file, the response could redirect to the item that contained the file. If the doi pointed to an item it could redirect to the collection that held the item.
The text was updated successfully, but these errors were encountered: