[GH-ISSUE #244] FR: Metadata Migration & Local Metadata Naming Structure #129

New Issue

2026-02-17T17:06:13-05:00

yindo commented

2026-02-17 17:06:13 -05:00

Originally created by @Elite-Alien on GitHub (Sep 8, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/244

These two options could make switching to a new server or whatever a less of a hassle & easier to run multiple instances of Drop with the same data. It could also be great for if you house the games on one install and docker stuff in another VM/PC. Before I get to ahead of myself, let me break it down and just start with the Local Metadata first.

I would like to see an option to place images into the game folder such as "/Game-Name/metadata" beside the "Version" folder(s). Using a default naming system, sort of like you do with say Plex, Emby, or Jellyfin, "Poster", "landscape", "banner", et cetera. Then Drop can load the local images auto-magically into the service instantly upon a option like "Import with Local data" button you could put near the "Import Without Metadata" button.

To further extend this, an option to store any downloaded metadata in this structure when your scrape would be delightful as well. To further a easy transition or whatever that may come ones way.

Metadata Migration would be that if you have data in the standard location you could go to say "Tasks" and hit a button to migrate current metadata to local metadata or vise versa. Which would take a long or short time based on your game library, but a task that could just run in the background while users have no clue it's happening. As the metadata could be moved with maybe something like "Rsync" using the "--remove-source-files" and perhaps also using "--prune-empty-dirs" to clean up the previous metadata & remaining empty folders. There may be a better way to do it than Rsync, but seems like a safe way around moving the data.

Originally created by @Elite-Alien on GitHub (Sep 8, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/244 These two options could make switching to a new server or whatever a less of a hassle & easier to run multiple instances of Drop with the same data. It could also be great for if you house the games on one install and docker stuff in another VM/PC. Before I get to ahead of myself, let me break it down and just start with the Local Metadata first. 1) I would like to see an option to place images into the game folder such as "/Game-Name/metadata" beside the "Version" folder(s). Using a default naming system, sort of like you do with say Plex, Emby, or Jellyfin, "Poster", "landscape", "banner", et cetera. Then Drop can load the local images auto-magically into the service instantly upon a option like "Import with Local data" button you could put near the "Import Without Metadata" button. To further extend this, an option to store any downloaded metadata in this structure when your scrape would be delightful as well. To further a easy transition or whatever that may come ones way. 2) Metadata Migration would be that if you have data in the standard location you could go to say "Tasks" and hit a button to migrate current metadata to local metadata or vise versa. Which would take a long or short time based on your game library, but a task that could just run in the background while users have no clue it's happening. As the metadata could be moved with maybe something like "Rsync" using the "--remove-source-files" and perhaps also using "--prune-empty-dirs" to clean up the previous metadata & remaining empty folders. There may be a better way to do it than Rsync, but seems like a safe way around moving the data.

yindo added the feature qol labels 2026-02-17 17:06:13 -05:00

yindo commented

2026-02-17 17:06:13 -05:00

@DecDuck commented on GitHub (Sep 16, 2025):

I wouldn't be against something like /game/version/.drop/metadata. We could also have an option to write the metadata to disk as a JSON or NFO file.

I like it, sounds good.

@DecDuck commented on GitHub (Sep 16, 2025): I wouldn't be against something like /game/version/.drop/metadata. We could also have an option to write the metadata to disk as a JSON or NFO file. I like it, sounds good.

yindo commented

2026-02-17 17:06:13 -05:00

@Elite-Alien commented on GitHub (Sep 16, 2025):

So, each version of the game you have, for example, v1.0 Linux, V4.0 Linux, v1.0 Windows, v4.0 Windows, v1.0 Mac, & v4.0 Mac would have the same metadata duplicated for each version? Or are you implying like a .NFO or JSON file was in those folders and it pulls from like the main folder structure of say /game/metadata if it's not modified different per game version?

Perhaps I have misunderstood something with the library structure a little as well. Is Drop capable of have a structure like /game/v1.0 and then have multiple sub folders in it with each of the platforms in it and Drop can determine to download only that sub-folder for Linux, Windows, or Mac? Because if so, I must be doing something wrong as Drop downloaded them all like that for me.

Ignore this bullet-point if the above is true.

That could be fairly cool to be able to have different changes per version. Like for the changes and all if it's Early Access to Released versions too. It could reflect on the game, not a bad idea. My one thought though, and only expanding on this idea further here, perhaps a toggle to link metadata for same versions, but different platforms so your not duplicating the metadata like three times. Perhaps when editing the games you can toggle something like "Link metadata" or some kind of option to keep them all together as sort of one.

Anyway, much appreciated for following up on this and a potential update in the far off future update down the line.

Edit: Also, is OpenCollective the only place to donate or is there more places? If there are more spots to donate which is best for donations percentage wise. Like which one gets you the highest percentage of the money?

@Elite-Alien commented on GitHub (Sep 16, 2025): So, each version of the game you have, for example, v1.0 Linux, V4.0 Linux, v1.0 Windows, v4.0 Windows, v1.0 Mac, & v4.0 Mac would have the same metadata duplicated for each version? Or are you implying like a .NFO or JSON file was in those folders and it pulls from like the main folder structure of say /game/metadata if it's not modified different per game version? Perhaps I have misunderstood something with the library structure a little as well. Is Drop capable of have a structure like /game/v1.0 and then have multiple sub folders in it with each of the platforms in it and Drop can determine to download only that sub-folder for Linux, Windows, or Mac? Because if so, I must be doing something wrong as Drop downloaded them all like that for me. Ignore this bullet-point if the above is true. - That could be fairly cool to be able to have different changes per version. Like for the changes and all if it's Early Access to Released versions too. It could reflect on the game, not a bad idea. My one thought though, and only expanding on this idea further here, perhaps a toggle to link metadata for same versions, but different platforms so your not duplicating the metadata like three times. Perhaps when editing the games you can toggle something like "Link metadata" or some kind of option to keep them all together as sort of one. Anyway, much appreciated for following up on this and a potential update in the far off future update down the line. Edit: Also, is OpenCollective the only place to donate or is there more places? If there are more spots to donate which is best for donations percentage wise. Like which one gets you the highest percentage of the money?

yindo commented

2026-02-17 17:06:13 -05:00

@DecDuck commented on GitHub (Sep 25, 2025):

The .nfo/.json would be at the game root, and store the metadata. And then we could have a different .json for version that sorts the version's configuration data.

The best way to contribute to the project is through OpenCollective or GitHub sponsors of individual contributors. OpenCollective is only for the project's expenses, but directly supporting contributors helps them pay bills and make time for the project. All options have about the same fees, usually around 5%.

@DecDuck commented on GitHub (Sep 25, 2025): The .nfo/.json would be at the game root, and store the metadata. And then we could have a different .json for version that sorts the version's configuration data. The best way to contribute to the project is through OpenCollective or GitHub sponsors of individual contributors. OpenCollective is only for the project's expenses, but directly supporting contributors helps them pay bills and make time for the project. All options have about the same fees, usually around 5%.

yindo commented

2026-02-17 17:06:14 -05:00

@Elite-Alien commented on GitHub (Oct 29, 2025):

Busy few weeks, I know you have had your share as well I am sure. Though, I went with OpenCollective and dropped 100USD. I wanted to be sure as much as possible would get in the hands of this project. I like contributing to OSS I use here and there so I might drop some more later on. Keep up the good work and if I can support individual contributors I might do that later as I have some ideas and perhaps I can pay out like a bounty or something. I would love to see this project be a lot more popular and just have more contributions all around.

@Elite-Alien commented on GitHub (Oct 29, 2025): Busy few weeks, I know you have had your share as well I am sure. Though, I went with OpenCollective and dropped 100USD. I wanted to be sure as much as possible would get in the hands of this project. I like contributing to OSS I use here and there so I might drop some more later on. Keep up the good work and if I can support individual contributors I might do that later as I have some ideas and perhaps I can pay out like a bounty or something. I would love to see this project be a lot more popular and just have more contributions all around.

yindo referenced this issue

2026-02-17 17:06:31 -05:00

[PR #194] [MERGED] Admin library multi-issue #258

yindo referenced this issue

2026-06-05 14:21:14 -04:00

[GH-ISSUE #129] Admin home page - bandwidth usage #69

yindo changed title from ~~FR: Metadata Migration & Local Metadata Naming Structure~~ to [GH-ISSUE #244] FR: Metadata Migration & Local Metadata Naming Structure

2026-06-05 14:21:36 -04:00

yindo commented

2026-06-05 14:21:37 -04:00

@Jeansy91 commented on GitHub (Mar 8, 2026):

I would like to echo this request. I use Drop OSS and have encountered the issue several times where the central metadata directory was emptied after a restart.

Since I invest a lot of time and effort in the texts and images in my game collection, storing them directly in the game directory would be an essential safety net. It would make the data more portable and ensure that it can be easily reloaded in an emergency without having to rely on external backups.

@Jeansy91 commented on GitHub (Mar 8, 2026): I would like to echo this request. I use Drop OSS and have encountered the issue several times where the central metadata directory was emptied after a restart. Since I invest a lot of time and effort in the texts and images in my game collection, storing them directly in the game directory would be an essential safety net. It would make the data more portable and ensure that it can be easily reloaded in an emergency without having to rely on external backups.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Drop-OSS/drop#129