Correct way of starting over from clean slate?

[tobeyger]

I removed the files in my library but there seems to still be references to the tracks that previously were there in the beets-flask database, since the UI is still telling me that tracks have been imported. I then ended up deleting the database file and that made the saved imports go away. Is that the recommended way of starting over from a clean slate or are there better ways?

The reason I ask is because I'm getting occasional "Integrity Warning" errors in the inbox. One specific album always gives me this error just as I add it to the inbox folder, so that got me thinking if there are left over data or something screwing things up?

[pSpitzner]

Hi Tobey,

I would say this is mostly expected behaviour, at least how I would expect it.

Beets Flask has its own database to keep track of what was imported at some point. This database is completely independent from beets, and it only gets update when using our interface. Depending on how you removed the files from you beets library, beets flask has no way to know about them being gone. The only way we currenlty have to remove files and keep those two perspecitves in sync is via the undo import action.

Until now, I think of the beets flask database more of a cache than something you would want to keep around forever.
If your inbox is fully imported and you are happy with the imports, you can safely remove it (restart the container afterwards).
In case you want to undo an import later, its possible via the cli, since we add a gui import id to the metadata (you can find it in the extended attributes of imported tracks, in your beets library)

The integrity warnings are something we added because we have to somehow link created previews (saved in the beets flasks database) to the folders they belong to — which can change over time, e.g. as new files are added. So indeed, if you have an old preview for a folder for which the content has changed, you might get a warning.
The warning should go away when you retag the folder, as this creates a new preview based on the current folder state, and marks the old preview as obsolete.

Hope this clarifies a bit, and let me know if you have any more questions :)
p