You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
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)
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)
The text was updated successfully, but these errors were encountered: