We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(Continuing the discussion about LPWC->SOA federated access from #7)
Look at this paper: https://linkedpaperswithcode.com/resource/?uri=https%3A%2F%2Flinkedpaperswithcode.com%2Fpaper%2Funderstanding-human-hands-in-contact-at-1 It shows the author names, but clicking on one of them leads to eg https://linkedpaperswithcode.com/resource/?uri=https%3A%2F%2Fsemopenalex.org%2Fauthor%2FA5061180684 which gives this message:
No data available for "A5061180684” Learn more about it at https://semopenalex.org/author/A5061180684 Clicking the link will take you out of metaphactory
Clicking on https://semopenalex.org/author/A5061180684 shows the author info in SemOpenAlex Explorer.
Formally the message is correct. But both datasets are in Metaphactory, both controlled by the same people.
LPWC knows which classes (nodes) are hosted in SOA. So could it skip the message and jump directly to the SOA URL?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
(Continuing the discussion about LPWC->SOA federated access from #7)
Look at this paper: https://linkedpaperswithcode.com/resource/?uri=https%3A%2F%2Flinkedpaperswithcode.com%2Fpaper%2Funderstanding-human-hands-in-contact-at-1
It shows the author names, but clicking on one of them leads to eg
https://linkedpaperswithcode.com/resource/?uri=https%3A%2F%2Fsemopenalex.org%2Fauthor%2FA5061180684
which gives this message:
Clicking on https://semopenalex.org/author/A5061180684 shows the author info in SemOpenAlex Explorer.
Formally the message is correct.
But both datasets are in Metaphactory, both controlled by the same people.
LPWC knows which classes (nodes) are hosted in SOA.
So could it skip the message and jump directly to the SOA URL?
The text was updated successfully, but these errors were encountered: