Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hydrus-friendly Image and DB export format #1492

Closed
2 tasks
DonaldTsang opened this issue Nov 3, 2018 · 5 comments
Closed
2 tasks

Hydrus-friendly Image and DB export format #1492

DonaldTsang opened this issue Nov 3, 2018 · 5 comments
Assignees
Labels
stale Issues not updated for a long time and likely not relevant anymore.

Comments

@DonaldTsang
Copy link

Is your feature request related to a problem? Please describe

Using Imgbrd-Grabber to download mainstream *boorus faster and Hydrus for niche websites, general image management and IPFS capabilities

Describe the solution you'd like

The creation of a new export file structure/format using Zip or others to package all images downloaded from Grabber along with the DB (which can be compressed into a smaller archive) and send it to Hydrus

Describe alternatives you've considered

Simple file path with formatted structure for image and DB location for easy drag-and-drop into Hydrus (that can be coordinated into a new feature in Hydrus for intermediate data transport)

Additional context

  • Needs metadata information, including web link, image format, size, dimensions
  • Needs to maintain all tags and meta-categories e.g. reference/copyright, artist, character
@Bionus Bionus self-assigned this Nov 3, 2018
@Bionus
Copy link
Owner

Bionus commented Nov 3, 2018

AFAIK Hydrus supports the "text file beside the image" format, so you can just use an separate tag file, with a ".txt" suffix and contents set to something like (there's a bunch of issues describing it in more details, such as issue #1001 or #588):

rating:%rating%
%all:includenamespace,excludenamespace=general,unsafe,spaces,separator=\n%

Or do you really need the ZIP/DB part?

@DonaldTsang
Copy link
Author

DonaldTsang commented Nov 3, 2018

@Bionus which one has a better design pattern? Because I do have ideas on transportation formats for Hydrus desktop to communicate with other software or other Hydrus desktops.

Text file beside the image

Pro: less archaic, easier to manipulate and control without knowledge on SQL
Con: Tags are not packed together to reduce size when compressed
Con: There is no error correction to protect from file corruption or errors

Database/Folder format

Pro: Everything is in a Database so compression can save tag file size
Pro: Archive files could have error correction when transporting
Con: Compressing images may not save space at all (see CBZ or CB7)
Con: Requires prior knowledge to manipulate SQL, even for conversion
Con: It may or may not save time for transferring compressed image files

@DonaldTsang
Copy link
Author

@Bionus right now I am a bit confused with the downloaded image files and I wondered where the tags have went.

@DonaldTsang
Copy link
Author

DonaldTsang commented Jan 8, 2019

@Bionus after testing around with Imgbrd-Grabber, I would like to say that it would be nice to have txt exports as out-of-the-box default.

rating:%rating%
%all:includenamespace,excludenamespace=general,unsafe,spaces,separator=\n%

Where does this script go in Imgbrd-Grabber?

@stale
Copy link

stale bot commented Mar 29, 2022

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed if no further activity occurs.

If this issue is about a bug that still happens in the latest version, or a suggestion that is still relevant, feel free to comment on it and the maintainers will have another look, they might have missed it!

Thank you!

@stale stale bot added the stale Issues not updated for a long time and likely not relevant anymore. label Mar 29, 2022
@stale stale bot closed this as completed Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues not updated for a long time and likely not relevant anymore.
Projects
None yet
Development

No branches or pull requests

2 participants