Closed macro1 closed 9 years ago
Should we trigger an Artist
model instance to be created whenever an FMA Artist is created?
I can try to make a data migration to move the old FMAArtist
data into the new fma Artist model. Then we could migrate the fixture data and delete the old model.
Probably create a artists.Hyperlink on new fma.Artist. We can create a new artists.Artist as part of saving Hyperlinks. I think I did this with the bandcamp app as well.
This adds a new app,
fma
, to store queried data from the FMA API. I did not work on migratingFMAArtist
fromartists
, I opted to make a duplicateArtist
model infma
for now. I did add the FMAArtist admin page though, and added a list action for kicking off the track query from that perspective. It will only query for artists that have not been modified in a week.If we're fine with this new layout for storing the data, we can work on migrating the existing FMA data into the new app, and decide on how we're going to update and back-fill the album and track data. I think there may be some additional fields we could take advantage of in the query as well.
I'm not capturing all of the data. I'm thinking of adding them as part of this PR. Here is an example of a single track's data: