-
Notifications
You must be signed in to change notification settings - Fork 2
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
No such file or directory @ rb_sysope #11
Comments
It looks like you don't have a file named |
You're right. I switched to root with each' for nil:NilClass (NoMethodError) PS. How to quote correctly multiline code? |
It looks like whatever manifest JSON you're trying to download doesn't have any sequences defined. I suspect it may not be a IIIF manifest but some other JSON used by a viewer. |
The file is not used by any viewer, at least to the best of my knowledge. If is offered to download as "IFFF manifest" by the Polish national library POLONA, cf. e.g. the right top corner of https://polona.pl/item/orthographia-seu-modus-recte-scribendi-legendi-polonicu-idioma-q-utilissimus,NzM3OTQzMzA/4/#info:metadata. Your link points to IIIF Presentation API 2.0, Latest Stable Version is 3.0.0. A search there for "sequence" finds in particular: If there is no Range that has the behavior value sequence, and the Manifest does not have the behavior value unordered, then the client should treat the order of the Canvases in the Manifest’s items array as the default order. Are you absolutely sure the POLONA manifests are illegal? |
Ah, I wasn't aware 3.0 wasn't backwards-compatible in this way. I've opened a separate issue for 3.0 support. Thanks for bringing it to my attention! |
Thanks! |
'docker run -t -v $(pwd):/data ryanfb/iiif-dl manifest.json
gives
Parsing manifest JSON...
Traceback (most recent call last):
1: from /usr/src/app/iiif-dl.rb:198:in
read': No such file or directory @ rb_sysopen - manifest.json (Errno::ENOENT)
`BTW, I had to install and to run the docker as a root:
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/create: dial unix /var/run/docker.sock: connect: permission denied.
As you may guess, I don't know docker and follow the instructions blindly.
The text was updated successfully, but these errors were encountered: