51 Matching Annotations
  1. Oct 2023
    1. Appendix

      Make this match "Collections" in size; add to TOC

    2. e.g. pages in a book

      maybe parenthetical?

    3. Conventions IDs

      kind of add to have 2 levels of subheadings here.

    4. announcement.

      I wouldn't link the word "announcement"

    5. route

      Could we use pattern or template? I feel like "route" is a programmer term, and we're speaking to technical users, but not programmers, here. (Picture your favorite medievalist.)

    6. https://iiif.archive.org/iiif/3/leedsuniversitylibrary/4/collection.json3000-3775

      Adding appendix-y sorts of material after this will wrap up the page nicely, too.

    7. In order to get the remaining items

      How can you tell?

      If the bottom of the collection has ""Page 2 of 4" then you have a paginated collection. Many IIIF viewers will ????

    8. manfiests

      spelling

    9. route

      pattern?

    10. colleciton

      spelling

    11. we've create a route that generates

      Can we just say "we generate"

      I'm against using "route" to non-programmers.

      (and if we keep this, create needs to be created)

    12. More than one IIIF manifests can be formally grouped into what is called a "collection" manifest.

      I'd change this to: A group of more than one IIIF manifests is called a collection.<br /> and then combine it with the following paragraph.

      Otherwise it's sort of a technical concept hanging out by itself, which this isn't the place for -- folks reading this aren't creating their own collection manifests, they are using the collection manifests that are generated from IA's collecitons.

    13. see the "Collections - A Basic Guide" page.

      get rid of "the" and "page" to simplify this.

    14. collections

      "Internet Archive collections" (to differentiate)

    15. manfiest

      spelling

    16. https://iiif.archive.org/iiif

      Although I might mention this in the collections section as a "look, the entire internet archive is a collection" sort of thing.

    17. Listing Items

      I think this also belongs at the end; it's more of an appendix than an "important thing you really need to know"

    18. associted

      spelling

    19. manfiests

      spelling mistake

    20. Getting legacy IIIF Presentation API 2.1 manfiests

      I'd be tempted to move this to the bottom, think of it as an appendix.

    21. The manifest URL can also be used with the version number removed (https://iiif.archive.org/iiif/:id/manifest.json),

      This looks weird in my browser -- URL formatting overlaps with the text above it.

    22. https://iiif.archive.org/iiif/:id/manifest.json

      Does this need the /3 ?

    23. There are some edge cases where rare file types are not represented in the IIIF presentation manifest. If you encounter an item where you think this may be the case, contact support.

      Or open an issue?

    24. which can be verified through the metadata API.

      cut this.

    25. Movie

      Is this IA's way of referring to video?

    26. Presentation API

      So.... is Presentation after Image the right order? I know it's how we always do it, but if you're not an implementer, I'm not sure it's the right order. The manifest is really the thing most folks interact with.

      And it sort of solves the image vs AV problem I pointed out in Getting Started.

    27. sequences of digital object

      add "e.g. pages in a book" ?

    28. Manifest URL

      Could we link this to the right section?

    29. One such tool is Glen Robson's Canvas Finder, which takes as input a Manifest URL (see below for how to find that).

      And returns....

      And returns a URL to the specified manipulated section of the image (?)

    30. https://iiif.archive.org/image/iiif/3/img-8664_202009%2FIMG_8664.jpg/info.json

      ok, I really hate where this one broke! Not on the hyphen, on a /, please.

    31. generate

      true, but maybe "find" is friendlier?

    32. {scheme}://{server}{/prefix}/{identifier}/{region}/{size}/{rotation}/{quality}.{format}

      Can we break this at a different point? I kind of like prefix on the first line and identifier on the 2nd.

      (Wish it didn't have to be broken across lines at all.)

    33. Getting started

      This whole section gets a bit confusing -- how much of it is about images and how much about AV? It's written to be about images, with AV tucked into the first paragraph...

      Maybe differentiate in this Getting Started section, pointing AV users to the Items section below and book/image folks to the image api??

    34. (annotation, side-by-size viewing, and loading images from different institutions into the same space)

      add an e.g. at the beginning?

    35. image or book

      item? Or "image, book, audio or video"

    36. now have an associated mechanism for accessing them via IIIF APIs

      Can we simplify this? "now have a IIIF API URI"???

    37. movie

      movie or video?

    38. ":"

      could we add a (colon) after ":" -- I know this stuff and I read that as a period not a colon!

    39. issues identified such as bugs or feature requests can be added.

      simplify to "bugs or features requests can be added"

    40. adopted

      perhaps "adopted by the Internet Archive" ?

    41. see our announcement blog post, Making IIIF Official at the Internet Archive.

      How about "see our Making IIIF Official at the Internet Archive announcement"

    42. fit in with

      "fit with" sounds better.

    43. The goal of IIIF is interoperability: to make an institution's image and audio/visual openly accessible resources available and easily reusable in a variety of web viewers and players without the need for any special plugins or software.

      I feel like either here or the previous section should mention "open source"

    44. initialism

      this is a bit too cute. :) perhaps acronym?

  2. May 2021
  3. Apr 2019
  4. Oct 2017
  5. Nov 2016
  6. Jul 2016
    1. RangeSelector: this what we had we had until now: a pair (for start and end) of XPaths pointing to the DOM elements, and the string offsets inside them. TextPositionSelector: this is a pair of string offsets, marking the start and end of the selected text in the character string representing the whole document. TextQuoteSelector: this selector stores three strings: exact: the selected text itself prefix: the (32-char long) text immediately before the selected text suffix: the (32-char long) text immediately after the selected text

      An API Call to an annotation will show these values.

    1. This is a page note.

    2. Now you have the extension up and running. It's time to start annotating some documents.

      Hypothesis annotates highlighted sections of documents. It has tags, and the ability to make an annotation private or public.