robotpsychology / wxyc-dj-hub Goto Github PK

There would still be an option to manually insert a breakpoint. These will show up ghosted out on the playlist timeline when the hour strikes. Also an alert when DJs submit playlists that they may be missing breakpoints if it's passed the hour and their is not one.

Would have to account for:

• Different time zones (remote DJs)
• Changing ghosted out element to actual entry
• ChronOrderID being changed when inserted already solved with swapID function in FlowsheetEntries.vue

Help section on the nav bar that presents a tutorial/resource links such as a link to the documentation for this repo.

Opens a new page with an interactive tutorial

DJ entries would have priority over outside (i.e., Discogs) information and fetches.

This will aggregate playlist and artwork data so the client only needs to make two requests for both. Currently, the client can make up to five requests for this information.

The backend service can also provide links to the track on other services: Spotify, Apple Music, Google Play, Pandora, Bandcamp, and others.

This should exist as its own project. Either we should extract all the webby bits in the current app so that it can run in a Linux box without the presence of Foundation, or we start from scratch on a server platform that doesn't use Swift (Python and Java come to mind, with whatever server frameworks they use; I'm just a mobile engineer).

@jakebromberg - WXYC/wxyc-ios-64#48

Data structure proposal:
Artist

{
    "establishedYear": Integer Date year,
    "originCountry": String,
    "artistBio": String,
    "artistImage": String URL,
    "releaseURIs": [Array of release String URIs],
}

Release

{
    "releaseYear": Integer Date year,
    "releaseBio": String,
    "releaseImage": String URL or downloaded image,
    "releaseGenres": [Array of genres String],
    "artistURI": String URI,
}

Use protobuffers as a cross platform data object descriptor. Can be used to generate code for the DB, flowsheet, services calls, and client code.

https://developers.google.com/protocol-buffers

Allow offline persistence functionality which caches entry data. This may mean turning this project into a progressive web app (PWA), which would also be useful for mobile/tablet compatibility.

Data for WXYC entries that will be directly linked to library data unless the playcut type is "other". Playcuts entered as a "library" type will but do not have a corresponding entry in the library DB will be marked for observation. They might indicate physical media in the station that is not in the library DB.
Most fields will be required. Must have djName or showName. chronOrderID is still useful for reordering of flowsheet order.
Playcut will contain a URI for externally fetched data about the playcut from a separate backend service.

Data structure proposal:

{
"id": Integer, 
"hour": Integer UNIX Time Code (maybe alternative),
"chronOrderID": Integer (always incrementing) 
"djName": String,
"showName": String,
"entryType": String ["playcut", "talkset", "breakpoint"],
"playcut": {
   "playcutType": String ["rotation", "library", "other"]
    "rotation": Boolean (maybe redundant but good for old structure consistency?),
    "request": Boolean,
    "externalMetdataURI": String URI,
    "playcutMetadata": {
        "songTitle": String,
        "labelName": String,
        "artistName": String,
        "releaseTitle": String,
         },
     },
 }

The current file has boilerplate text and broken links and images. Also, it should provide more detailed instructions on installation and standing up a server and interacting with the client.