This is two separate issues, really:
1) When showing comics for import, currently the first image physically is
the one loaded and treated as the cover. This is done for performance
reasons since reading files from an archive is an expensive operation, and
2) When actually importing comics, the pages are added to the comic in the
same order they appear physically in the comic.
I think #2 is easily achieved by sorting the pages alphabetically before
inserting them into the database.
Regarding #1, before I implemented #437 to replace the old, slow archive
adaptors with a more maintainable implementation, I had code that loaded
the alphabetically first image from each archive when choosing comics for
import. And I remember it was *VERY* slow since there were times where the
image was the last file in the archive and the entire archive had to be
read, which is (again) an expensive operation.
Since you only import once, I'm willing to let that continue to be a
first-image-entry operation, while we add sorting the pages to the batch
process step to load a comic during import. I've opened the following
ticket to capture that feature request:
https://github.com/comixed/comixed/issues/1104
How does that work?
On Tue, Nov 16, 2021 at 9:28 PM Doug Crowe <doug_crowe@xxxxxxxxxxx> wrote:
question for #2 on my Fixes list, what about just "sorting" the pages to
find the cover.
like in 7zip, if you go to view and uncheck sorted, then I see what
comixed currently does page 4 is first in a comic, but that sorted option
nails it. So maybe you dont need to make users pick the cover, just add
sorting to the pages to discover it. the first graphic file after sorting
is the cover. And in the cases where it isnt I will damn well delete
whatever came first, lol
------------------------------
*From:* comixed-bounce@xxxxxxxxxxxxx <comixed-bounce@xxxxxxxxxxxxx> on
behalf of Doug Crowe <doug_crowe@xxxxxxxxxxx>
*Sent:* Tuesday, November 16, 2021 9:15 PM
*To:* comixed@xxxxxxxxxxxxx <comixed@xxxxxxxxxxxxx>
*Subject:* [comixed] Re: Summary of comments for .11 SNAPSHOT
personally once #1 and #2 on the Fixes portion of my summary here is
handled, I will be happy to import my entire collection (25K marvel books),
but right now I am stopping at 15 books, lol...added suggestion #4, and fix
#3, was an option in .10.5 up by the account button, now its gone...
Fixes by order of importance
1. The Cover Date seems to have two issues
1. Sometimes Comixed has the correct cover date listed in details,
meaning it matches CV, and other times it does not
2. Regardless of letter (a) the file naming is always wrong when
using the $COVERDATE variable.
2. Allow for a right click on a page to "Assign as cover", then
reorder/rebuild and make it so.
3. Cannot find option to change cover sizes.
4. go to duplicate pages, click on a scanner tag page, in detail of
the scanner page choose to block pages like this, the popup then says
UNBLOCK, but does actually block like it should.
Suggestions
1. Allow for padded issue numbers 1 - 0001 (some series have 1000+)
PLUS the .HU .LR etc.
2. Annual integration
1. A new $ANNUAL variable to use in file naming, and if an issue is
an annual then the word annual would be included, otherwise blank.
2. Annuals would be stored along with the series they are attached
to in the same folder and not be a seperate folder or series.
3. Linking annuals to series can "sometimes" be done via CV data,
but there also would need to be a way in the app GUI to manually
link/unlink annuals to series using CV ID's in order to corrrect faulty
CV
data or just provide data when CV has none.
3. Name rules for scraping, provide something on that page to
explain/detail how it works.
4. Add ability to use Metron instead of CV, CV is doomed....
https://metron.cloud/
<https://metron.cloud/>
Metron <https://metron.cloud/>
What? Metron is a community-based site whose goal is to build an open
database with a REST API for comics. Why? Currently the only comic book
database the provides a REST API for users is Comic Vine.Unfortunately,
since it's a corporately-owned service, the community that uses it has no
control over the amount of resources provided to maintain it or ensure it's
continued accessibility.
metron.cloud
