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

Integrating the DOG web application #238

Open
dietervu opened this issue Oct 7, 2021 · 0 comments
Open

Integrating the DOG web application #238

dietervu opened this issue Oct 7, 2021 · 0 comments

Comments

@dietervu
Copy link
Contributor

dietervu commented Oct 7, 2021

If the input for the LRS is a URI that the profiler recognizes as HTML or CMDI, the DOG app should be added to the list of callable tools, supposed a preflight API check returns that the URI is recognized by the Digital Object Gateway.

Example workflow:

  • user enters https://zenodo.org/record/1639549
  • profiler recognizes HTML
  • profiler sends preflight API call to the DOG REST API with the URI as argument
  • the response is positive, the DOG will show up as processing tool
  • user selects DOG as processing application
  • in the DOG web application, the actual files are shown (in this case PDF), with a button "process in switchboard" (this is based on the DOG's awareness about the Invenio API and a call it has made for the URI)
  • user clicks the button and gets redirected to the switchboard with the option to process the PDF
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

No branches or pull requests

2 participants