andrewvy / dojinlist Goto Github PK

Should be able to see when album was created, edited, etc.

https://www.evanmiller.org/bayesian-average-ratings.html

https://github.com/sandeepshetty/subdomain-blacklist

You should be able to upload track audio data, and get feedback whether or not the audio file is valid for input.

• mastered by
• vocals
• instrument
• instrument type

See: https://developer.mozilla.org/en-US/docs/Web/API/NavigatorLanguage/language

We should store initial locale + preference in local storage.

Adding a storefront, can pick an artist name.

Is this you? to link up to existing artists. If clicked yes, manual verification step needed to link a storefront to an artist.

Can store a subdomain for the storefront.

Searching for a track name should bring up albums with that track name.

• Classification: Original Work, Arrangement, Remix

bunch of tags?

original-work, arrangement, touhou

Should be able to modify tracklist for an album.

How to handle tracklists in different languages? (Separate tracks, or track has multiple names?)

Users should be able to gain points through community interaction + album submission.

Be able to add/remove user permissions from GQL, as long as you have the modify_permissions permission.

In order to get to i18n-everything, we will need to return consumable errors-as-data, with translatable error codes that the client can interpret.

Because the initial fetch is cached in the MeContext, which will return no data when unauthenticated. It will not refetch after we've logged in.

We should refetch Me when authcontext changes.

So that we can do #14 to credit the user who created the album after it's been verified.

Instead of just albums(storefront_id: ID!), should also make it so you can fetch via storefront.albums association.

Elasticsearch provides suggestion text ranked by related documents.

This helps the user narrow down their search before actually executing it.

This process breaks apart the text into tokens and finds similar tokens, ranked by "relevancy."

Some POC GQL types:

albumSuggestions(suggestion: String) {
  suggestions {
    length
    offset
    options {
      doc {
      }
      text
    }
  }
}

UI:

Suggestion: "te"

Test
Test Album
Album Test
China House Tea

"Mark as helpful"

In addition to getting overall top albums, need to add more data to ETS storage that will allow matching for genres, artists, and events.

An album could be purchased in many different ways.

Search albums by name.

Likes:

rating: 0-10
description: Text

https://stackoverflow.com/questions/18710992/how-to-add-album-art-with-ffmpeg

Since there will be multiple different services, API/transcoder/front-end, it would be nice to have a monorepo to organize in.

test

• Adding tracks as part of initial album creation
• Editing a track

Albums can get associated to a storefront, which means it is available for purchase.

• How to purchase an album, and what that data model looks like?
• Where is price stored?
• If purchased, what should the split be?
• Who originally uploaded the album?

We should fill in as much details into the form to make the Stripe Connect OAuth process much easier + faster.

List of resources for building phase 2 of album recommendations, which is a machine-learning oriented approach as an evolution/alternative to a set of business rules.

http://cs229.stanford.edu/proj2017/final-reports/5244334.pdf

Add to GQL + Core, ability to search albums by event.

Activity Item Types:

• NEW_REVIEW
• SUBMITTED_ALBUM
• ADDED_ALBUM
• COMMENTED_ON_ALBUM

Events like Comiket 93, Comiket 94, should maybe be grouped under a parent Event Group called Comiket.