judell / facet Goto Github PK

In this situation:

we send you to https://hypothes.is/a/_Nw9fkTvEemWD_9oSMSD_A

That link can be transcluded into an iframe. Just need to make sure there is no more than one transcluded Hypothesis client at a time, to avoid the dreaded second discovery server syndrome.

I seem to remember that it was possible to search using tag prefixes, but it doesn't seem to be working anymore, https://jonudell.info/h/facet/?max=1000&tag=RRID&group=world.

Hi Jon! Thanks a lot for the awesome hypothes.is tools you created!

I encountered what I believe to be a bug, but maybe I'm simply misunderstanding something. In the latter case, I'd be eager understand things correctly.

If I export an annotation, the column quote in CSV export format is empty (the column text is populated as expected), whereas the annotated/quoted text does appear in the JSON version (in the field exact) and on the HTML version.

As a minimal reproducible example I exported the most recent public annotation on https://www.nytimes.com/* and attached the three outputs (zipped into hypothesis_export.zipas github doesn't seem to allow me to upload those file types).

Thanks!

https://twitter.com/judell/status/1192544342604316672

I filled in user, API token but couldn't change to private group. Refreshing doesn't work.

Hi Jon,

Let me start by saying that the facet tool is absolutely awesome! I have been experimenting a lot with it already, analyzing my annotations.

Small question: in the CSV format, the column "Title" is missing, whereas in in the JSON export it is there. Since it is sometimes more comfortable to work with a CSV export, I would like to ask if there is a specific reason for its absence? Or maybe I am making a mistake? For me this column is very useful because I mainly annotate PDF files and the title is a very fast and intuitive way of identifying in which PDF file specific annotations are located.

All the best,

Jesse

There's a 3-way sync among URL parameters, form values, and localStorage. Rationale:

• Everything I change in a form should be remembered and restored.

• Everything I change in a form should also be reflected into the URL so I can share the view I've constructed with another person, and/or so that I can enable a bot/app to link into that view.

Suppose I navigate to a view that has several non-default params, say max:200, tag:postgres. Now I send you that URL. You have previously navigated to any:sebastopol. Your view will combine these and yield (probably) no results.

So perhaps the rule should be: if non-default params come in on the URL, ignore all local non-default params.