oduwsdl
Potential integration with WASAPI?
There is currently some work being done on an IMLS Grant for the WASAPI project, which I believe initially involves Archive-It. There was also some talk awhile back of webrecorder supporting it for WARC upload.
We should investigate any advantages that adhering to this protocol may provide. Interoperability may facilitate new users trying out ipwb.
Use case, allowing a user to authenticate with their Archive-It credentials (using A-It's OAuth, I presume) and single-click to pull in all their remotely stored WARCs into their local ipwb instance.
There exists a Python (3) client for Archive-It's WASAPI implementation, see https://github.com/unt-libraries/py-wasapi-client/issues/19.
Webrecorder now has a WASAPI endpoint.
See https://webrecorder.io/docs/api (via @N0taN3rd) or access by collection at https://webrecorder.io/api/v1/download/webdata.
If you log into your account, doing something like https://webrecorder.io/api/v1/download/webdata?collection=my_collection would should give you a JSON response. (thx @ldko)
I have developed a private integration of ipwb with WASAPI that hooks into the admin interface for importing WARCs. I hope to submit a PR and get this merged soon.
However, it might also be useful to allow this functionality to be invoked at startup of ipwb replay, e.g., allow a user to submit the parameters via the CLI and initiate the web access points with data pulled from WASAPI endpoints by default. This flow would also be interesting for automated testing.