Skip to content
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

dedicated resolver page? #36

Open
ynnig opened this issue Feb 22, 2023 · 2 comments
Open

dedicated resolver page? #36

ynnig opened this issue Feb 22, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@ynnig
Copy link
Member

ynnig commented Feb 22, 2023

Consider making a dedicated resolver page with the resolve box and extracts from the factsheet on resolution and proxy behaviours that people may not be aware (like parameters, REST API the Chrome plug in) We could also make something similar to the Handle resolver page with options to resolve to the record (http://hdl.handle.net) or bring the data in (such as who the RA is)

@ynnig ynnig added the enhancement New feature or request label Feb 22, 2023
@JonathanClarkDOIF
Copy link
Contributor

So far, we have had two researchers contact us about this. We do know that a lot of resolutions happen from the home page (when we last looked about 1/3 of all home page hits ended with a resolution). Website usage in 2022 was about 2 million hits a month. We thus assumed resolutions were most likely from bots / scripts and did not imagine the manual workaround the researchers reported.

@JonathanClarkDOIF
Copy link
Contributor

This is consistent with what Cathy Rey at CNRI reports that if they made changes they always received one or two requests to make the cursor appear in the resolve box when the home page loaded (so same use case)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants