I seem to have
wax_tasks (1.0.0.pre.beta) installed. Is this something you've run into before?
@mnyrop here is what the config looks like https://gist.github.com/edsu/992c50f13d477e05aa403a00993c9928
@JoshuaGOB also, if you @ me I'll likely be able to notice / respond sooner, depending on the circumstances.
(for folks who have original metadata messing up the orientation of the image of the viewer)
(feel free to make a private one and add me as a collaborator)
Hey folks! First off, thanks @elotroalex @mnyrop et al for Wax! I'm just wondering if it's possible to embed one specific image of a multi-image object in an exhibit? In other words, with {% include inline_image.html collection='collection' pid='obj1' %} I need image 04 from obj1. Thanks in advance!
Hi @bradleypallen custom sorting is not currently a feature, but I would be happy to point you in the right direction to implement this for your own site. This is where you'd want to make a slight change: https://github.com/minicomp/wax/blob/1adf4f462865d543dc5e1ffb3b83ca288b9a5c73/_includes/collection_gallery.html#L4
And you'd want to use the
sortfilter in liquid to do it: https://www.siteleaf.com/blog/advanced-liquid-sort/
Happy to go into more detail if needed.
@mnyrop that was easy to change to get the behavior I was looking for, thanks so much! The only remaining issue I have is that I am getting errors reported from the Jekyll server when I go to a collection item page of the form: "`/wax/img/derivatives/iiif/images/brion_gysin_dream_machine_1/full/306,/0/default.jpg' not found." Else everything is working as advertised.
@bradleypallen does everything look fine in the UI when you play around? if so, i wouldn't worry about it. the IIIF viewer should be able to dynamically provide a different image size if the one requested isn't available. this is somewhat normal as long as the actual behavior is correct, and is likely just a symptom of jekyll serve being so verbose.
I feel like the larger GLAM community has struggled with establishing straight-forward solutions for institutions that have little to no technical staff, minimal budgets and rich collections. Wax is increasingly looking like a promising frontend to a decoupled, light-weight digital preservation backend.
Does Wax have any numbers on scale? i.e. how many objects/images can be searched and delivered in reasonable user-time?
For your question, it really just depends on the structure of the lunr index. You can have more records if the metadata is simple, fewer if there's a lot of text per item. As an example, https://bunraku.library.columbia.edu/search/ has a pretty enormous search index. It's a little slow but not terrible, and could probably be optimized further.
Here's the index: https://bunraku.library.columbia.edu/js/lunr-index.json
@binipringle do you have a public repository i could look at? hard to say without seeing what you're working with
Hello @mnyrop , thank you a lot for getting back to me. I got it working! It was my csv file which got messed up because there were commas in the source column and the csv was comma-separated. iiif derivatives and pages are working beautifully. Here's the repo: https://github.com/binipringle/laislat
Hi, folx! Gitter has left some things to be desired (mostly consistent notifications), so I set up a #minicomp-wax channel in the Code4Lib Slack. If you're not currently a member of the Code4Lib Slack, my understanding is you can request an invite here: https://docs.google.com/forms/d/e/1FAIpQLSeD77mBp0Y13mFePF8UmDwFrlbxNx3VttEjz_3dgglJeK-Zbg/viewform?c=0&w=1
I'm hopeful the switch will be worth your while, especially since many of the other channels will likely be of interest!
–Marii
Hello! Very new to Wax and know that once I get it down I will come to love it! I am able to complete steps 1-10 without issue. Unfortunately when I run the bundle exec jekyll serve the images dont appear (but their labels do) clicking the box where they should be brings me to a 404 message. I also cant seem to browse the collection because the stock qatar images are still there?
question: my site is basically working but I think I made the big mistake of using CAPS in my IDs and filenames. I have partially resolved that by changing the metadata and reprocesing but when I compile the search index it still comes out with CAPS. The links from search results have those CAPS and lead to 404 pages. Just changing to lowercase fixes that but I don't know how to re-process everything so that the index uses lowercase. Ideas? Is there a way to delete all assets (i.e., derivatives and manifests, etc) and recompile everything?
Hi! I’m currently digging into wax for a project. I got two questions regarding to faceted browsing where I’d appreciante some hints.
- Is it possible to specify multiple fields as facets in the collection browser? E.g., facet by work type and motif?
- Is it possible to have a facet on a multi-value field? E.g., when I have motifs, each item might contain multiple motifs. The first challenge is to encode that in the data sheet. CSV cannot really express that, so I guess I’d have to use YAML or JSON? But would the browsing widget support filtering by these multi-value fields at all?