This short guide explains how to create a JackTrip Virtual Machine using DigitalOcean, an easy to use cloud server platform. The goal here is to create a server with a desktop interface that you can login to and start JACK and QJackTrip for rehearsals, performances, etc. You can also install audio processing software like SuperCollider but I will save that for another tutorial. The benefit of creating this on a virtual machine is that using DigitalOcean's snapshot feature you can save this configuration and spin it up as needed and save money. You don't need this running 24/7 if you're only using it for rehearsals and performances. This configuration costs about $0.35/month to store on DigitalOcean as a snapshot. The minimal configuration described at the very bottom (without the desktop interface) is about $0.11/month to store on DigitalOcean using their snapshot feature.
María A. Matienzo anarchivist
| { | |
| "skill": 5, | |
| "stamina": { | |
| "max": 18, | |
| "remaining": 15 | |
| }, | |
| "name": "Tom Sawyer", | |
| "background": "River Child", | |
| "luck": { | |
| "max": 8, |
| #this | |
| ffmpeg -loglevel debug -f hls -referer 'https://10play.com.au/live' -user_agent 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/82.0.4050.0 Safari/537.36' -f hls -i "https://manifest.prod.boltdns.net/manifest/v1/hls/v4/aes128/2199827728001/6bd7fe89-1f2f-42d0-b7a5-c676791a0d83/10s/master.m3u8?fastly_token=NWUzZDliOGZfNTJhZjJhN2IxMzQ5OTdjNGVkYmEzODkwNjYwZTYyMWY2ZmY1YjNmNGJkNWM3NjdiNDFiZmViNjczNzMwMmJlYQ%3D%3D" -c copy project5.mp4 | |
| # or this | |
| ffmpeg -loglevel debug -f hls -referer 'https://10play.com.au/live' -user_agent 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/82.0.4050.0 Safari/537.36' -f hls -i "https://manifest.prod.boltdns.net/manifest/v1/hls/v4/aes128/2199827728001/6bd7fe89-1f2f-42d0-b7a5-c676791a0d83/10s/master.m3u8?fastly_token=NWUzZDliOGZfNTJhZjJhN2IxMzQ5OTdjNGVkYmEzODkwNjYwZTYyMWY2ZmY1YjNmNGJkNWM3NjdiNDFiZmViNjczNzMwMmJlYQ%3D%3D" -c copy -bsf:a aac_adtstoasc project3.mp4 |
code debt in the metadata context may include cataloging done outside of the confines of our cataloging rules ... or in violation of established metadata specifications
debt native to the metadata itself -- not enough of it, or metadata insufficient to meet user needs
Problem: how to provide Google Images with a full image suitable for display in its search results, without requiring regular users to download a large image?
Solution: link to a suitable full image in a schema.org contentUrl property
Evidence that this works: I've tried it in a low-traffic hobby site, using static IIIF images. E.g. for this image, the schema.org entry looks like this:
Update, March 2019
Many of the discussions below have been synthesised into this slide deck: https://docs.google.com/presentation/d/1zAmXDlfvuwlQtp9uVgFLS7RVcfNqTcyEJybnNdQ2TgY
The links below are more comprehensive and are kept here for posterity. The other document worth considering is this:
Universal Viewer design principles
(in progress) Inspired by discussions at UVCON; an attempt to set out some guiding principles for the UV; comments sought!
- v 1.0 "How to hack code4lib" by Declan Fleming, Director of IT, UCSD Libraries (BigD in channel), heavily edited by the community
- v 2.0 sources: v 1.0 from Code4Lib; "Social Rules" and "Programmer Community Issues" from Write The Docs
Working draft for consideration by the community. This will eventually be placed in a pull request in the CodeOfConduct4Lib [CoC4Lib] repository. ~yo_bj
[todo - table of contents?]
| require 'benchmark' | |
| require 'uri' | |
| require 'solr_ead' | |
| require 'concurrent' | |
| # Make a subclass with all the speed patches | |
| class IndexerWithPatches < SolrEad::Indexer | |
| def additional_component_fields(node, addl_fields = Hash.new) | |
| # Clear or create the cache |
For background, see this GitHub issue -- it has the UX design in there.
- The exhibit users are required to manage Zotero bibliography libraries as the database for an exhibit item's bibliography information.
- They are also required to manage the "synchronization" between their exhibit and Zotero (via the Exhibit Settings > Bibliography).
Some examples about how your objects in IIIF (the bridge to the Human Presentation API) link to semantic description (your model, or other shared models). The IIIF manifests for all "catalogue" objects would link to a semantic description via the seeAlso property:
A link to a machine readable document that semantically describes the resource with the seeAlso property, such as an XML or RDF description. This document could be used for search and discovery or inferencing purposes, or just to provide a longer description of the resource. The profile and format properties of the document should be given to help the client to make appropriate use of the document.
While your catalogue Manifests link to some experimental RDF, your IIIF Collections currently don't link to seeAlso resources, but they should, expecially when you start making ad hoc curated collections. And similarly for ad hoc manifests.
This strong link between the Presentation API object that people "see" and the semantic descrip