Add "Primary Source" as default/top of list in scrape dialog

[Eleniat]

Describe the feature you'd like

Now that stashbox lists the primary source separate from databases and other sources. It would be nice to have the primary designated always.

Currently the newest URL from stashbox get put on the top.

Describe the benefits this would bring to existing users

The primary benefit for this is when scraping by url.
There have been many times I'm performing multiple scrapes by URL from the tagger page and a different URL got sorted to top and now I have data from a different source that I have to go back and fix.

Is there an existing way to achieve this goal?

Delete URL's and manually arrange them.

Have you searched for an existing open/closed issue?

• I have searched for existing issues and none cover the core request of my proposal

Additional context

No response

[DogmaDragon]

How do you determine primary though? It will vary depending on stash-box instance.

[Eleniat]

I guess it would be the same way the stashboxes do it?

Studio > 3rd party databases (IAFD, DATA18) > Other (TPDB)

Or even just being able to designate the studio URL as the URL to be scraped against.

[Maista6969]

This categorization of links is new in stash-box v0.10.0 and those categories are just something I quickly threw together last night: they are definitely subject to refinement and change

I do not believe they're visible to Stash when scraping so this feature request would probably require changes to stash-box as well, with all of the backwards compatibility considerations that entails

[Eleniat]

Fair enough, I just saw it and thought it would be a good idea to help with scraping from tagger when mixed URLs are present.

[Maista6969]

I agree and I think it might even help steer the community towards better primary source literacy 😁

[DogmaDragon]

I guess it would be the same way the stashboxes do it?

Studio > 3rd party databases (IAFD, DATA18) > Other (TPDB)

Or even just being able to designate the studio URL as the URL to be scraped against.

The categorization is arbitrary though, it has no inherent meaning on the software side, it's just what individual stash-box instance admins decide.

Also, based on #5238 being reverted as it would break manual sort order people might have, I don't think it's a likely change.

[Eleniat]

What do you mean by this breaking it by allowing one to be designated as a primary in the list?
Even if you manually sort, a newly added URL is added to the top with no control over it's position when added. This function where it gets added at the top already breaks every manual sort.

Since the 'top' one is the one that gets targeted, it is now broken. They should be added at the bottom at the very least then.

[DogmaDragon]

My point was that the change was reverted because it would impact the manual sort people might have right now. Your proposal would have the same end result, so I think the same reasoning would apply.

[Eleniat]

Currently, as it is right now, with the change reverted. Also breaks manual sorting.

I do not see how being able to designate a link to always be on top would break any form of manual sorting.

[AdultSun]

I think the source of confusion here is you're both talking about two different lists. If I understand correctly, Eleniat is asking for the list of URLs in the scrape results to follow the stash-box's configured sort order, not for all saved URLs to be re-sorted. Fresh scrapes appear to be sorted alphabetically right now:

Re-scraping through either the tagger or the scraper dialog already seems to just add missing URLs to the bottom of the list without moving manually sorted links:

[Eleniat]

That is correct, I do not want anything already existing to be changed.