This commit is contained in:
32
PROJECT.org
32
PROJECT.org
@ -88,7 +88,7 @@ fetching and simple saving.
|
||||
*** Metadata sources
|
||||
**** Scraper
|
||||
|
||||
* Backlog [4/24] :vrobbler:project:personal:
|
||||
* Backlog [5/24] :vrobbler:project:personal:
|
||||
** TODO [#C] Create small utility to clean up tracks scrobbled with wonky playback times :bug:music:scrobbles:
|
||||
:PROPERTIES:
|
||||
:ID: 702462cf-d54b-48c6-8a7c-78b8de751deb
|
||||
@ -522,21 +522,6 @@ easily. And our exposure to PII is really low at this point in the project,
|
||||
so we can probably use backtrace=True and diagnose=True to help us root cause
|
||||
bugs faster.
|
||||
|
||||
** TODO [#B] Add a /trends/ page that shows trends based on scrobble data :feature:trends:scrobbles:
|
||||
:PROPERTIES:
|
||||
:ID: 03e9fe30-2bc6-4062-bb24-e95b98daf05b
|
||||
:END:
|
||||
|
||||
*** Description
|
||||
|
||||
This project is a bit invovled. But we should add a top level URL `trends` that shows
|
||||
various trends as defined either in a static settings file, or dynamically via a database table.
|
||||
|
||||
Trends could be things like doing multiple things at the same time, like while driving, what
|
||||
did we listen to this week, or while running, what were listening to this week?
|
||||
|
||||
Or more complicated trends like, how time per page changes based on the book I was reading, or if I was doing something else (music or sport event) while reading.
|
||||
|
||||
** TODO [#B] Scrape ComicBookRoundUp ratings for comic book metadata :books:feature:comicbook:
|
||||
:PROPERTIES:
|
||||
:ID: b3cc57ca-3d2c-468d-ab7c-c47f1120309b
|
||||
@ -594,6 +579,21 @@ named constants for maintainability.
|
||||
- ~vrobbler/apps/scrobbles/importers/tsv.py~ (line 55) -- ="S"= completion status
|
||||
|
||||
|
||||
** DONE [#B] Add a /trends/ page that shows trends based on scrobble data :feature:trends:scrobbles:
|
||||
:PROPERTIES:
|
||||
:ID: 03e9fe30-2bc6-4062-bb24-e95b98daf05b
|
||||
:END:
|
||||
|
||||
*** Description
|
||||
|
||||
This project is a bit invovled. But we should add a top level URL `trends` that shows
|
||||
various trends as defined either in a static settings file, or dynamically via a database table.
|
||||
|
||||
Trends could be things like doing multiple things at the same time, like while driving, what
|
||||
did we listen to this week, or while running, what were listening to this week?
|
||||
|
||||
Or more complicated trends like, how time per page changes based on the book I was reading, or if I was doing something else (music or sport event) while reading.
|
||||
|
||||
** DONE [#B] Notify users when Last.fm import completes :importers:notifications:
|
||||
:PROPERTIES:
|
||||
:ID: 92846b36-54c5-4b78-9c57-bdc401045fbe
|
||||
|
||||
Reference in New Issue
Block a user