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

Batch-edit entities #25

Open
1 of 10 tasks
kellnerd opened this issue Aug 1, 2022 · 0 comments
Open
1 of 10 tasks

Batch-edit entities #25

kellnerd opened this issue Aug 1, 2022 · 0 comments
Assignees
Labels
idea Ideas for new scripts and features

Comments

@kellnerd
Copy link
Owner

kellnerd commented Aug 1, 2022

Collection of ideas for my Batch-edit release groups userscript.

Please be aware that I do not recommend you to use the script in its current version because the usage is not self-explanatory and it is possible to cause a lot of damage with it!

Overall goal: Extend the script from release groups to (all) other entities, especially releases

Unstructured notes

  • Rate limiter (requests per second and/or pending requests)
  • Safely extract edit source data for all entity types. Attention, the embedding has been changed on test.mb.org! (using ws/js for simplicity and compatibility with *.mb.org)
  • Extract error messages from the asynchronously fetched result pages and display them
  • Abort unnecessary page loads after redirects (for successful edits)
  • Search and replace with RegEx and/or conditions (e.g. language == eng => script = latin)
  • Validate edit data and preview non-trivial changes
  • Select-menu and textbox based UI
    • Select for Field & Action (Set to, Condition, Search & Replace), Input for Search/Condition & Replace/Value
    • Restrict values for certain fields with select (e.g. RG types, multi-select for secondary types)
    • Button to add/remove actions/conditions
    • Allow JSON for advanced fields (e.g. artist credits, arrays) until there is a better solution
  • Hidden feature: Code injection, e.g. (data) => (data.name + data.comment), using eval() or safer alternatives?
  • Automatically generate a description for the edit note ("Set x to y if z", MB Batch-edit 2021.m.d on mb.org/artist/mbid)
  • Propagate recording name to selected tracks (make name of current entity available as variable?)
    • Related idea: Use recording titles as track titles (from inside the release editor)
@kellnerd kellnerd added the idea Ideas for new scripts and features label Aug 1, 2022
@kellnerd kellnerd self-assigned this Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea Ideas for new scripts and features
Projects
None yet
Development

No branches or pull requests

1 participant