pi_get_songs output format

[MayaGans]

See Issue #4 - I think we can simplify the output maybe?

[levisc8]

Sure. Are you thinking to drop the tags column? Or spread it somehow?

[MayaGans]

Thinking about how to spread this...

possum <- pi_get_songs(phishin_key, "Possum")

> possum$tags[1]
[[1]]
[[1]][[1]]
[[1]][[1]]$id
[1] 1

[[1]][[1]]$name
[1] "SBD"

[[1]][[1]]$priority
[1] 1

[[1]][[1]]$group
[1] "Audio"

[[1]][[1]]$color
[1] "#888888"

[[1]][[1]]$notes
NULL

[[1]][[1]]$transcript
NULL

[[1]][[1]]$starts_at_second
NULL

[[1]][[1]]$ends_at_second
NULL


[[1]][[2]]
[[1]][[2]]$id
[1] 8

[[1]][[2]]$name
[1] "Debut"

[[1]][[2]]$priority
[1] 7

[[1]][[2]]$group
[1] "Song Content"

[[1]][[2]]$color
[1] "#888888"

[[1]][[2]]$notes
NULL

[[1]][[2]]$transcript
NULL

[[1]][[2]]$starts_at_second
NULL

[[1]][[2]]$ends_at_second
NULL

Date	Title	Position	Set	Duration	Likes_CT	ID	Name	Notes
1985-10-30	Possum	3	1	6.76	2	1	SBD	NULL
1985-10-30	Possum	3	1	6.76	2	8	Debut	NULL

1. Why do these have different IDs?
2. Do you think the other data in tags is worth including?

• Priority
• Color
• Group
• Transcript
• Starts_at_Second
• Ends_at_Second

I can include all of it I guess if you think that's useful?

[levisc8]

I am not sure why they'd have different IDs. I doubt that it refers to track ID. Maybe it's a tag ID?

Group and color are probably not useful - those can't be used to further query the API (I tried Group for a tag search and got 404'd). Starts/ends_at_second might be useful for looking at how banter length evolved over time, maybe? I think priority just sets the order of appearance on the actual phish.in website when you're streaming a show, so that could probably get dropped too.

I have no idea what transcript is. If it refers to the literal transcript of, say, banter, could be used in some kind of "Can we predict the NYE gag from banter over summer/fall tour?"/word-cloud question. Need to find a track where that tag is non-NULL first to figure out what that's referring to.