samvera / iiif_manifest Goto Github PK
View Code? Open in Web Editor NEWLicense: Other
License: Other
This seems pretty stable, and releasing 1.0 will make managing it as a dependency (e.g. in Hyrax) easier.
See: samvera/hyrax#3880
This work shall build upon (i. e. involve the refactoring and generalization from) the Princeton University implementation of Valkyrie, Figgy.
This is derived from samvera/maintenance#119, and follows the guide in https://guides.rubygems.org/mfa-requirement-opt-in/
It is useful to render manifests as sammelbands outside of the narrow definition in the ManifestFactory. The gem should provide a way to indicate if works should be rendered as sammelbands.
Rails version 6.0.0 was released on 08/16/2019, and in accordance with the charter of the current phase of the Component Maintenance Working Group, the CircleCI configuration for this should be updated.
Derived from samvera/maintenance#77
Currently, Scientist.com has made tremendous progress in integrating support for PDF derivative generation with https://github.com/scientist-softserv/iiif_print. Perhaps the approach undertaken by this Gem should be ported into this project?
This repository’s default branch has already been renamed to main
using GitHub’s renaming tool. In order to preserve automatic redirection of links that reference the old branch name master
to the new default main
branch, a branch with the old name should not be recreated.
CircleCI can be used to prevent the recreation of the old default branch name by preventing PRs with a branch named master
from being merged by causing a test failure during continuous integration.
Git's default "master" branch derives from "master/slave" jargon which perpetuates systemic racist language and systems (see email Replacing "master" reference in git branch names). To uphold our Code of Conduct, we must move away from the term "master" in our technical language (as well as words like blacklist or whitelist).
If a PR is submitted with a branch named master, the continuous integration tests should fail.
If a PR is submitted with a branch named master, the continuous integration tests will not fail because of the branch name.
Background on the renaming effort is available in the working group notes.
See samvera-labs/iiif_manifest#?
Implementing thumbnail from the IIIF Presentation 3.0 spec.
Ruby 2.7.0 was released on 12/25/2019, and in accordance with the charter of the current phase of the Component Maintenance Working Group, the CircleCI configuration for this should be updated.
Hello, this is more of a question than a issue, but is there any way to cleanly add a builder to this process?
I need to add thumbnail support to the manifest and I know I can overwrite things and all that, but I was hoping there was a place where I could just insert my own builder and let the code run as intended.
I'm happy to clarify, if I'm not being clear. Thanks.
This follows the proposed maintenance reorganization within samvera/maintenance#137
I've been experimenting with using the Universal Viewer in conjunction with the RIIIF server for the AIC's Sufia-based app, and would like to use it with PDFs. This means creating media sequences, that implement type "ixif", and adding them to pdf manifests (and maybe more).
I have a behavior module for creating manifests locally, in which I add the media sequences to the manifest created by this gem, and it works, which is great. But I think the way I found is janky, and I'd love help in finding a better architecture for this. One way would be to make it part of this gem, but that seems really ambitious to me, and would require adding options to choose when to add them (based on file and viewer type, I'd think). Another way might be to do what I'm doing, find a way to extend the manifest creation locally, only in less janky way, probably.
This is my manifest_behavior module, that gets added to the generic_works_controller:
https://gist.github.com/jenlindner/9bc2162e95f30f7f1cd8281e0dc165a1
Thanks,
Jen
This repository’s default branch has already been renamed using GitHub’s renaming tool. Links that reference the old branch name are automatically forwarded to the new default branch. But string references are not automatically updated.
Check this repository for hard-coded string references to the legacy “master” default branch and update them to the new default branch name “main.”
Important places to check include, but are not limited to:
NOTE: READMEs, wikis, and other documentation are important to update to avoid confusion and correct errors in long lasting documentation.
Less common places to check:
NOTE: String references to themaster
branch in Issues, PRs, and code are uncommon. Also Issues and PRs are temporal in nature, making it less critical to update those occurrences.
Git's default "master" branch derives from "master/slave" jargon which perpetuates systemic racist language and systems (see email Replacing "master" reference in git branch names). To uphold our Code of Conduct, we must move away from the term "master" in our technical language (as well as words like blacklist or whitelist).
Templates can be found here: https://github.com/samvera/maintenance/tree/master/templates
Add the following branch renaming language to the README for this repository.
## Contributing
If you're working on PR for this project, create a feature branch off of `main`.
This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct) and [language recommendations](https://github.com/samvera/maintenance/blob/master/templates/CONTRIBUTING.md#language). Please ***do not*** create a branch called `master` for this repository or as part of your pull request; the branch will either need to be removed or renamed before it can be considered for inclusion in the code base and history of this repository.
Git's default "master" branch derives from "master/slave" jargon which perpetuates systemic racist language and systems (see email Replacing "master" reference in git branch names). To uphold our Code of Conduct, we must move away from the term "master" in our technical language (as well as words like blacklist or whitelist).
Derived from samvera/maintenance#89
The maintenance template for CONTRIBUTING.md is used by all Samvera repos. Replace the current version with the updated maintenance template version.
Implementing posterCanvas from the IIIF Presentation 3.0 spec.
DisplayContent
and run through the CanvasBuilder
Derived from samvera/maintenance#76
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.