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

Adds data lookup for detected standard identifiers #15

Merged
merged 1 commit into from
Nov 20, 2023
Merged

Conversation

JPrevost
Copy link
Member

Why are these changes being introduced:

  • The ability to provide additional details about what TACOS can detect will allow consuming systems to act on that information. That may mean simply displaying it, or it may mean modifying queries to other systems in more nuanced ways than the original raw search from the user may have led to

Relevant ticket(s):

How does this address that need:

  • This brings the Fact lookup models over from TIMDEX UI and modifies them slightly to be more useful to this application.
  • A details section has been added under standard_identifiers in graphql that will trigger lookups if identifiers have been detected.
  • Only lookups that have matches are run, and only if a user has requested details be provided by requesting fields within the details block

Document any side effects to this change:

dotenv-rails was introduced as a dependency to simplify the test environment configuration.

Any missing configuration documented in the
README will result in exceptions.

Why are these changes being introduced:

* The ability to provide additional details about what TACOS can detect
  will allow consuming systems to act on that information. That may mean
  simply displaying it, or it may mean modifying queries to other
  systems in more nuanced ways than the original raw search from the
  user may have led to

Relevant ticket(s):

* https://mitlibraries.atlassian.net/browse/ENGX-244

How does this address that need:

* This brings the Fact lookup models over from TIMDEX UI and modifies
  them slightly to be more useful to this application.
* A details section has been added under standard_identifiers in graphql
  that will trigger lookups if identifiers have been detected.
* Only lookups that have matches are run, and only if a user has
  requested details be provided by requesting fields within the details
  block

Document any side effects to this change:

dotenv-rails was introduced as a dependency to simplify the test
environment configuration.

Any missing configuration documented in the
README will result in exceptions.
Copy link
Contributor

@jazairi jazairi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

end

def link_resolver_url(metadata)
"#{ENV.fetch('LINKRESOLVER_BASEURL')}&rft.atitle=#{metadata[:title]}&rft.date=#{metadata[:year]}&rft.genre=#{metadata[:genre]}&rft.jtitle=#{metadata[:journal_name]}&rft_id=info:doi/#{metadata[:doi]}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This made me nervous when I did it in Bento, and it makes me nervous here. 🙂 I do think the benefits outweigh the risks, though. The only potential downside is having broken links that we don't know are broken, and the risk of that feels relatively low since it's just OpenURL.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it the manual construction of OpenURL in general that is causing nervousness or something more specific about how it is being constructed. Trusting Alma LinkResolver to be useful is indeed nervous making.

@JPrevost JPrevost merged commit 6a925ab into main Nov 20, 2023
2 checks passed
@JPrevost JPrevost deleted the engx244-lookups branch November 20, 2023 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants