- Jan 2020
-
scottbot.github.io scottbot.github.io
-
coffee
OOh, another good choice.
-
-
scottbot.github.io scottbot.github.io
-
Another great heading (h2)
Is this really so great?
-
- Oct 2018
-
teic.github.io teic.github.io
-
diuers rare things
What does this look like: https://gist.github.com/mdlincoln/cb8f92199200dac5cf502bcac5b1e828
-
- Dec 2017
-
github.com github.com
-
Updated annotation.
Tags
Annotators
URL
-
- Aug 2017
-
github.com github.com
-
Updated annotation.
Tags
Annotators
URL
-
- Apr 2017
-
collectionsasdata.github.io collectionsasdata.github.io
-
infrastructure
helpful to include "such as shared vocabularies or ontologies"? too limiting?
-
- Jun 2016
-
-
with a link to the newly-opened issue
Eagle-eyed readers will note that the script is wrong: it posted an API link rather than a human-readable link.
-
-
programminghistorian.org programminghistorian.org
-
Nihil Novi Sub Sole
Classicists just gotta classicize.
(This comment is only intended to trigger a new issue on the PH repo. No offense to @shawngraham is meant!)
-
-
github.com github.com
-
R made me!
Tags
Annotators
URL
-
-
h.readthedocs.io h.readthedocs.io
-
"document": { ... }, "target": [ ... ], "tags": [],
Docs on which of these fields must be formatted, and how, would also be great.
-
HTTP/1.1 200 OK Content-Type: application/json; charset=UTF-8 { "rows": [ { "consumer": "00000000-0000-0000-0000-000000000000", "created": "2014-01-12T18:36:15.697572+00:00", "id": "LGVKq4E4SKKro1dBBEMwsA", "permissions": { ... }, "references": ["6lkzoOubSOOymDNDIgazqw"], "target": [], "text": "Peut-etre", "updated": "2014-01-12T18:36:15.697588+00:00", "uri": "http://epubjs-reader.appspot.com//moby-dick/OPS/chapter_003.xhtml", "user": "acct:gluejar@hypothes.is" } ], "total": 1 }
A full list of the possible response fields would be very useful!
-
-
perspective.revues.org perspective.revues.org
-
Second, there remains a rift between academic art historians’ understanding of the digital future of our field, and the digitally-inflected work that museums have pursued for decades.39 Thus, the specter of the “two art histories” is newly relevant today.40 Digital methods offer an opportunity for bridge-building between academic art historians using computational methods, and museum staff (including not only curators, but also registrars, archivists, and technologists) who have built rich repositories of collections data. Yet digital efforts in museums have generally been turned towards visitor services and outreach needs, rather than producing or supporting original research. Recent efforts such as the Online Scholarly Catalog Initiative and the digital “labs” at the Cooper-Hewitt Museum and the Metropolitan Museum of Art suggest a sea change in museums’ perspective on this question. However, it will take continued pressure from both sides of our field to ensure that these experiments gain a permanent place at the table.
Technical resources will flow easily towards big public projects. It will be harder to steer them towards more complex and specialized projects with smaller audiences.
-
- Dec 2015
-
literaturegeek.com literaturegeek.com
-
Jekyll is faster, lighter, and better for longterm security and preservation.
It might be helpful to emphasize the archivalbility bit: DB-based websites need a constantly-running DB server; Jekyll just needs flat HTML files
-
This is the first hypothes.is comment I've ever done!
I know Getty Publications did an experiment with Jekyll as a publishing platform a while back: https://github.com/gettypubs/inventionofphoto-jekyll
-