issue_comments

Table actions

4 rows where issue = 447408527 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • simonw · 4 ✖

issue 1

  • Option to facet by date using month or year · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
495080591 https://github.com/simonw/datasette/issues/483#issuecomment-495080591 https://api.github.com/repos/simonw/datasette/issues/483 MDEyOklzc3VlQ29tbWVudDQ5NTA4MDU5MQ== simonw 9599 2019-05-23T06:07:53Z 2019-05-23T06:09:05Z OWNER

As far as URL design goes... I'm going to stick with ?_facet_date= for this and use the not-yet-fully-baked JSON alternative syntax. Probably something like this:

?_facet_date={"column":"created","interval":"month"}

Where interval can be day (the default), month or year. And maybe week? Not sure about that.

Still not sure what/if I should do about exposing these options in the UI.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to facet by date using month or year 447408527  
495080390 https://github.com/simonw/datasette/issues/483#issuecomment-495080390 https://api.github.com/repos/simonw/datasette/issues/483 MDEyOklzc3VlQ29tbWVudDQ5NTA4MDM5MA== simonw 9599 2019-05-23T06:06:53Z 2019-05-23T06:06:53Z OWNER

Yes there's definitely something exciting to be done with location facets.

The easiest one would be a radius-distance-from-a-point facet (5km, 10km etc). A more sophisticated thing might be possible on top of GeoJSON and SpatiaLite - that's probably something I would put in a plugin rather than shipping in Datasette itself.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to facet by date using month or year 447408527  
495032933 https://github.com/simonw/datasette/issues/483#issuecomment-495032933 https://api.github.com/repos/simonw/datasette/issues/483 MDEyOklzc3VlQ29tbWVudDQ5NTAzMjkzMw== simonw 9599 2019-05-23T01:28:45Z 2019-05-23T01:28:45Z OWNER

Would this be useful for other facets? How many facet types are likely to have a small number of options that could be linked to in this way?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to facet by date using month or year 447408527  
495032818 https://github.com/simonw/datasette/issues/483#issuecomment-495032818 https://api.github.com/repos/simonw/datasette/issues/483 MDEyOklzc3VlQ29tbWVudDQ5NTAzMjgxOA== simonw 9599 2019-05-23T01:28:06Z 2019-05-23T01:28:06Z OWNER

Here's a UI concept:

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Option to facet by date using month or year 447408527  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);