Is the data versioned?

[DanForever]

I don't think I've seen anything resembling a version number in any of the releases, and I was thinking it might be a good idea to do so, so that if you want to add more information in the future, it's easy to tell [programmatically] which entries should have it and which may need updating.

I was thinking you should give a version to the "schema" that the json files follow, as well as include the name and version of the program used to create the json.

So for example, I was thinking it might be a good idea to also include a link to https://www.blu-ray.com for whatever blu ray you're looking at.
Assuming you like that idea and decide to add it, you'd also bump the schema version (e.g. from "1" to "2", or whatever version format you want to use) so that anything reading the data knows that this data should include that additional link.

Also the version of the import software would also be useful in case any errors start cropping up that you think might be caused by the importer rather than by user error. Something like:
{ "importer": { "name": "ImportBuddy", "version": "1.1.0" } }

[lfoust]

As you mentioned - the schema of the data is currently not versioned. Part of the reason I use JSON is because it is forgiving if data is added or taken away. I am not sure if having a formal version would really benefit any current scenarios I can think of. There have been several changes to the schema over the years and it is the job of the tools to handle data that might be added or missing. This has worked out so far.

I do like the idea of having the blu-ray.com link - but I would probably rather just do the ID of the item in case the url format of that site changes. The metadata.json file does have an ExternalIds section already so we could add it there:

[DanForever]

I was thinking of it only from the user perspective, but of course you're right storing the ID is a much better idea