[Feature Request]: Migration script from A1111/Forge

[huchenlei]

Is there an existing issue for this?

• I have searched the existing issues and checked the recent builds/commits

What would your feature do ?

Automatically convert model metadata json (LoRA notes, configurations) generated from A1111/Forge to the markdown format this extension uses.

Proposed workflow

When A1111/Forge format JSON metadata files are detected, auto convert them to markdown format this extension uses.

Additional information

No response

[hayden-fr]

Do you want to merge or overwrite the conversion? That is, if the model has a markdown file, whether to execute the conversion program.

[Ainaemaet]

Hi there - I'd like to chime in and say I believe the best way would be to convert the .json to .md and overwrite any existing .md files that were previously created by Model Manager.

[Ainaemaet]

Also, thanks again for keeping on this. I think I would have given up on comfy long ago had it not been here to make things easier for us!!

[hayden-fr]

I think it would be great to add an A1111 conversion feature in the model scanning function, allowing precise control over the model information to be converted.

However, I haven’t used A1111 for a long time, so I’m not very familiar with some of its functionalities. I would greatly appreciate it if you could provide a template and the corresponding mapping relationships for the conversion.

[Ainaemaet]

Sounds good - will try to get that to you within the next few hours - if not, tomorrow. Ty.

[Ainaemaet]

Ok, took a little longer than I would like but here are some example .json files (as well as some of the .html's it) generated by a popular A1111 model management plugin. This should give you a concrete look at how the metadata is structured - things like LoRA notes, configurations, and other fields.

The plugin is a newer version of one I mentioned previously and is still ubiquitously used by many - I don't use A1111 at all anymore and haven't for nearly 2 years, but I keep it around exclusively for this plugin as it handles scanning and downloading of model files and info beautifully!

The idea would be to map these JSON keys (would also be nice if we could get them from the .HTML's, but not at all essential) into the markdown format Model Manager uses. Having this template should make it easier to design the conversion logic without needing to reinstall A1111.

Let me know if you need more examples from anywhere else. I can grab a few variations if that helps cover edge cases.

Thanks again for all your work here. It would make migration between A1111/Forge and Comfy a lot smoother!

stockphoto2.civitai.json
stockphoto2.html
FT_art.civitai.json
FT_art.html
Ghostly03b_CE_QWEN_AIT3k.civitai.json
Ghostly03b_CE_QWEN_AIT3k.html

[Ainaemaet]

I made a temp script for conversion, didn't have time to implement it into the code proper after doing the regex stuff - but maybe it will be helpful.

https://gist.github.com/Ainaemaet/ca560ca0f704d019d172e2a1acaa7255