Skip to content

[Feature] More studio scrape fields #5837

@feederbox826

Description

@feederbox826

Describe the feature you'd like

I would like studio scrapers to support additional fields such as Tags, Details, and Aliases via the scraper interfaces.

Describe the benefits this would bring to existing users

This feature would provide users with more comprehensive data about studios, enhancing their ability to organize and navigate their collections. Having access to additional fields would improve the overall usability and functionality of the scrapers.

Is there an existing way to achieve this goal?

Currently, studio scrapers only support basic fields like Name and URL, limiting the information available to users.

Additional context

The proposed solution includes adding Tags, Details, and Aliases to the URL scraper, as well as introducing an array for additional URLs within the Studio entity. An alternative approach considered was using a GraphQL bypass, but this may not be as efficient.

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions