[@suvid:matrix.org](https://matrix.to/#/@suvid:matrix.org) we decided to not use the listens importer or external service oauth table for the imports. but a separate table like we do for user data exports.
suvid[m]
oh thank god 😅
makes life a bit easier!?
lucifer[m]
great, you should be able to copy most of the logic from exports and use it in import APIs.
suvid[m]
yes that was indeed the original plan
* yes,, * and that was
lucifer[m]
The only difference is that the API to trigger the import should be uploading the files
suvid[m]
* yes,, * and that was, * original plan :)
lucifer[m]
And you don't need an api to download the files.
suvid[m]
i am wondering should i start from scratch 🤔
lucifer[m]
your call.
suvid[m]
just to be clear, we aren't using the listens_importer tablr now right?
lucifer[m]
Nope
suvid[m]
and we're making the new imports table right?
lucifer[m]
Yes
suvid[m]
👍️
ok lemme think on how to go about it and will let you know in a few hours
gotta see if i should start from scratch 😅
rayyan_seliya123
hey lucifer while testing my updated indexer aligining with your recent suggestions i encountered an issue that i am unable to get directly the metatdata for `artist` and `album ` they’re only present inside the `HTML` in the `description` field Should I implement a helper function like `extract_from_description` to parse these values from the description `HTML` as a fallback, or do you prefer that we only index
what’s available in the top-level metadata?
```txt
lucifer[m]
[@rayyan_seliya123:matrix.org](https://matrix.to/#/@rayyan_seliya123:matrix.org) can you share the item id or url with me
rayyan_seliya123 sent a txt code block: https://matrix.chatbrainz.org/_matrix/media/v3/download/chatbrainz.org/wUWJqhuPAMwkZgwLpAeSSASX
